>On Thu, Jan 22, 2015 at 3:06 PM, Jeff Potter <[email protected]> >wrote: >> The other issue: a sending server can resolve the CNAME and rewrite the >> address on you. I saw this years ago. >> >> E.g.: >> >> foo.com with a CNAME of “bar.com” >> foo.com with an MX of “some-good-mailserver.example.com”
On 22.01.15 19:23, Jan Ingvoldstad wrote: >Well, this is in direct violation of the DNS specification for CNAME. When >foo.com is a CNAME, it CANNOT have any other records, so the behaviour of >that MX record is undefined, whether it breaks in the way you describe or >foo.com simply won't resolve, is too risky to rely on. I believe that was supposed to be: foo.com with a CNAME of “bar.com” I have also seen the mailserver to rewrite the domain when CNAME was found, unrelated to other records... -- Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 2B|!2B, that's a question! ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
