On 09/05/2011 09:16 PM, Eric Shubert wrote:
On 09/04/2011 10:29 PM, Pak Ogah wrote:
On 09/03/11 16:13, P.V.Anthony wrote:
...

Often I hope gmail will get more strict and stop accepting emails for
not properly setup servers. This will would really make my life easier.

P.V.Anthony

I agree with this. gmail can rcvd email from sender domain that use
IP.Add.re.ss as MX record rather than MX hostname.
While other email-related applications, like Exim and ASSP can't as they
obeying the RFC

- From: http://en.wikipedia.org/wiki/MX_record
The characteristic payload information of an MX record is the fully
qualified domain name of a mail host and a preference value. The host
name must map directly to one or more address record (A, or AAAA) in the
DNS, and must not point to any CNAME records.[1]

---------------------------------------------------------------------------------

Thanks for this, Pak. For some time I've wondered where it's specified that MX records must not point to CNAME records. I see now that it's in RFC 2181, Section 10.3.

I haven't thought this through, but could it be that some services honour SPF records more than others? Even if my MX record is an IP, not an A record, but I explicitly define that IP as an acceptable sender in my SPF record, that could be helping.

eg: My MX record is X.X.X.X instead of an A record, but my SPF record in DNS explicitly states : "v=spf1 a mx ip4:X.X.X.X -all", which means I authorise sending mail from my domain's A record, my MX and also from the IP X.X.X.X but none other.

Bharath

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to