[Mimedefang] A Bit of Confusion - Solved but differentproblemwith CLAMD
Rob
rob_macgregor at hotmail.com
Mon Feb 23 12:26:38 EST 2004
> -----Original Message-----
> From: mimedefang-bounces at lists.roaringpenguin.com
> [mailto:mimedefang-bounces at lists.roaringpenguin.com] On
> Behalf Of Peter A. Cole
>
> As it turns out, I had everything right as far as the clamav.sock and
> clamav.pid files go, but even though I had set this correctly in
> mimedefang.pl.conf, mimedefang.pl actually has a hard coded entry that
> overrides this and tries to access clamd.sock in
> /var/spool/MIMEDefang/clamd.sock.
>
> This is what was causing the grief and after changing this to
> /var/run/clamd.sock it now works like a bought one!
Odd, I made my change to mimedefang-filter and it worked:
$ClamdSock = "/var/run/clamav/clamd";
> The only hassle I have now is that spam gets sent to my
> maildrop mailbox,
> but it also still goes to the original recipient as well.
>
> I know this is a problem in my filter, but any tips as to where?
This has been discussed in the past and examples are in the archive,
however... I use the following to strip out all existing recipients, add
them in a header (in the event that it becomes relevant in future) and set
the recipient to postmaster:
# Record who it was for
action_add_header("X-Orig-Rcpts", join(", ", @Recipients));
# Remove oroginal recipients
foreach $recip (@Recipients) {
delete_recipient($recip);
}
# Send to the postmaster
add_recipient('postmaster at my.domain');
PLEASE - keep list traffic on the list. Email sent directly to me may be
ignored utterly.
--
Rob | What part of "no" was it you didn't understand?
More information about the MIMEDefang
mailing list