I've been rejecting bad HELO's for a couple of years now. I'm glad to see others are finally catching on! Its a HUGE boost in not only blocking very obvious spam, but also stops the spam extremely early during the blocking process - taking less time, effort, resources, etc.
On Wed, Aug 27, 2008 at 3:00 PM, <[EMAIL PROTECTED]> wrote: > Greetings, again... > > I just got a reply from AT&T. They said the problem probably lies in the > HELO statement in the header. (Unfortunately, I am not the Notes > administrator, but...) > > Our Notes server is in a private network (napcc.aspca.int), so that is the > domain presented in the HELO statement. Reverse lookups find the IP > address, but it does not resolve to "napcc.aspca.int" but rather to > "mwro.aspca.org". > > Do messaging servers such as Notes or Exchange have a setting so that it > identifies itself other than with its local network name? I'm sure the > "internal to external" situation I have is far from unique. > > Thanks! > -------------------------------------- > Richard McClary, Systems Administrator > ASPCA Knowledge Management > 1717 S Philo Rd, Ste 36, Urbana, IL 61802 > 217-337-9761 > http://www.aspca.org > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > -- ME2 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
