On Mon, 24 Feb 2003, D. Höhn wrote:
> Hello.
>
> I am using sedmail + sophos + MailScanner 4.12-2 + Spamassassin.
>
> While running on 2.44 everything was fine. I decided to upgrade to 2.50 only
> to find 768 files unscanned in the morning. I tracked things down like this.
>
> Using 2.50 the s
Bob Apthorpe <[EMAIL PROTECTED]> writes:
> One nice thing about the old body report was exactly that - it broke the
> HTML content. Very nice for HTML-only garbage read under Pegasus Mail,
> which renders HTML-only as HTML[1] whether you want it to or not.
> Corrupting the HTML body fooled Pegasus
On Mon, Feb 24, 2003 at 12:28:40PM +, Graham Murray wrote:
> > So, I was wondering, is it OK to run "sa-learn --spam" on SpamAssassin
> > marked mails (both old and new), or do I need to clean 'em up first?
>
> sa-learn will remove any Spamassassin markup before learning, so
> just submit it.
again the debug will produce the same thing but here is the output from
spamassassin --lint -D
debug: Score set 0 chosen.
debug: ignore: using a test message to lint rules
debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: u
On Mon, 24 Feb 2003 the voices made [EMAIL PROTECTED] write:
> Young whipper-snappers. When I started coding we had to enter code through
> front panel switches, and read our output on the console lights - and we
> had to replace at least three vacuum tubes per run. On the newest
> machines, we c
