>How does the "HELO $domain" work...
It doesn't. It's broken. It will fail the HELOBOGUS test.
>I recieved a spam complaint that had a
>bogus host at my domain as the originating host in the headers (their spam
>software connected directly to my server), but the Imail log shows "HELO
>$domain
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry
Sent: Friday, June 07, 2002 6:53 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Could you explain HELOBOGUS?
When this happens, it's a configuration error on the other end o
> > This is exactly why the test is so useful. psu.edu, for example, is a
> > perfectly valid domain, and it has an MX record.
>
>Except, at least 3 of those 5 messages are not spam.
Interesting.
>I see this in my IMail log file -
>
>06:07 16:24 SMTPD(BC3000AE) [12.20.248.130] HELO bur05.stand
on 6/7/02 3:55 PM, R. Scott Perry wrote:
>> I see the following entries in my log file -
>>
>> Msg failed HELOBOGUS (Domain engrmail1.engr.psu.edu has no MX/A records.).
>> Msg failed HELOBOGUS (Domain bur05.standardsteel.com has no MX/A records.).
>> Msg failed HELOBOGUS (Domain mail12.w-advert
>I'm getting similar messages for OUTBOUND messages from users of my own
>domain.
That should only happen if:
1. They are sending mail from non-local addresses, and
2. You use the HELOBOGUS test for outgoing E-mail (in the global.cfg file), and
3. Their mail is being sent with a bogus HELO name
>Could you explain HELOBOGUS?
It is a new test to verify that the hostname supplied in the HELO/EHLO SMTP
command is not bogus. From what we have heard recently, a bogus hostname
in the HELO command indicates spam about 99% of the time. The HELO
hostname must either have a DNS MX record or
I'm getting similar messages for OUTBOUND messages from users of my own
domain.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Helpdesk
Sent: Friday, June 07, 2002 3:42 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] Could you explain HELOBOGUS?
S
