Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-07 Thread Kevin A. McGrail
What a simple and useful trick! Thanks, KAM It is a good idea to do anyway, and is easy to do via a cron entry: 0 7 * * * /usr/sbin/tmpwatch -cf 168 /var/spool/MD-Quarantine This would delete any files that have not been accessed for over a week (168 hours), I run it every day at 7 am. _

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-07 Thread Steffen Kaiser
Or one can keep a report of the internal variables of the filter for a mail, e.g.: http://lists.roaringpenguin.com/pipermail/mimedefang/2004-May/022272.html Bye, -- Steffen Kaiser ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang ma

RE: [Mimedefang] How can I tell WHY this was rejected?

2005-04-06 Thread James Ebright
On Tue, 5 Apr 2005 16:22:33 -0500 , Damrose, Mark wrote > > If you go the quarantine route, you will want some > automated process to delete old messages. It is a good idea to do anyway, and is easy to do via a cron entry: 0 7 * * * /usr/sbin/tmpwatch -cf 168 /var/spool/MD-Quarantine This w

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-06 Thread James Ebright
One thing I do on all my MD installs that my mail admins love: md_syslog('info', "$QueueID: SA hits=$hits, tests=$names"); I add this in before action_change_header("X-Spam-Status" This will allow you to see exactly what tests a particular message hit on in your mail log, good or bad an

RE: [Mimedefang] How can I tell WHY this was rejected?

2005-04-05 Thread Damrose, Mark
> -Original Message- > From: Lisa Casey > > Put this before your action_bounce(): > > > action_quarantine_entire_message($report); > > Where would the message be quarantined to?? >From man mimedefang-filter: DISPOSITION ... quarantine The part is deleted and a warning is added to t

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-05 Thread Lisa Casey
Hi, Thanks for the responses on this. I have some questions about some of the responses. Matthew Von Eerde said: * Create a special email address for this kind of thing * Modify mimedefang-filter to attach a SpamAssassin report for all emails to that address See http://www.mimedefang.org/kwiki

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-05 Thread Joseph Brennan
if ($hits > 6.0) { return action_bounce("Suspected spam - blocked Please contact Netlink 2000, Inc."); Is there any way I can figure out WHY mimedefang is rejecting this e-mail so I can tell my user what he can change to keep this from happening again? Inside that if condition,

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-04 Thread Craig Green
Lisa Casey wrote: Is there any way I can figure out WHY mimedefang is rejecting this e-mail so I can tell my user what he can change to keep this from happening again? The graphdefang sub probably isn't quite meant to be used for this, but it's convenient for dumping info to the maillog. Put

Re: [Mimedefang] How can I tell WHY this was rejected?

2005-04-04 Thread Matthew Schumacher
Lisa Casey wrote: According to my user, this e-mail consists of just a jpg image in the body of the email (and when I had him send the mail using a different mail server without mimedefang/spamassassin and CC a copy of it to me so I could take a look at it, sure enough that is what I got). Is t

RE: [Mimedefang] How can I tell WHY this was rejected?

2005-04-04 Thread Matthew.van.Eerde
Lisa Casey wrote: > if ($hits > 6.0) { > return action_bounce("Suspected spam - blocked Please > contact Netlink 2000, Inc."); > > Is there any way I can figure out WHY mimedefang is rejecting this > e-mail so I can tell my user what he can change to keep this from > happening agai

[Mimedefang] How can I tell WHY this was rejected?

2005-04-04 Thread Lisa Casey
Hi, I'm using Mimedefang & Spamassassin. One of my users seems to have problems sending mail through my mail server quite often. He gets this error message: An unknown error has occurred. Subject '', Account: 'mail.jellico.com', Server: '63.162.128.2', Protocol: SMTP, Server Response: '554 5.7.1