Now one of our customers send a legit message trough our mailserver.
Your use of legit is confusing. Rephrased, an SPF TXT
record _is_ a legitimate use policy. For the purposes of an
SPF check, there is no greater arbiter of legitimacy than that record.
I specified legit in this case
Wouldn't be possible to let declude check for SPF-Records only
for incomming
messages?
Not on version 7. decluse does not know if it is a local or remote user
until Imail 8 and SMTP auth. Imail 8 indicates in the Q file it the user
authed or not not if the user is local or remote.
Kevin
Wouldn't be possible to let declude check for SPF-Records only for
incomming messages?
Not on version 7. decluse does not know if it is a local or
remote user until Imail 8 and SMTP auth. Imail 8 indicates in
the Q file it the user authed or not not if the user is local
or remote.
Guess correct me if I am wrong.
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Markus Gufler
Sent: Thursday, May 06, 2004 12:19 PM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [Declude.JunkMail] Declude and SPF
Wouldn't be possible to let
Not on version 7. decluse does not know if it is a local or
remote user until Imail 8 and SMTP auth. Imail 8 indicates in
the Q file it the user authed or not not if the user is local
or remote.
And why we can specify separate XINHEADER and XOUTHEADER lines?
That's different.
And why we can specify separate XINHEADER and XOUTHEADER lines?
That's different. XINHEADER/XOUTHEADER looks to see whether
the E-mail is incoming or outgoing (based on the
recipient(s), which is never forged). All spam is incoming;
the problem with SPF is determining if it is a local
