Mailman sa-exim Question
"Justin F. Knotzke" <[email protected]>
| Newsgroups | gmane.mail.exim.spamassassin |
|---|---|
| Message-ID | <[email protected]> |
Hi Sorry to be a pest again. I have a question concerning mailman and sa-exim. My mailman configuration uses: http://www.daa.com.au/~james/articles/mailman-spamassassin/ And the following happened: 2003-08-08 07:20:35 19l5IQ-0002Me-S4 SA: Debug: SAEximRunCond expand returned: '1' 2003-08-08 07:20:35 19l5IQ-0002Me-S4 SA: Debug: check succeeded, running spamc 2003-08-08 07:20:39 19l5IQ-0002Me-S4 SA: Debug: SAEximRejCond expand returned: '1' 2003-08-08 07:20:39 19l5IQ-0002Me-S4 SA: Debug: SAteergrubecond expand returned: '1' 2003-08-08 07:20:39 19l5IQ-0002Me-S4 SA: Debug: Writing message to /var/spool/exim/SAteergrube/new/[email protected]. 2o.oxd 2003-08-08 07:35:40 19l5IQ-0002Me-S4 SA: Action: teergrubed sender until full configured duration of 900 secs (hits=9.9 requir ed=4.3 trigger=5.0) 2003-08-08 07:35:40 19l5IQ-0002Me-S4 temporarily rejected by local_scan(): "Please try again later" Which of course is fine. The problem is that the message was forwarded to mailman and the spamassassin patch to mailman kicked in and had the message marked for approval. Is there a way to configure sa-exim to _not_ do this? If the message is teergrubed then I'd like the message dropped just as it does for a message destined to a regular user. Thanks J -- Justin F. Knotzke [email protected] http://www.shampoo.ca