Mike Diehl <[EMAIL PROTECTED]> writes:
> I have it partially working by having procmail call spamassin and by calling
> tmda via .forward. However, this leads to some strange behavior. The
> original message passes through SA, so the confirmation message has the
> spamassassin markings on it, but the final message does not. That's not what
> I want.
That's odd, since if SA sees the message before TMDA does, the version
TMDA stores in pending/ will have the SA header field(s). That's the
version that gets re-injected once it is confirmed.
How is procmail being called on your system?
> So I thought I'd have both SA and tmda called from /etc/procmailrc. This
> leads to these errors:
>
[...]
> File "/usr/src/tmda/tmda-0.62/bin/tmda-rfilter", line 160, in ?
> raise Errors.MissingEnvironmentVariable('SENDER')
> MissingEnvironmentVariable
Which MTA are you using? /etc/procmailrc is processed before
~/.procmailrc, so if you're using Sendmail, you need to have the
procmail code that sets the SENDER, RECIPIENT and EXT environment
variables in /etc/procmailrc, before TMDA is called.
> Here is the /etc/procmailrc file, with the call to tmda commented out for now:
>
> :0fw
> | spamassassin -P -F1
>
> #:0fw
> #|/usr/src/tmda/tmda-0.62/bin/tmda-filter.pl
^^
Perl? Also, tmda-filter is not a filter, in UNIX parlance. There is
no output on stdandard out. The 'f' flag may confuse procmail.
Tim
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
