From the lack of response to my posting I'm guessing the list is as
perplexed as I am about the problem I've described.
.\\ichelle
>To: [EMAIL PROTECTED]
>From: Michelle Brownsworth <[EMAIL PROTECTED]>
>Subject: [SAtalk] SA + procmail are blocking non-spam mail
>Date: Mon, 6 May 2002 17:03:41
Is the following line from the non-spam procmail log entry a clue?
procmail: Bypassed locking "/var/mail/mdb.lock"
Should it be able to lock my mailbox file? And what are the
implications if it can't?
.\\ichelle
>To: [EMAIL PROTECTED]
>From: Michelle Brownsworth <[EMAIL PROTECTED]>
>Subj
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
>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
>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
>
>Al
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
>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
>> int
If spamd is started with the -D switch, i.e.:
/usr/bin/spamd -d -D -F 1
...where will the debugging info be written -- to the syslog,
console, message headers, or a file somewhere?
.\\ichelle
-
Michelle Brownsworth
System Administrator
PrimeLogic Corporation
http://www.p
I'm running spamd 2.20 as root on a FreeBSD 4.5 server, with
system-wide filtering. It seems to be disregarding anything in
/etc/mail/spamassassin/local.cf. Yesterday, I added my address as
"all_spam_to [EMAIL PROTECTED]," but spamd/procmail then
subsequently filtered and intercepted numerou
Theo Van Dinter writes:
>HUPping spamd won't do anything for you, you have to fully stop/start it.
>In fact, sending it a HUP causes it to die because there's no handler
>for it.
That's too bad. It would be useful to be able to force spamd to
reread its configuration file without having to k
> > Has the possibility of
>> using the envelope headers instead been suggested to Craig Hughes?
>
>Not all mail system tells you what is the enveloppe. Unless your mail
>system has a way to include the enveloppe inside the message headers,
>then SA will not know about it.
>
>But if your goal is
Folks,
I have an odd one to report. I've been using SpamAssassin 2.20
(running as spamd) for months now without a problem. Last week, I
added a few whitelist_to and whitelist_from entries to
/etc/mail/spamassassin/local.cf, in this format:
whitelist_to *@todomain.com
Spamassassin seems to b
Theo Van Dinter says:
On Fri, Jan 10, 2003 at 08:41:43PM -0800, M. Brownsworth wrote:
> Note that it does report "USER_IN_WHITELIST_TO," but it still doesn't
add -100 to keep the score below the 5.0 threshold. Experimenting, I
Of course not, the score for USER_IN_WHITELI
Turns out "all_spam_to" was my friend. I'd still like to know why
"whitelist_to" had absolutely no effect whatsoever.
.\\ichelle
Folks,
I have an odd one to report. I've been using SpamAssassin 2.20
(running as spamd) for months now without a problem. Last week, I
added a few whitelist_to
14 matches
Mail list logo
