I cant sent or recieve e-mail using virtualmin pro

3 posts / 0 new
Last post
#1 Mon, 03/23/2009 - 05:13
virtualminldwms

I cant sent or recieve e-mail using virtualmin pro

I'm having e-mail problems with pop imap usermin_mail my OS debian 4 r7 virtualmin 3.66 webmin 1.450

Can't use webmail/usermin htpps::20000 browser Can't use thunderbrid e-mail client dovecot outgoing server smtp.domain.net incoming mail.domain.net or imap.domain.net Can't use outlook e-mail client outgoing server smtp.domain.net incoming mail.domain.net or imap.domain.net

See:Errors from mail clients

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

ldwms@wmsinv.net

Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <ldwms@wmsinv.net>: Recipient address rejected: User unknown in virtual alias table (state 14).

----- Original message -----

MIME-Version: 1.0 Received: by 10.142.107.5 with SMTP id f5mr2870087wfc.130.1237816284564; Mon, 23 Mar 2009 06:51:24 -0700 (PDT) In-Reply-To: <E1Llg1q-0007TD-QS@host2.cnczone.com> References: <E1Llg1q-0007TD-QS@host2.cnczone.com> Date: Mon, 23 Mar 2009 08:51:24 -0500 Message-ID: <dfe1dd9f0903230651n75cfa67drc790c18a7b0a0d47@mail.gmail.com> Subject: Fwd: CNCzone Weekly Newsletter From: L D Williams <ldwmss@gmail.com> To: ldwms@wmsinv.net Content-Type: multipart/alternative; boundary=001636e90a90f04c200465c98fe0

--001636e90a90f04c200465c98fe0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

Mon, 03/23/2009 - 05:17
andreychek

Howdy,

So, the domain you're sending it to is &quot;wmsinv.net&quot;.

Checking out your DNS, the primary MX record for that domain points to &quot;mx.att.com&quot;.

That sounds a little fishy, are you sure that's correct? :-)
-Eric

Mon, 03/23/2009 - 06:51 (Reply to #2)
ronald
ronald's picture

this is the full report

MX Records Your MX records that were reported by your nameservers are:

10 mail.wmsinv.net 76.186.181.29
7 mx.wmsinv.net No A Record (no glue either)
8 mx.tx.rr.com No A Record (no glue either)
9 wmsinv.net 76.186.181.29
10 mx.ns2 No A Record (no glue either)
10 rr.com 24.28.199.142 (no glue)
10 tx.rr.com No A Record (no glue either)

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]

Warning Different MX records at nameservers The MX records that are not the same at all your nameservers:
mail.wmsinv.net with ip(s): 76.186.181.29 reported only by: 76.186.181.29
mx.wmsinv.net without any IP and no glue reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
mx.tx.rr.com without any IP and no glue reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
wmsinv.net with ip(s): 76.186.181.29 reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
mx.ns2 without any IP and no glue reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
rr.com with ip(s): 24.28.199.142 reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
tx.rr.com without any IP and no glue reported only by: 69.57.160.118 67.214.161.154 67.214.175.73 64.182.102.188
It is better to have the same MX records at all your nameservers!

Error MX name validity The MX records that do not seem valid hostname:
mx.ns2
This can cause problems

Topic locked