Now here's an interesting thing.
I received this email twice - once sent to squirrelmail list and once sent
directly to me. No problems so far, obviously the sender sent the email
twice.
The interesting thing is that it got picked up as SPAM by by (probably
incorrectly configered) spamassassin in
Seth Randall said:
> Matt,
> I just took a look at the email you sent earlier in the week. All of the
> spamassassin tests that your example failed were tests on the Recieved
> line (hence the RCVD_IN test names). A brief (and not hugely thorough
> look) at the Spamassassin source doesn't turn up
Matt,
I just took a look at the email you sent earlier in the week. All of the
spamassassin tests that your example failed were tests on the Recieved
line (hence the RCVD_IN test names). A brief (and not hugely thorough
look) at the Spamassassin source doesn't turn up any tests against a IP
addre
On Wed, 7 Apr 2004 [EMAIL PROTECTED] wrote:
> Whitelists that are address based are more insecure. It is not cheating at
> all. The purpose of the DYNALIST feature in SORBS and others to detect large
> bulk-spammers that hail form dynamic IPs that can't be easily shut-down.
> Email from SquirrelM
Tomas Kuliavas said:
>>> SquirrelMail 1.4.3cvs adds User-Agent and X-Mailer. By doing it
>>> SquirrelMail risks to get +40 points in some German SA installs.
>>> SquirrelMail 1.5 adds only User-Agent: header. SquirrelMail 1.4-STABLE
>>> will keep both headers until SA stable version with 20_head_t
Whitelists that are address based are more insecure. It is not cheating at
all. The purpose of the DYNALIST feature in SORBS and others to detect large
bulk-spammers that hail form dynamic IPs that can't be easily shut-down.
Email from SquirrelMail is just not the case - it is a single user sendin
No,It seems SquirrelMail adds the dialup IP as part of the msgid.
SpamAssassin is parsing that IP from the msgid and flagging it as spam
because of dialup. I posted a message about this a couple of days ago,
but no-one gave a decent response.
I have grep'd/awk'd through my maillog and it seems t
>> SquirrelMail 1.4.3cvs adds User-Agent and X-Mailer. By doing it
>> SquirrelMail risks to get +40 points in some German SA installs.
>> SquirrelMail 1.5 adds only User-Agent: header. SquirrelMail 1.4-STABLE
>> will keep both headers until SA stable version with 20_head_tests.cf
>> bugfix is relea
Tomas Kuliavas said:
>> Big subject line but what the heck.
>>
>> When I send email from SquirrelMail to friends who use spamassassin
>> it gets marked as spam.
>
>> 2.0 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
>> [xx.xx.xx.xxx listed in dnsbl.sorbs
> Big subject line but what the heck.
>
> When I send email from SquirrelMail to friends who use spamassassin
> it gets marked as spam.
> 2.0 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
> [xx.xx.xx.xxx listed in dnsbl.sorbs.net]
> 2.5 RCVD_IN_DYNABLOC
Big subject line but what the heck.
When I send email from SquirrelMail to friends who use spamassassin
it gets marked as spam.
Example:
(IPs and usernames xed out to protect my interests)
Content analysis details: (5.4 points, 5.0 required)
pts rule name description
--
11 matches
Mail list logo
