Just an fyi - We use the 'send all mail to relay' feature and our relays show that the server always connects from the primary imail IP and the HELO/EHLO is the OHN configured in IMail.
In order to satisfy your client and get the mail delivered, consider building a cheap (i.e. free) relay using a spare machine. Nothing spectacular is needed. Len has put together some excellent info regarding this. I think the site is imgate.meiway.com. If not, search the archives for 'imgate' Regards, David Gregg dgSoft Internet Services Web hosting, Email outsourcing, Dedicated and shared infrastructure solutions. (949) 584-1514 ----- Original Message ----- From: "R. Scott Perry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 15, 2003 6:32 AM Subject: Re: [IMail Forum] PTR record for a virtual IP > > ><That's not a problem. No decent mailserver or anti-spam program will > >complain if the EHLO/HELO does not match the PTR.> > > > >But some are starting to do just that (supanet.com). > >what if this practice become more widely used ? > > Then don't send mail to them. The RFCs say they can't block your mail even > if your EHLO/HELO is invalid. But yours is 100% valid! > > The problem is on their end. If supanet.com is doing this, it is their > problem. > > >Shouldn't IPSWITCH add an option to let us define what ehlo should be used > >with VD? > > It would be nice if they did. But it won't solve the problem -- tomorrow, > it will be something else. Supanet's competitor will say "Reverse DNS > entries must have the word MAIL in them". Then Supanet will say "Too much > spam is coming from EHLO/HELO's that have 'mail' in them -- we're going to > reject such mail." Now you can't send E-mail to both Supanet and their > competitor. > > When someone chooses to require something silly in order to send them > E-mail, you have to make a judgement call. Are you willing to switch > mailservers because of some bozo that doesn't understand how mail > works? What happens when you switch mailservers, but then there is a new > requirement that the new mailserver won't handle? > > This is the problem with trying to make new rules for an old game. For the > same reason that we can't easily come out with "SMTP2" that has controls to > minimize spam, people can't start making new assumptions unless there are > very good reasons behind them, and the requirements are within > reason. Requiring the EHLO/HELO to match the PTR is plain silly. It may > work well in a weighted system (making it more likely that the E-mail will > be marked as spam), but not for outright rejections. > > Somewhere you have to draw the line as to what hoops you will be willing to > jump through to get other people to read your mail. > > -Scott > --- > Declude JunkMail: The advanced anti-spam solution for IMail mailservers. > Declude Virus: Catches known viruses and is the leader in mailserver > vulnerability detection. > Find out what you've been missing: Ask about our free 30-day evaluation. > > --- > [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] > > > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html > List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ > Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
