Re: Wrong FQDN in From
On Mon, July 13, 2009 18:05, Jaime Kikpole wrote: When RT sends an email to me, it is coming from r...@atlas.cairodurham.org. I am trying to make that say r...@cns.cairodurham.org, instead. postconf -e 'myorigin=cns.cairodurham.org' postconf -e 'myhostname=atlas.cairodurham.org' more problems ? postconf -n to pastebin, none here have a crystallball :) -- xpoint
Re: Wrong FQDN in From
On Mon, July 13, 2009 19:34, Noel Jones wrote: Don't use a CNAME in a mail address. hmm i belived it was just for the mx to not be a cname ? -- xpoint
Re: Wrong FQDN in From
Jaime Kikpole a écrit : On Mon, Jul 13, 2009 at 1:47 PM, Victor Duchovnivictor.ducho...@morganstanley.com wrote: Don't use a CNAME in a mail address. Why not? After all, how would you handle vhosts if you can't send as the CNAME record? since when CNAME was needed for vhosts? alice A 192.0.2.1 bob A 192.0.2.1 ... CNAME is necessary when the name points to an external zone which is not under your control. that is: alice CNAME joe.example.com. bob CNAME joe.example.com. with example.com being an external domain (that is not under your control). if example.com zone is under your control, it is easy to use a script to generate A records instead. [snip] So its caused by some combination of factors which includes the CNAME and Request Tracker. (Remember, using telnet to manually build and send a message sent it as cns.cairodurham.org before the DNS changed.) maybe submission is using Sendmail and not the sendmail command provided by postfix. It is generally easier to uninstall Sendmail when you want to use postfix. Any reason I shouldn't leave the DNS like this? As Noel already said, external MTAs may replace the CNAME, which would cause problems. Also, that question about virtual hosting of several email domains was not rhetorical. How is a sysadmin supposed to configure their DNS for such a thing? see above.
Re: Wrong FQDN in From
Jaime Kikpole wrote: I just migrated most users from one server to another one. However, a few things still need to work on the first server. One of them is a web-based program named Request Tracker (RT). When RT sends an email to me, it is coming from r...@atlas.cairodurham.org. I am trying to make that say r...@cns.cairodurham.org, instead. The reverse DNS lookup is atlas, but there is also a CNAME for cns. The original email coming out of RT says From: Enoch Root via RT r...@cns.cairodurham.org. However, it seems to be rewrtiten as From: Enoch Root via RT r...@atlas.cairodurham.org by the time it arrives in my inbox. Don't use a CNAME in a mail address. -- Noel Jones
Re: Wrong FQDN in From
On Mon, Jul 13, 2009 at 12:34:00PM -0500, Noel Jones wrote: Jaime Kikpole wrote: I just migrated most users from one server to another one. However, a few things still need to work on the first server. One of them is a web-based program named Request Tracker (RT). When RT sends an email to me, it is coming from r...@atlas.cairodurham.org. I am trying to make that say r...@cns.cairodurham.org, instead. The reverse DNS lookup is atlas, but there is also a CNAME for cns. The original email coming out of RT says From: Enoch Root via RT r...@cns.cairodurham.org. However, it seems to be rewrtiten as From: Enoch Root via RT r...@atlas.cairodurham.org by the time it arrives in my inbox. Don't use a CNAME in a mail address. Sendmail often rewrites these. Postfix typically leaves CNAME domains alone. The OP should avoid these, but otherwise, should find out *where* along the delivery path the CNAME is replaced with the underlying name. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: mailto:majord...@postfix.org?body=unsubscribe%20postfix-users If my response solves your problem, the best way to thank me is to not send an it worked, thanks follow-up. If you must respond, please put It worked, thanks in the Subject so I can delete these quickly.
Re: Wrong FQDN in From
On Mon, Jul 13, 2009 at 1:47 PM, Victor Duchovnivictor.ducho...@morganstanley.com wrote: Don't use a CNAME in a mail address. Why not? After all, how would you handle vhosts if you can't send as the CNAME record? Sendmail often rewrites these. Postfix typically leaves CNAME domains alone. The OP should avoid these, but otherwise, should find out *where* along the delivery path the CNAME is replaced with the underlying name. I'm the OP. Based on the data I have, I believe that what goes into postfix uses the CNAME but what comes out is using the A record. I do have a little doubt, though, as the /var/log/maillog file shows w...@atlas.cairodurham.org connecting to postfix. If I grep cairo main.cf* and grep atlas main.cf*, I don't see anything that should be rewriting this. I just tried a test with telnet localhost 25 to be sure about this. That test appears to have worked out the way that I want. IOW, that it came from local_u...@cns.cairodurham.org. This gave me some doubts. However, when I change DNS so that both atlas.cairodurham.org and cns.cairodurham.org are A records (and the reverse DNS points to atlas) and try to send email from Request Tracker again, I find that it works the way that I want. So its caused by some combination of factors which includes the CNAME and Request Tracker. (Remember, using telnet to manually build and send a message sent it as cns.cairodurham.org before the DNS changed.) Any reason I shouldn't leave the DNS like this? Also, that question about virtual hosting of several email domains was not rhetorical. How is a sysadmin supposed to configure their DNS for such a thing? Thanks, Jaime -- Network Administrator Cairo-Durham Central School District http://cns.cairodurham.org
Re: Wrong FQDN in From
Jaime Kikpole wrote: On Mon, Jul 13, 2009 at 1:47 PM, Victor Duchovnivictor.ducho...@morganstanley.com wrote: Don't use a CNAME in a mail address. Why not? After all, how would you handle vhosts if you can't send as the CNAME record? Sendmail often rewrites these. Postfix typically leaves CNAME domains alone. The OP should avoid these, but otherwise, should find out *where* along the delivery path the CNAME is replaced with the underlying name. I'm the OP. Based on the data I have, I believe that what goes into postfix uses the CNAME but what comes out is using the A record. I do have a little doubt, though, as the /var/log/maillog file shows w...@atlas.cairodurham.org connecting to postfix. If I grep cairo main.cf* and grep atlas main.cf*, I don't see anything that should be rewriting this. I just tried a test with telnet localhost 25 to be sure about this. That test appears to have worked out the way that I want. IOW, that it came from local_u...@cns.cairodurham.org. This gave me some doubts. However, when I change DNS so that both atlas.cairodurham.org and cns.cairodurham.org are A records (and the reverse DNS points to atlas) and try to send email from Request Tracker again, I find that it works the way that I want. So its caused by some combination of factors which includes the CNAME and Request Tracker. (Remember, using telnet to manually build and send a message sent it as cns.cairodurham.org before the DNS changed.) Any reason I shouldn't leave the DNS like this? Also, that question about virtual hosting of several email domains was not rhetorical. How is a sysadmin supposed to configure their DNS for such a thing? Thanks, Jaime The easy fix is don't use a CNAME in a mail address. In the distant past it was a requirement to canonicalize a CNAME in addresses. If I remember right, postfix dropped this behavior around version 2.0. Although it's no longer a requirement, some software continues to do this or old software may be in the path. For general mail sent over the internet, avoid using CNAME because you can't control when or if it will get rewritten. The hard fix is to track a message from creation and submission to transmission to delivery and find what software is changing the name and fix it. Since you've already successfully tested with telnet directly to postfix, it would seem the problem is with creation or submission. -- Noel Jones
