[EMAIL PROTECTED] wrote:
Rick Macdougall wrote:
Is it possible to do anything about local users that are listed in
RBL's ?
Use SMTP AUTH, and bypass SpamAssassin checks on authenticated sessions?
Heh, with 20K high speed users we need to scan the outgoing mail for
spam and viruses or else we get listed in spamcop daily. So that option
is out the door.
The listing is correct but I don't really want mail sent
to us from our users to be marked as spam
You need to find a way to be sure it's really from your user and not just
spoofed (hence AUTH)
(I know it wouldn't have if the date on the computer was set correctly
but in this case it's my mother.)
Fix her clock :)
Hey, it's my Mother, her VCR clock is covered in black electrical tape
:) Plus she lives 600 km's away.
X-Spam-Report:
* 1.0 SUBJ_ALL_CAPS Subject is all capitals
* 2.8 DATE_IN_FUTURE_12_24 Date: is 12 to 24 hours after Received:
date
* 0.1 HTML_50_60 BODY: Message is 50% to 60% HTML
* -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
* [score: 0.0000]
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP
address
* [216.221.34.10 listed in dnsbl.sorbs.net]
* 1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
* [216.221.34.10 listed in combined.njabl.org]
I suppose you could zero out the scores for the RCVD_IN_*_DUL rules...
Yah, that's not an option either, I'll look into Matt's suggestion of
trusted and internal networks.
Thanks for the reply though.
Regards,
Rick
