[Mimedefang] How to pass custom headers to spamassassin?

2005-02-10 Thread Enrico Scholz
Hi, does there exist a way to create custom headers which are evaluated by SpamAssassin? E.g. I have | action_add_header(X-FOO, 'bar') if something in my filter_begin(). Then I have a SpamAssassin rule which checks for this header and scores the message accordingly. Unfortunately, this

Re: [Mimedefang] How to pass custom headers to spamassassin?

2005-02-10 Thread Jan Pieter Cornet
On Thu, Feb 10, 2005 at 12:29:24PM +0100, Enrico Scholz wrote: does there exist a way to create custom headers which are evaluated by SpamAssassin? E.g. I have | action_add_header(X-FOO, 'bar') if something in my filter_begin(). Then I have a SpamAssassin rule which checks for this

[Mimedefang] Clam AV Question

2005-02-10 Thread Mark Penkower
When running freshclam, I get the message: WARNING: Your ClamAV installation is OUTDATED - please update immediately! WARNING: Current functionality level = 3, required = 4 I am running: X-Virus-Scanned: ClamAV 0.80/562/Fri Oct 29 08:39:45 2004, clamav-milter version 0.75c What does the version

Re: [Mimedefang] How to pass custom headers to spamassassin?

2005-02-10 Thread David F. Skoll
On Thu, 10 Feb 2005, Jan Pieter Cornet wrote: It would be nice if there was a standard way to pass custom headers to SpamAssassin... There is... re-write ./INPUTMSG. :-) I'm reluctant to make this easy to do, because attackers can insert the custom headers before they send mail, and if

Re: [Mimedefang] Clam AV Question

2005-02-10 Thread Rob MacGregor
On Thu, 10 Feb 2005 11:03:08 -0500, Mark Penkower [EMAIL PROTECTED] wrote: When running freshclam, I get the message: WARNING: Your ClamAV installation is OUTDATED - please update immediately! WARNING: Current functionality level = 3, required = 4 I am running: X-Virus-Scanned: ClamAV

[Mimedefang] SECURITY: Flaw in MIMEDefang = 2.50

2005-02-10 Thread David F. Skoll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, all. I've discovered a bug in MIMEDefang versions up to 2.50. (2.51 is fixed.) The bug is a theoretical vulnerability only; I don't believe it's exploitable. Nevertheless, I suggest upgrading to 2.51 just to be prudent. A full description of

[Mimedefang] discarding messages that are sent to addresses with [ or ] characters in them.

2005-02-10 Thread Tom Hodder
Hi, I have a filter in filter -- Tom Hodder e:[EMAIL PROTECTED] Technical Consultantm:0797 975 1734 ECNOW LTD f:0208 880 9273 Email, Messaging Directory Services http://www.avmailscan.co.uk ___ Visit