* Michael :
> smtp inet n - n - - smtpd
>-o content_filter=spamassassin
...
> spamassassin unix - n n - - pipe
> user=spamd argv=/usr/bin/spamc -f -e
> /usr/sbin/sendmail -oi -f ${sender} ${recipient}
So the
On Tue, 2011-03-08 at 21:18 +0100, Ralf Hildebrandt wrote:
> * Michael :
> > On Tue, 2011-03-08 at 21:13 +0100, Ralf Hildebrandt wrote:
> > >
> > > You seem to have a content_filter setup. Could that be?
> >
> > Yes, SpamAssassin is in the chain. I did'nt realise this may be the
> > issue.
>
>
* Michael :
> On Tue, 2011-03-08 at 21:13 +0100, Ralf Hildebrandt wrote:
> >
> > You seem to have a content_filter setup. Could that be?
>
> Yes, SpamAssassin is in the chain. I did'nt realise this may be the
> issue.
Please show master.cf
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung
On Tue, 2011-03-08 at 21:13 +0100, Ralf Hildebrandt wrote:
>
> You seem to have a content_filter setup. Could that be?
Yes, SpamAssassin is in the chain. I did'nt realise this may be the
issue.
* Michael :
> This might be a stupid question.
>
> I have a header_check rule that puts certain mails into the HOLD queue
> for inspection by senior staff, and when its released into the deferred
> queue for delivery, it gets chucked back into the HOLD queue due to
> Postfix reapplying the Header_
This might be a stupid question.
I have a header_check rule that puts certain mails into the HOLD queue
for inspection by senior staff, and when its released into the deferred
queue for delivery, it gets chucked back into the HOLD queue due to
Postfix reapplying the Header_checks.
It does go thr
