Re: Confirmation email caught by spam filter

Ashley Sheridan wrote: > On Thu, 2009-05-28 at 07:45 +0200, Per Jessen wrote: >> Ashley Sheridan wrote: >> >> > I've also seen this happen where the address that the mail was sent >> > from is different from the MX record for the domain the email says >> > it is sent from. The only way round this is to have the MX and A >> > records point to the same server. >> >> It's not a real problem - lots of companies have different inbound >> and outbound servers. >> >> >> /Per >> > The spam filters we use at work have this problem, not any others that > I've seen, but I was just saying it is a problem, and in a corporate > environment, not just someone with an over zealous firewall. > > Would setting up a backup MX record solve this do you think? Possibly, but it depends on how that check is done. It really ought to be fixed by the receiving end (fixed=removed). It is perfectly normal to have separate inbound and outbound mail-servers. For instance, if you're having your email filtered by an external service such as Spamchek or Messagelabs. A check on inbound mail that says it must be sent by the MX listed for the sending domain is really only going to hurt the receiving end. I personally wouldn't do anything to try to fix it from my side. /Per -- Per Jessen, Zürich (14.2°C)