Backup/Secondary Mx Issue

Hi Group,

I really hope you can help me with this one. We have a domain for which
we have 3 MX records configured. First one is Primary and is with local
mail hosting provider. The other 2 are with Yahoo Small business and
acting as a secondary mx so in case primary mx is busy or down all the
mails will me sent to the seondary MX records. WE have a internal mail
server on which mails are getting pushed (SMTP Tunneling) from the
Primary mx. We are popping the messages from Yahoo server using
fetchmail.
But somehow this MX arrangment seems to be giving trouble. We get
bounce messages once in a while like from yahoo even though we have a
catchall account with them:

Message from yahoo.com.
Unable to deliver message to the following address(es).

:
This user doesn't have a somedomain.com account (user@somedomain.com)
[0]

Any inputs will be really appreciated.

Thanks,
Shrinath

Re: Backup/Secondary Mx Issue

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-22980-1160391739-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

tornado579@gmail.com writes:

> Hi Group,
>
> I really hope you can help me with this one. We have a domain for which
> we have 3 MX records configured. First one is Primary and is with local
> mail hosting provider. The other 2 are with Yahoo Small business and
> acting as a secondary mx so in case primary mx is busy or down all the
> mails will me sent to the seondary MX records. WE have a internal mail

For starters, secondary MX bring no value on the modern Internet. If your
main line goes down for an hour, or two, all senders will simply wait and
try again.


> But somehow this MX arrangment seems to be giving trouble. We get
> bounce messages once in a while like from yahoo even though we have a
> catchall account with them:
>
> Message from yahoo.com.
> Unable to deliver message to the following address(es).
>
> :
> This user doesn't have a somedomain.com account (user@somedomain.com)
> [0]
>
> Any inputs will be really appreciated.

Only Yahoo can help you regarding problems with their mail service. Contact
Yahoo technical support.


--=_mimegpg-commodore.email-scan.com-22980-1160391739-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFKiw7x9p3GYHlUOIRAq8LAJ995aCGKPvJlNx+F3FDJVAiW3EMRgCf dRc7
GzM1g6QBwX15DYcSGLWXVKM=
=1AGk
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-22980-1160391739-0001--

Re: Backup/Secondary Mx Issue

Hi,

Thanks for replying.

> For starters, secondary MX bring no value on the modern Internet. If your
> main line goes down for an hour, or two, all senders will simply wait and
> try again.

What has line got to do with it ? The mail servers are not hosted with
us. They are hosted with the hosting service providers from which are
pushing/fetching the messages.

> Only Yahoo can help you regarding problems with their mail service. Contact
> Yahoo technical support.

Yes, i had contacted them. This is what they have to say. I am not sure
this is a valid reason:

"As we have been investigating your email issue, we have run into the
root cause of the problem. The problem is caused by a special MX
record you have created above Yahoo!'s MX record for your email
account.

We unfortunately cannot fix the problem because it is a setting you
have designated above Yahoo!. By removing that MX record should return
your email settings back to normal."

Here special MX record is nothing but the primary MX record that is
with the local service provider.

Comments please.

Re: Backup/Secondary Mx Issue

tornado579@gmail.com wrote:

>Message from yahoo.com.
>Unable to deliver message to the following address(es).
>
>:
>This user doesn't have a somedomain.com account (user@somedomain.com)

Is somedomain.com meant to be your domain name or is it the domain
name of a third party? Is this message in response to a message you
have sent or is it in response to a message sent by someone else to
you? Is it a misdirected bounce caused by a spammer forging your email
address?

Re: Backup/Secondary Mx Issue

Hi,

somedomain is our domain only. i dont think this is caused by spammers
forging the email. Because the headers tell a different story. The
headers are coming from yahoo.
for e.g.:

Message from yahoo.com.
Unable to deliver message to the following address(es).

someuser@somedomain.com:
This user doesn't have a bitwiseglobal.com account
(someuser@somedomain.com) [0]

X-Rocket-Track: cat=UK;
info=ip:NN;sv:UK;s
g:UK
X-Originating-IP: [203.124.128.26]
Return-Path:
Authentication-Results: mta104.biz.mail.re2.yahoo.com
from=bitwiseindia.com; domainkeys=neutral (no sig)
Received: from xx.xx.xx.xx (EHLO somedomain.com) (xx.xx.xx.xx)
by mta104.biz.mail.re2.yahoo.com with SMTP; Mon, 02 Oct 2006 21:55:45
-0700
Received: from emailserver ([xx.xx.xx.x])
by somedomain.com (8.11.7p1+Sun/8.9.1) with ESMTP id k934ZDI11686;
Mon, 2 Oct 2006 23:35:13 -0500 (GMT)
Received: from 192.168.62.127 by emailserver ([192.168.62.222] running
server) with ESMTP; Tue, 3 Oct 2006 10:26:35 +0530
From: someuser@somedomain.com
To: someuser@somedomain.com
Cc: someuser@somedomain.com
Subject: estimates
Date: Tue, 3 Oct 2006 10:26:42 +0530
Message-ID: <00ba01c6e6a8$519bff70$7f3ea8c0@bitwiseglobal.net>
MIME-Version: 1.0
Content-Type: mu
*** MESSAGE TRUNCATED ***

Re: Backup/Secondary Mx Issue

Hi,

somedomain is our domain only. i dont think this is caused by spammers
forging the email. Because the headers tell a different story. The
headers are coming from yahoo.
for e.g.:

Message from yahoo.com.
Unable to deliver message to the following address(es).

someu...@somedomain.com:
This user doesn't have a somedomain.com account
(someu...@somedomain.com) [0]

X-Rocket-Track: cat=UK;
info=ip:NN;sv:UK;s
g:UK
X-Originating-IP: [203.124.128.26]
Return-Path:
Authentication-Results: mta104.biz.mail.re2.yahoo.com
from=bitwiseindia.com; domainkeys=neutral (no sig)
Received: from xx.xx.xx.xx (EHLO somedomain.com) (xx.xx.xx.xx)
by mta104.biz.mail.re2.yahoo.com with SMTP; Mon, 02 Oct 2006 21:55:45
-0700
Received: from emailserver ([xx.xx.xx.x])
by somedomain.com (8.11.7p1+Sun/8.9.1) with ESMTP id
k934ZDI11686;
Mon, 2 Oct 2006 23:35:13 -0500 (GMT)
Received: from 192.168.62.127 by emailserver ([192.168.62.222] running
server) with ESMTP; Tue, 3 Oct 2006 10:26:35 +0530
From: someu...@somedomain.com
To: someu...@somedomain.com
Cc: someu...@somedomain.com
Subject: estimates
Date: Tue, 3 Oct 2006 10:26:42 +0530
Message-ID: <00ba01c6e6a8$519bff70$7f3ea8c0@somedomain.net>
MIME-Version: 1.0
Content-Type: mu
*** MESSAGE TRUNCATED ***

Re: Backup/Secondary Mx Issue

Hi,

somedomain is our domain only. i dont think this is caused by spammers
forging the email. Because the headers tell a different story. The
headers are coming from yahoo.
for e.g.:

Message from yahoo.com.
Unable to deliver message to the following address(es).

someu...@somedomain.com:
This user doesn't have a somedomain.com account
(someu...@somedomain.com) [0]

X-Rocket-Track: cat=UK;
info=ip:NN;sv:UK;s
g:UK
X-Originating-IP: [203.124.128.26]
Return-Path:
Authentication-Results: mta104.biz.mail.re2.yahoo.com
from=domain.com; domainkeys=neutral (no sig)
Received: from xx.xx.xx.xx (EHLO somedomain.com) (xx.xx.xx.xx)
by mta104.biz.mail.re2.yahoo.com with SMTP; Mon, 02 Oct 2006 21:55:45
-0700
Received: from emailserver ([xx.xx.xx.x])
by somedomain.com (8.11.7p1+Sun/8.9.1) with ESMTP id
k934ZDI11686;
Mon, 2 Oct 2006 23:35:13 -0500 (GMT)
Received: from 192.168.62.127 by emailserver ([192.168.62.222] running
server) with ESMTP; Tue, 3 Oct 2006 10:26:35 +0530
From: someu...@somedomain.com
To: someu...@somedomain.com
Cc: someu...@somedomain.com
Subject: estimates
Date: Tue, 3 Oct 2006 10:26:42 +0530
Message-ID: <00ba01c6e6a8$519bff70$7f3ea8c0@somedomain.net>
MIME-Version: 1.0
Content-Type: mu
*** MESSAGE TRUNCATED ***

Re: Backup/Secondary Mx Issue

tornado579@gmail.com writes:

> Hi,
>
> Thanks for replying.
>
> > For starters, secondary MX bring no value on the modern Internet. If your
> > main line goes down for an hour, or two, all senders will simply wait and
> > try again.
>
> What has line got to do with it ? The mail servers are not hosted with
> us. They are hosted with the hosting service providers from which are
> pushing/fetching the messages.
>
> > Only Yahoo can help you regarding problems with their mail service. Contact
> > Yahoo technical support.
>
> Yes, i had contacted them. This is what they have to say. I am not sure
> this is a valid reason:
>
> "As we have been investigating your email issue, we have run into the
> root cause of the problem. The problem is caused by a special MX
> record you have created above Yahoo!'s MX record for your email
> account.
>
> We unfortunately cannot fix the problem because it is a setting you
> have designated above Yahoo!. By removing that MX record should return
> your email settings back to normal."
>
> Here special MX record is nothing but the primary MX record that is
> with the local service provider.

Is that mailbox on primary MX ?

Re: Backup/Secondary Mx Issue

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-29502-1160432840-0004
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

tornado579@gmail.com writes:

> Hi,
>
> Thanks for replying.
>
>> For starters, secondary MX bring no value on the modern Internet. If your
>> main line goes down for an hour, or two, all senders will simply wait and
>> try again.
>
> What has line got to do with it ? The mail servers are not hosted with
> us. They are hosted with the hosting service providers from which are
> pushing/fetching the messages.

Same principle applies. There's very little, if any benefit, to be had with
secondary MX servers on the modern Internet.

On the other hand, using secondary MX server brings a whole host of new
problems.

>> Only Yahoo can help you regarding problems with their mail service. Contact
>> Yahoo technical support.
>
> Yes, i had contacted them. This is what they have to say. I am not sure
> this is a valid reason:
>
> "As we have been investigating your email issue, we have run into the
> root cause of the problem. The problem is caused by a special MX
> record you have created above Yahoo!'s MX record for your email
> account.
>
> We unfortunately cannot fix the problem because it is a setting you
> have designated above Yahoo!. By removing that MX record should return
> your email settings back to normal."
>
> Here special MX record is nothing but the primary MX record that is
> with the local service provider.
>
> Comments please.

Sounds like Yahoo does not support their customers using Yahoo for a backup
MX.



--=_mimegpg-commodore.email-scan.com-29502-1160432840-0004
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFKszIx9p3GYHlUOIRAlXcAJ9B5fj0FBmY+OqlIcEWqZN0rdwWUQCg gA7p
y/PqgLw6aJLLYN54xHB0Rdo=
=5ZUx
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-29502-1160432840-0004--