[TriLUG] REQUEST: Spam notifications

Aaron Schrab via TriLUG trilug at trilug.org
Tue Mar 26 10:28:31 EDT 2019


At 10:13 -0400 26 Mar 2019, Mauricio Tavares via TriLUG <trilug at trilug.org> wrote:
>On Tue, Mar 26, 2019 at 10:04 AM Matt Flyer via TriLUG
><trilug at trilug.org> wrote:
>>
>> Is the server configured to send them on regardless of the SPAM score?

Not exactly. There's a range of spam score for which messages will be 
tagged as likely spam, but still passed on. Above that range they'll 
instead be rejected or discarded.

>> If so, and if this is the desired functionality, you could consider
>> using a Sieve filter on the receiving end to put them in a SPAM folder
>> or even directly into the circular file.

The updated version of the TriLUG mail server is likely to allow users 
to setup sieve filters on their account to send messages flagged as spam 
to a separate folder or to /dev/null.

>> In a multi user situation, it is probably best to err on the side of
>> caution and pass on messages labeled as SPAM, arguing that it is better
>> to pass on questionable messages than to reject one that is valid.

Indeed.

>      Also, trilug at trilug.org is a mailing list, not an email account.
>IMHO, it makes sense to tag spam and then let each member's mail
>application decide how to handle tagged spam. To quote a certain
>newspaper, "we inform, you decide."

I believe what's under discussion here is messages to user mail 
accounts, not ones to the list. Spam making it through to the list is 
quite rare. First, the list only allows messages from members; although 
some spammers will get past that by forging their sender address.  
Second, the same discarding of high-scoring spam applies to messages to 
the list. Third, messages that are flagged as spam by the filter will be 
discarded by the list software.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 549 bytes
Desc: not available
URL: <http://www.trilug.org/pipermail/trilug/attachments/20190326/573cec35/attachment.pgp>


More information about the TriLUG mailing list