Benny Pedersen wrote:
POP-before-SMTP olso works with imap
only bad thing about POP-before-SMTP is that it does not work if
POP-before-SMTP user is behind a NAT ip
if a user sits behind NAT it could open relay for more then one user, that
the only reason i do not use
POP-before-SMTP
Uwe Kiewel a écrit :
The best solution would be to make your users send with SMTP-AUTH,
and
then tell whatever calls SpamAssassin to skip SA if it finds valid
SMTP-AUTH info.
I'd guess from your description, however, that you're running
SpamAssassin on delivery and not on receipt, which will
On Fri, March 3, 2006 18:56, Uwe Kiewel wrote:
Also (like Kelson said), if you don't want to scan local-domain mail
at all (NOT something I prefer myself), you can probably configure
amavisd-new or Postfix to skip mail from
these users.
POPAuth is not prefered, because a lot of clients use
Daryl C. W. O'Shea [EMAIL PROTECTED] schrieb im Newsbeitrag
news:[EMAIL PROTECTED]...
Kelson wrote:
[EMAIL PROTECTED] wrote:
User Sam and Joe has internet access via DSL with a dynamic ip
address. The mail going from [EMAIL PROTECTED] to [EMAIL PROTECTED] is
identified as SPAM because
[EMAIL PROTECTED] wrote:
User Sam and Joe has internet access via DSL with a dynamic ip
address. The mail going from [EMAIL PROTECTED] to [EMAIL PROTECTED] is
identified as SPAM because the sending ip address is the dynamic dial
up address.
The solution is twofold:
1) Don't scan outgoing mail
Kelson wrote:
[EMAIL PROTECTED] wrote:
User Sam and Joe has internet access via DSL with a dynamic ip
address. The mail going from [EMAIL PROTECTED] to [EMAIL PROTECTED] is
identified as SPAM because the sending ip address is the dynamic dial
up address.
The best solution would be to make
Hi there,
on my server, there are two mail domains hostet. Spam and virus check is done
by amavis. Amavis uses SpamAssassin 3.1 and H+BEDV Antivir in current
versions.
The administration front end for SpamAssassin is MaiaMailguard
Well, lets say the hosted domains are dom1.org and dom2.org
My
On Wednesday 01 March 2006 12:21, you wrote:
Have you tried whitelisting the problem addresses?
whitelist_from [EMAIL PROTECTED]
In this case, what happens, if a spammer fake the from and use the
whitelisted address?
Uwe
Lisa,
Hi,
Well, lets say the hosted domains are dom1.org and dom2.org
My problem is:
User Sam and Joe has internet access via DSL with a dynamic ip address.
The
mail going from [EMAIL PROTECTED] to [EMAIL PROTECTED] is identified as SPAM
because
the sending ip address is