 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
11 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Deleting an email in ...| From | Sent On | Attachments |
|---|---|---|
| Timothy Ha | Apr 13, 2006 4:07 am | |
| Devin Rubia | Apr 13, 2006 6:36 am | |
| Timothy Ha | Apr 13, 2006 6:49 am | |
| Jay Lee | Apr 13, 2006 7:12 am | |
| mouss | Apr 14, 2006 3:40 am | |
| Clive Dove | Apr 14, 2006 5:55 am | |
| Jay Lee | Apr 14, 2006 8:16 am | |
| Clive Dove | Apr 14, 2006 9:13 am | |
| Jay Lee | Apr 14, 2006 10:16 am | |
| Clive Dove | Apr 14, 2006 1:02 pm | |
| mouss | Apr 14, 2006 1:48 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [maildropl] Deleting an email in maildrop after virus checking | Actions... |
|---|---|---|
| From: | Clive Dove (chd...@rogers.com) | |
| Date: | Apr 14, 2006 1:02:41 pm | |
| List: | net.sourceforge.lists.courier-maildrop | |
On Friday 14 April 2006 13:14, Jay Lee wrote:
Clive Dove wrote:
On Friday 14 April 2006 10:37, Jay Lee wrote:
Clive Dove wrote:
The above code is preceeded by a routine that sends cooker mailing list messages directly to the default mailbox. This is because cooker is a high volume mailing list which I don't want to feed through spamassassin.
I had posted a message to this list respecting whether it would work to have set the exitcode to 553. The fetchmail man page states that smtp return code 553 would cause fetchmail to remove the message with the server without any attempt at bouncing it.
I received no reply so I went with simply returning exitcode 0 so that fetchmail would treat the message as having been delivered.
I would have preferred the other return code in the hope that I could get the fetchmail log to leave a trail for any rejected messages. The .maillog file does not leave such a trail.
You're confused. The SMTP code has nothing to do with the maildrop code. By the time maildrop sees the message and begins filtering the server has long since accepted the message and either closed the SMTP connection or moved on to other messages.
Jay
Thank you.
I had been under the impression that fetchmail did not accept or reject the messag until it had gotten a zero code either from the local smtp listener or in the absence of a local smtp listener (as in my system) a return code from an MDA such as maildrop and that it was therefor able to either purge or otherwise deal with the message depending on the return code.
So as an alternative question: Is there a way for maildrop to leave a trail in a log file when it uses "exit" to blackhole a message?
I think your still confused. Maildrop is not an MDA (Mail Delivery Agent), it is a LDA (Local Delivery Agent). It is responsible for taking the spool and delivering it to the user's mail folder on the server. In the process, it runs the filters which determine where the message should go.
What exactly are you trying to do (big picture)?
Jay
I am using spamassassin to filter for spam and KMail to read my mail.
KMail freezes while processing a message through spamassassin so I have moved spamassassin upstream to maildrop and am using fetchmail to fetch the mail and send it through maildrop. fetch mail runs as a cron job every 6 minutes.
The mail is handed off to maildrop by adding"mda maildrop" in .fetchmailrc.
In maildrop, I divert any mail for the cooker mailing list to the default mailbox then filter the rest through spamassassin which puts the spamassassin headers into the messages then I have maildrop use exit to remove any message that spamassassin has given a spam weight of 10 or more. The whole .mailfilter file is as follows:
QUOTE{
HOME=/home/chd DEFAULT=/var/spool/mail/chd logfile "$HOME/.maillog"
if(/^List-Id:.*mandrivalinux\.org>/) { to $DEFAULT }
xfilter "/usr/bin/spamassassin"
if(/^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*/) { EXITCODE = 0 exit }
}END QUOTE
KMail then puts any spam having a weight between 5 and 10 into a spam folder and assigns the rest of the mail to folders according to the type or source of the message as picked up from the headers. That way, any delays in processing the mail occur in the background and KMail works without hanging when I want to see and reply to my mail.
The setup seems to work well except that that any messages that get killed leave no trails in the maillog file.
Note that this is specific to only one user (me). My son uses thunderbird in his account and he is content to use the ISP's junk mail filter instead. He gets a lot higher percentage of uncaught spam than I do bu is prepared to tolerate it.
I contemplated using postfix instead but it seemed that it would be using a pile driver to crack walnuts and I could see no benefit to justify the added complexity. I am trying to keep it simple so I do not have postfiix or exim running.
Clive