M. Brownsworth wrote:
MB> Ah, sorry. My procmail is doing system-wide filtering and invokes
MB> spamc. From /usr/local/etc/procmailrc:
MB>
MB> :0fw
MB> | spamc
MB>
MB> :0:
MB> * ^X-Spam-Status: Yes
MB> /var/log/spam
Ok, so why not just add a rule at the top of your procmail recipe which looks
>Suppose a recipient wanted a message that had been marked as spam by
>mistake, intercepted, and archived. Is there a way to deliver this
>specific message to the recipient, preventing it from being
>intercepted again? It would involve circumventing spamd's scanning
>this message so that it
>On Tue, 4 Jun 2002, M. Brownsworth wrote:
>
>> Ah, sorry. My procmail is doing system-wide filtering and invokes
>> spamc.
>>
>> $DEFAULT is the default used by the vanilla procmail from FreeBSD
>> 4.5's port. The default mail spool directory is /var/mail. The Perl
>> script to redeliver
On Tue, 4 Jun 2002, M. Brownsworth wrote:
> Ah, sorry. My procmail is doing system-wide filtering and invokes
> spamc.
>
> $DEFAULT is the default used by the vanilla procmail from FreeBSD
> 4.5's port. The default mail spool directory is /var/mail. The Perl
> script to redeliver runs as r
>On Tue, 4 Jun 2002, M. Brownsworth wrote:
>
>> Suppose a recipient wanted a message that had been marked as spam by
>> mistake, intercepted, and archived. Is there a way to deliver this
>> specific message to the recipient, preventing it from being
>> intercepted again?
>[...]
>> BTW, procm
On Tue, 4 Jun 2002, M. Brownsworth wrote:
> Suppose a recipient wanted a message that had been marked as spam by
> mistake, intercepted, and archived. Is there a way to deliver this
> specific message to the recipient, preventing it from being
> intercepted again?
[...]
> BTW, procmail is my
David T-G spaketh:
>% Some good info and suggestions in your reply. What do you think of
>
>Happy to help!
>
>% this brute-force approach?
>
>Hrmmm...
>
>% $cf = '/etc/mail/spamassassin/local.cf';
>% system("cp -p $cf ${cf}.tmp"); # Preserve original
>% open(CF, ">>$cf") || die "Can't open $cf
Michelle, et al --
...and then M. Brownsworth said...
%
% >...and then M. Brownsworth said...
% >%
...
% >% this message so that it can be redelivered to the user's local
% >% mailbox.
% >
% >In some recent posts there has been talk of SA automatically (that is, in
% >the default configuration)
>Michelle --
>
>...and then M. Brownsworth said...
>%
>% Suppose a recipient wanted a message that had been marked as spam by
>% mistake, intercepted, and archived. Is there a way to deliver this
>% specific message to the recipient, preventing it from being
>
>Almost certainly; anything is possi
Michelle --
...and then M. Brownsworth said...
%
% Suppose a recipient wanted a message that had been marked as spam by
% mistake, intercepted, and archived. Is there a way to deliver this
% specific message to the recipient, preventing it from being
Almost certainly; anything is possible :
>On Tue, Jun 04, 2002 at 11:54:55AM -0700, M. Brownsworth wrote:
>> Suppose a recipient wanted a message that had been marked as spam by
>> mistake, intercepted, and archived. Is there a way to deliver this
>> specific message to the recipient, preventing it from being
>> intercepted again?
Suppose a recipient wanted a message that had been marked as spam by
mistake, intercepted, and archived. Is there a way to deliver this
specific message to the recipient, preventing it from being
intercepted again? It would involve circumventing spamd's scanning
this message so that it can b
12 matches
Mail list logo
