helpSpamAssassin Milter Plugin - Support: sr #105475, -r discard instead of reject?

 
 

sr #105475: -r discard instead of reject?

Submitted by:  None
Submitted on:  Mon 24 Jul 2006 09:52:10 PM UTC  
 
Category: NonePriority: 5 - Normal
Severity: 1 - WishStatus: None
Privacy: PublicAssigned to: None
Originator Email: -unavailable-Open/Closed: Open
Operating System: None

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 24 Sep 2008 10:20:18 PM UTC, comment #5:

> we are getting lots of spam, bounces from forged From: header.
> Which is in turn identified as spam and rejected to the
> spammer's victim, once again. So this affects the
> spammer's victim server once again.


Then something is misconfigured. Bounces MUST be sent with MAIL FROM <>, to prevent exactly these kinds of loops.
Also, there is a SpamAssassin module to detect bounces from mails which you didn't send (however, that mis-classifies, too, e.g. bugzilla mails are misdetected as bounced).

Ben Bucksch <benb>
Wed 24 Sep 2008 10:17:15 PM UTC, comment #4:

As people said, you can easily redirect mail via -B or -b to null@hostname, then aliases null: /dev/null.

BUT that is a very bad idea. There will be false positives, and you must not discard ham. In some countries, that can get you in jail (discarding mail or communication is a criminal offense). It may not matter either that it's a company account. Even if you use your server only personally, it's extremely disrespectful to the sender.

Ben Bucksch <benb>
Fri 17 Aug 2007 08:00:31 PM UTC, comment #3:

I am looking for the exact same feature. The reason being, we are getting lots of spam, bounces from forged From: header. Which is in turn identified as spam and rejected to the spammer's victim, once again. So this affects the spammer's victim server once again.

Anonymous
Tue 19 Sep 2006 08:02:36 PM UTC, comment #2:

I would concur on the addition of this option.

To currently bypass this issue, what would be the best to do?

I just would like all email tagged to be deleted.

I couldn't figure out the best way to handle the deletion of email to a local mbox.

Mark Burleson <mburleson>
Mon 24 Jul 2006 10:01:28 PM UTC, comment #1:

Ah. Obviously I could do something like

-B 'spamhandler@mydomain.com'

and then build procmail recipies. However -B doesn't allow me to specify a threshold and some users want to parse through their own potential spam.

Ideally I'd like to be able to say:

If threshold is >=X just discard it;

I could probably achieve this by using a combination of spamass-milter and milter-regex but its more elegant to just use spamass-milter I think.

Anonymous
Mon 24 Jul 2006 09:52:10 PM UTC, original submission:

Anyway I can set a flag similar to the -r flag that will discard mail instead of rejecting it? Here's my rational:

1. A good spamming program will see the reject and may try to recraft spam around my rulesets;
2. Users who are subscribed to mailing lists (such as those hosted by yahoo.com) start having problems if the server rejects/bounces too many messages.

I'd rather just send back a quick "accepted, thank you" and just discard the email if its over X threshold.

Please consider this request for a future release.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by benb (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup