asked on

MDaemon, 554 Message is not RFC compliant

My MDaemon server is blocking mail alerts from my bank institution because they are not RFC compliant.

Where can I tell my server to alow this messages?

If i recive this messages on hotmail they arrive perfectly.

Thanks for your help.

Fri 2008-08-15 10:23:04: ----------
Fri 2008-08-15 10:23:06: Session 1381; child 5; thread 2964
Fri 2008-08-15 10:22:55: Accepting SMTP connection from [xxx.xxx.xxx.xxx:59810]
Fri 2008-08-15 10:22:55: Performing PTR lookup (71.43.244.148.IN-ADDR.ARPA)
Fri 2008-08-15 10:22:55: * D=xx.xx.xxx.xxx.IN-ADDR.ARPA TTL=(720) PTR=[host-xxx-xxx-xx-xx.block.alestra.net.mx]
Fri 2008-08-15 10:22:55: * Gathering A records...
Fri 2008-08-15 10:22:55: * D=host-148-244-43-xx.block.alestra.net.mx TTL=(720) A=[xxx.244.xx.71]
Fri 2008-08-15 10:22:55: ---- End PTR results
Fri 2008-08-15 10:22:55: --> 220 internetmovil.com.mx ESMTP MDaemon 9.6.3; Fri, 15 Aug 2008 10:22:55 -0500
Fri 2008-08-15 10:22:55: <-- EHLO gfbemail3.bbva.bancomer.com
Fri 2008-08-15 10:22:55: Performing IP lookup (gfbemail3.bbva.bancomer.com)
Fri 2008-08-15 10:22:55: * Error: * Name server reports domain name unknown
Fri 2008-08-15 10:22:55: ---- End IP lookup results
Fri 2008-08-15 10:22:55: --> 250-internetmovil.com.mx Hello host-xx-244-xx-71.block.alestra.net.mx, pleased to meet you
Fri 2008-08-15 10:22:55: --> 250-VRFY
Fri 2008-08-15 10:22:55: --> 250-EXPN
Fri 2008-08-15 10:22:55: --> 250-ETRN
Fri 2008-08-15 10:22:55: --> 250-AUTH=LOGIN
Fri 2008-08-15 10:22:55: --> 250-AUTH LOGIN CRAM-MD5
Fri 2008-08-15 10:22:55: --> 250-8BITMIME
Fri 2008-08-15 10:22:55: --> 250 SIZE 0
Fri 2008-08-15 10:22:55: <-- MAIL FROM:<alertatdu@serviciobancomer.com> SIZE=5840
Fri 2008-08-15 10:22:55: Performing IP lookup (serviciobancomer.com)
Fri 2008-08-15 10:22:56: * P=010 S=000 D=serviciobancomer.com TTL=(180) MX=[mail.serviciobancomer.com]
Fri 2008-08-15 10:22:56: ---- End IP lookup results
Fri 2008-08-15 10:22:56: --> 250 <alertatdu@serviciobancomer.com>, Sender ok
Fri 2008-08-15 10:22:56: <-- RCPT TO:<xxxxxxx@grupohabita.com.mx>
Fri 2008-08-15 10:22:56: xxxxxx@grupohabita.com.mx is an alias for xxxxx@grandhabita.com
Fri 2008-08-15 10:22:56: Performing DNS-BL lookup (148.244.43.71 - connecting IP)
Fri 2008-08-15 10:22:58: * zen.spamhaus.org - passed
Fri 2008-08-15 10:22:58: * bl.spamcop.net - passed
Fri 2008-08-15 10:22:58: ---- End DNS-BL results
Fri 2008-08-15 10:22:58: --> 250 <xxxx@grupohabita.com.mx>, Recipient ok
Fri 2008-08-15 10:22:59: <-- DATA
Fri 2008-08-15 10:23:01: Creating temp file (SMTP): d:\mdaemon\queues\temp\md50000078348.tmp
Fri 2008-08-15 10:23:01: --> 354 Enter mail, end with <CRLF>.<CRLF>
Fri 2008-08-15 10:23:01: Message size: 5831 bytes
Fri 2008-08-15 10:23:01: --> 554 Message is not RFC compliant
Fri 2008-08-15 10:23:06: <-- QUIT
Fri 2008-08-15 10:23:06: --> 221 See ya in cyberspace
Fri 2008-08-15 10:23:06: SMTP session terminated (Bytes in/out: 5973/467)

jar3817

It's really scary that a legit bank would have email servers setup like this. The reverse DNS on their mail server looks like some dynamic residential computer: host-148-244-43-xx.block.alestra.net.mx. That right there would cause any of my servers to reject the mail as spam.

Then they give a rather specific but invalid EHLO name:
Fri 2008-08-15 10:22:55: <-- EHLO gfbemail3.bbva.bancomer.com
Fri 2008-08-15 10:22:55: Performing IP lookup (gfbemail3.bbva.bancomer.com)
Fri 2008-08-15 10:22:55: * Error: * Name server reports domain name unknown

This is most likely the cause of your server rejecting the mail. The RFC says they have to give a valid hostname in the HELO/EHLO stage, and they don't.

To ensure you receive their mail, I would say you can whitelist either the domain of the FROM address "serviciobancomer.com" or the IP range of the bank itself: 148.244.0.0/16

lyanez30

ASKER

Do you know a way of whitelisting it in MDaemon?,

ASKER CERTIFIED SOLUTION

jar3817

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial