}
>
> The "spam" test passes the message to spamassassin's spamd. The test
> returns true iff the spamassassin score is greater than the threshold.
> This way, only users that want to use spamassassin incur the extra
> overhead.
>
> If you're interested, I can provide diffs against 2.1.3...
>
> -- Bob
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
zyk <[EMAIL PROTECTED]>, who wrote:
> On 2002.03.05 02:21:15 +0100 Sam Roberts wrote:
> > Can't you see if it's to you, and do a keep?
>
> But it's not good for threading messages:
> With this behaviour in mailboxes for group1 and group2 are no messages for
e to me, and I have
> to reply on it.
> Will it be possible in next imapd version: 2.1?
>
> Regards,
>
> Olaf Fraczyk
>
>
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
.. is this possible ?
>
>
> machineA is unknown version - telnet just reports :
> Escape character is '^]'.
> * OK i3.atat.at IMAP4 service ready
> (ps: how can I find out version of this ?)
> machineB is cyrus2.0.16
>
> thnx,
> peter
>
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
l. Every time you post, you get a dozen responses from people
who are away from work. I think it *is* important for a vacation
implementation not to be stupid.
Sam
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
Quoting Ken Murchison <[EMAIL PROTECTED]>, who wrote:
> > I'm guessing from your response that this is not the way things work?
>
> No, there are variables in Sieve. What your were reading was a syntax
> definition.
What he meant was "No, there are NO variables
nable long term fix (not that good in the short
> term, either). Has anyone come across a reasonable way to keep /dev/random
> seeded on a machine with no keyboard or mouse, or with a good alternative to
> /dev/random?
>
> Thanks for the help - John
>
> [EMAIL PROTECTED]
>
>
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
tz"
> <[EMAIL PROTECTED]>
> Sent: Thursday, July 19, 2001 4:17 PM
> Subject: Re: Vacation Sieve
>
> > It [sieve rules] should be case sensitive for the stuff on the left side
> of the
> > "@", and case-insensitive for the stuff on the right side of the "@".
--
Sam Roberts <[EMAIL PROTECTED]> (Vivez sans temps mort!)
