> "Arley" == arc <[EMAIL PROTECTED]> writes:
Arley> I ran into this problem trying to build cyrus 2.1.3 on
Arley> Freebsd-4.5 p2. Anybody has anybody had any better success
Arley> than I ?
Here's the changes I made to get it to build on FreeBSD 4.5-RELEASE:
diff -c -r cyrus-im
> "David" == David Fuchs <[EMAIL PROTECTED]> writes:
David> It seems that I'm missing a library that contains a
David> required function called fdatasync(). `configure' checks
David> for the existence of this function in -lrt, but doesn't
David> find it (I have no librt.so).
> "Rob" == Rob Siemborski <[EMAIL PROTECTED]> writes:
Rob> We are testing a combination of SpamAssassin and MimeDefang
Rob> here at CMU, where we just tag spam with a header and allow
Rob> people to use sieve to do what they will with the resulting
Rob> messages.
I've written
I've gotten a handful of requests for the "spam" sieve extension I
mentioned yesterday. The diffs aren't too big, so I'll post them to
the list.
The diffs add a test to sieve that passes the message to SpamAssassin.
If SpamAssassin scores the messages as spam, the test fails, otherwise
the test
> "Jeremy" == Jeremy Howard <[EMAIL PROTECTED]> writes:
Jeremy> Neat. Our approach is to use a Postfix content filter. It
Jeremy> checks the recipients against a DB to see if anyone have
Jeremy> spam protection turned on, and if one does then it adds
Jeremy> the SpamAssassin h
> "Scott" == Scott Lamb <[EMAIL PROTECTED]> writes:
Scott> My question: How do I find out the SMTP client's IP
Scott> address? I hoped to see this in the envelope stuff, but I
Scott> don't. Nothing else seems to use it. I know Postfix makes
Scott> this information available in
> "Hein" == Hein Roehrig <[EMAIL PROTECTED]> writes:
Hein> - From the operational point of view, the only advantage of a sieve
Hein> extension is that at this point of delivery, Cyrus knows exactly
Hein> whether the recipient exists, who it is, whether it is over quota
Hein> e
> "Jeremy" == Jeremy Howard <[EMAIL PROTECTED]> writes:
Jeremy> Doing it in a content_filter lets you add headers that you
Jeremy> can then handle in Sieve scripts on a per-user basis,
Jeremy> which is faster and cleaner.
Would it really be faster?
I haven't played with Postfix
> "Marc" == Marc G Fournier <[EMAIL PROTECTED]> writes:
Marc> I've thought to modify the code, to extend the spam
Marc> extension, so that it adds a simple:
Marc> X-Spam-Score: /
Marc> so that if spam is enabled, then it auto-adds this header,
I thought about doing somet
