On Wed, Jan 22, 2003 at 09:38:31PM -0500, Matthew S. Crocker wrote: > > Hello, > > I run an ISP, we have a 4 machine cluster running qmail-ldap with > SpamAssassin and Virus scanning. Normally I block inbound port 25 traffic > going to my dedicated bandwidth (t1, DSL..) customers. I set the > customers domain MX record to point to my mailserver. I then scrub the > mail and forward to their real mail server (normally exchange). > > I have one customer who is complaining about lost mail. They have a > support department sending them e-mail from a machine which has a forward > and reverse A/PTR combo but no MX record. The domain has no MX record as > well. Our mail server is configured with RETURNMXCHECK which is failing > and sending the error back to the sender. > > My customer is not bitching at me to remove the check. The company says > their mail server is configured properly. They list a bunch of RFCs they > are in complance with. What ammunition do I have to tell my customer > that what I'm doing is valid. I don't want to remove the checks but I > would like to get the mail working. I'm assuming that this sender is > having trouble mailing to everyone else that checks return MX records. > > The sending domain is 'intergralis.com' no MX records but does have A > records. >
Turn of RETURNMXCHECK for IP 64.225.154.175 in the tcpserver cdb. Then this specific domain can send mails to you even if they dont have a MX. This is the fast and easy fix. The hard way is to patch qmail-smtpd to accept A and MX dns entries. It is useful to check if the return/sender address domain exists. So we should check for a MX or a A dns entry. This would solve many of those errors with the problem, that probably to many mails get accepted. I will think about it. -- :wq Claudio
