-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/18/09 12:00, quoth Michael Scheidell:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> SA + spamass-milter + sendmail
>>
>> I have spamass-milter set to reject during reception if the score is too
>> high.
>> What I'd like to have happen is for the rejected mail to be automatically
>> reported to spamcop.
> If you have a valid spamcop_from and spamcop_to address, any email that is
> then piped to 'spamassassin --report (or -r)' will initiate a smtp (over
> port 587 I think) connection to spamcop's mail servers.
>
> You will then get an email back with a link to the pre-formated report,
> ready for you to confirm url's and that this is spam.
>
> To facilitate this, you would need to get your mta (and possibly postfix) to
> send the full email (with untouched headers, not as an attachment) to
> spamassassin --report.
>
> This will also send to any other reporting facility you have enabled, like
> DCC, razor or pyzor.
>
> If you just want to send to spamcop, then just fwd the email to the
> spamcop_to address.
>
>
Right. And that's just what I *don't* want to do. I'm running a milter and I
want all messages that pass through spamassassin that exceed the threshhold to
automatically be processed a la -r. IOW, I *really want* my invocation of spamc
to really be
spamc || spamassassin -r
- From a process structure perspective, it looks like this:
sendmail
\
\---spamass-milter
\
\---spamc
I can configure SA anyway you tell me to, but I don't see any other access
except via whatever options are available.
Anyone?
I do *not* want all the spam that gets rejected to not be reported to spamcop.
Is there a way for SA to do this?
- --
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkpiD7wACgkQRIVy4fC+NyRZ+ACfRArqEOvTy5YAz6rqVLIq9Bj8
Bn0AnifD3b0Dl6KuKoQk7A+sbK6G9tBw
=TCX6
-----END PGP SIGNATURE-----
