Re: Per-user capabilities
From: "Loren Wilton" <[EMAIL PROTECTED]>
> > However you should examine what proportion of mail nowadays, arriving
from
> > the internet, *is* addressed to multiple users in the one SMTP
> > transaction. This may appear to be a major failing, but in my
experience
> > it's just not, in real-world use.
>
> In my experience, virtually all multi-address mail that I receive (and ALL
> multi-address mail where all destinations are at the same ISP) are spam.
>
> Thus an acceptable solution would be to automatically tag all
multi-address
> mail as spam. :-)
The bigger the ISP the less true this will be. Since the most local ISP
here is two people that's a generally good rule. If the email includes
Earthlink addresses beyond the two if us it's likely spam. I'd give a
modest score to multiple addressed email in general usage. That way
ad hoc mailing lists that last a couple weeks would not get penalized
too badly.
{^_-}
Re: Per-user capabilities
> However you should examine what proportion of mail nowadays, arriving from > the internet, *is* addressed to multiple users in the one SMTP > transaction. This may appear to be a major failing, but in my experience > it's just not, in real-world use. In my experience, virtually all multi-address mail that I receive (and ALL multi-address mail where all destinations are at the same ISP) are spam. Thus an acceptable solution would be to automatically tag all multi-address mail as spam. :-) Loren
Re: Per-user capabilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Khalid Waheed writes: > SpamAssassin has all sorts of per-user capabilities, including whitelists, > rule weights, and Bayesian filtering. > But all of this stuff is totally useless in some mail servers (e.g. > SunOne messaging server), for the simple reason that being able to > process mail for multiple users simultaneously is an absolutely > critical capability, and SpamAssassin is simply not designed to offer > this capability. yep. However you should examine what proportion of mail nowadays, arriving from the internet, *is* addressed to multiple users in the one SMTP transaction. This may appear to be a major failing, but in my experience it's just not, in real-world use. Sounds like SunOne needs an interface that can cope with that. - --j. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFBh8eFMJF5cimLx9ARAgjqAJwOlA5dcZtkfdaiSYh50Q1OGWDkJwCfdWh4 AYmAeihvbFxD2b8/K1M4Rn8= =E89Z -END PGP SIGNATURE-
Re: Per-user capabilities
From: "Khalid Waheed" <[EMAIL PROTECTED]>
>
> SpamAssassin has all sorts of per-user capabilities, including whitelists,
rule weights, and Bayesian filtering.
> But all of this stuff is totally useless in some mail servers (e.g. SunOne
messaging server), for the simple reason that being able to process mail for
multiple users simultaneously is an absolutely critical capability, and
SpamAssassin is simply not designed to offer this capability.
Sh, please, not so loud. My system might hear you and get funny ideas.
{o.o}
Per-user capabilities
SpamAssassin has all sorts of per-user capabilities, including whitelists, rule weights, and Bayesian filtering. But all of this stuff is totally useless in some mail servers (e.g. SunOne messaging server), for the simple reason that being able to process mail for multiple users simultaneously is an absolutely critical capability, and SpamAssassin is simply not designed to offer this capability.
