The setup for said mailserver is pretty convoluted (due to it being on a dynamic IP address and me being cheap).
The primary domain chimera-tech.com uses the tzo server to provide dynamic name resolution.
I host a secondary domain (intuitmassage.com) for a friend of mine who is a massage therapist. She has an email address at that domain. She only receives email through my server, her outgoing mail goes through her ISP so there are no problems with the lack of PTR record. The domain intuitmassage.com has a CNAME record that points it back to chimera-tech.com (because it is much cheaper than hosting a second domain on tzo). Because it is a CNAME, it has no MX, as a mailserver SHOULD pull the CNAME for intuitmassage.com, which returns chimera-tech.com, and then pull the MX for that.
In most cases, this works just fine, mail flows in just as it should.
However, I recently ran into a problem with someone sending her (my friend with the intuitmassage.com email address) an email from SBC. Instead of going through, she got the following bounce from SBCs mailserver (note the left hand side of addresses have been munged to protect the guilty... err, I mean innocent):
QUOTE
------ Forwarded Message
From: Mail Delivery Subsystem <MAILER-DAEMON[at]ylpvm12.prodigy.net>
Date: Wed, 30 Aug 2006 12:15:22 -0400
To: <xxxx[at]worrellcreative.com>
Subject: Returned mail: see transcript for details
The original message was received at Wed, 30 Aug 2006 12:15:20 -0400
from ppp-70-255-182-127.dsl.hstntx.swbell.net [70.255.182.127]
----- The following addresses had permanent fatal errors -----
<xxxx[at]intuitmassage.com>
(reason: 550 5.7.1 Unable to relay for xxxx[at]www.chimera-tech.com)
----- Transcript of session follows -----
... while talking to mail.chimera-tech.com.:
>> DATA
<<< 550 5.7.1 Unable to relay for xxxx[at]www.chimera-tech.com
550 5.1.1 <xxxx[at]intuitmassage.com>... User unknown
<<< 554 5.5.2 No valid recipients
Reporting-MTA: dns; ylpvm12.prodigy.net
Received-From-MTA: DNS; ppp-70-255-182-127.dsl.hstntx.swbell.net
Arrival-Date: Wed, 30 Aug 2006 12:15:20 -0400
Final-Recipient: RFC822; xxxx[at]www.chimera-tech.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mail.chimera-tech.com
Diagnostic-Code: SMTP; 550 5.7.1 Unable to relay for
xxxx[at]www.chimera-tech.com
Last-Attempt-Date: Wed, 30 Aug 2006 12:15:22 -0400
------ End of Forwarded Message
From: Mail Delivery Subsystem <MAILER-DAEMON[at]ylpvm12.prodigy.net>
Date: Wed, 30 Aug 2006 12:15:22 -0400
To: <xxxx[at]worrellcreative.com>
Subject: Returned mail: see transcript for details
The original message was received at Wed, 30 Aug 2006 12:15:20 -0400
from ppp-70-255-182-127.dsl.hstntx.swbell.net [70.255.182.127]
----- The following addresses had permanent fatal errors -----
<xxxx[at]intuitmassage.com>
(reason: 550 5.7.1 Unable to relay for xxxx[at]www.chimera-tech.com)
----- Transcript of session follows -----
... while talking to mail.chimera-tech.com.:
>> DATA
<<< 550 5.7.1 Unable to relay for xxxx[at]www.chimera-tech.com
550 5.1.1 <xxxx[at]intuitmassage.com>... User unknown
<<< 554 5.5.2 No valid recipients
Reporting-MTA: dns; ylpvm12.prodigy.net
Received-From-MTA: DNS; ppp-70-255-182-127.dsl.hstntx.swbell.net
Arrival-Date: Wed, 30 Aug 2006 12:15:20 -0400
Final-Recipient: RFC822; xxxx[at]www.chimera-tech.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mail.chimera-tech.com
Diagnostic-Code: SMTP; 550 5.7.1 Unable to relay for
xxxx[at]www.chimera-tech.com
Last-Attempt-Date: Wed, 30 Aug 2006 12:15:22 -0400
------ End of Forwarded Message
Now, from looking at this, it looks to me as if the SBC mail server is rewriting the recipient using the cname record, so instead of sending to xxxx[at]intuitmassage.com, SBC pulls the CNAME for intuitmassage.com which is www.chimera-tech.com and rewrites the Recipient as xxxx[at]www.chimera-tech.com, which doesn't exist.
So first, am I reading that correct, or is there something else going on here that I am missing?
Second, if that is what is happening, is this RFC compliant? I can't find anywhere in the RFCs for SMTP that I have looked for that indicate recipient addresses should ever be rewritten with the CNAME values.
