MTo: satalkSubject: RE: [SAtalk] Re: Rule
misfires
> I'm at least partly responsible for that one, since I
forwarded (but did> not invent) the procmail recipe on which it is
based. Can you send along> the header of a legitimate juno
message?>>Here you go:Return-Pat
> I'm at least partly responsible for that one, since I
forwarded (but did> not invent) the procmail recipe on which it is
based. Can you send along> the header of a legitimate juno
message?>>Here you go:Return-Path:
<[EMAIL PROTECTED]>Delivered-To:
[EMAIL PROTECTED]Received: (qmail 28710
On Fri, 5 Jul 2002, Derrick 'dman' Hudson wrote:
> | FORGED_JUNO_RCVD:
>
> This is bugged. I rescored it to 0 when my parents' (juno) mail
> triggered it. I don't know what is wrong with that rule, but I
> dropped it from my setup.
I'm at least partly responsible for that one, since I forward
> | Here is what I found:
> |
> | DATE_IN_FUTURE_03_06: This rule misfired on an email that one of my
> | customers sent. Her date was set using Pacific Time while
> being in Eastern
> | time so her clock was set 3 hours ahead to correct the date. From my
> | experience with novice users and
On Fri, Jul 05, 2002 at 11:25:54AM -0400, CertaintyTech - Ed Henderson wrote:
| (Geocrawler is so difficult to search thru archives!).
It is horrible, isn't it? It doesn't even display threads!
| Here is what I found:
|
| DATE_IN_FUTURE_03_06: This rule misfired on an email that one of my
|
