On 1/19/11 2:10 AM, David F. Skoll wrote:
On Tue, 18 Jan 2011 23:37:07 +0100
Rolf E. Sonneveldr.e.sonnev...@sonnection.nl wrote:
I agree with you, looking at my own personal situation. However, many
mail admins (and maybe you too) are responsible for the e-mail
handling of many
Am 18.01.2011 20:41, schrieb J4:
On 01/18/2011 07:54 PM, J4 wrote:
On 01/18/2011 06:51 PM, Patrick Ben Koetter wrote:
* J4 ju...@klunky.co.uk:
This is pretty much what I would like to achieve, the reason I
decided not to use Dovecot Sieve (apart from me being incapable of
setting it.
On Tuesday, January 18, 2011, 4:59:05 AM, Warren Jr. wrote:
* Yes, we cannot be 100% sure our opt-in was only for that particular
site and not their partners. But in any case automatic ham trapped
mail will be only the mail branded by the subscribed provider, because
that is the only mail we
On 01/18/2011 11:49 PM, Jeff Chan wrote:
On Tuesday, January 18, 2011, 4:59:05 AM, Warren Jr. wrote:
* Yes, we cannot be 100% sure our opt-in was only for that particular
site and not their partners. But in any case automatic ham trapped
mail will be only the mail branded by the subscribed
Hi,
I set
use_bayes 1
bayes_auto_learn1
bayes_expiry_max_db_size30
bayes_auto_expire 1
bayes_store_module
Mail::SpamAssassin::BayesStore::SQL
bayes_sql_dsn
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
make sure you run the cronjob for each user in bayes.
mysql mail -AssBbe 'select username from bayes_vars'
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
OK...but..why? :)
make sure you run the cronjob for each user in bayes.
The database ist global...
On 1/19/11 7:56 AM, Helmut Schneider wrote:
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
OK...but..why? :)
to fix your problem.
plus auto expire can seriously degrade the performance
Michael Scheidell wrote:
On 1/19/11 7:56 AM, Helmut Schneider wrote:
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable auto expire and run a cronjob.
OK...but..why? :)
to fix your problem.
On 1/19/11 8:16 AM, Helmut Schneider wrote:
1295442708,
Last: 1295442672, atime: 0, count: 0, newdelta: 0, ratio: 0, period:
43200
or, it has been trying (automatically) for a while. remove auto expire
(at least)
change to this also
bayes_store_module Mail::SpamAssassin::BayesStore::MySQL
On Wed, 19 Jan 2011 13:16:09 + (UTC)
Helmut Schneider jumpe...@gmx.de wrote:
Michael Scheidell wrote:
On 1/19/11 7:56 AM, Helmut Schneider wrote:
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire 1
disable
Michael Scheidell wrote:
On 1/19/11 8:16 AM, Helmut Schneider wrote:
1295442708,
Last: 1295442672, atime: 0, count: 0, newdelta: 0, ratio: 0, period:
43200
or, it has been trying (automatically) for a while. remove auto
expire (at least)
done.
change to this also
bayes_store_module
RW wrote:
On Wed, 19 Jan 2011 13:16:09 + (UTC)
Helmut Schneider jumpe...@gmx.de wrote:
Michael Scheidell wrote:
On 1/19/11 7:56 AM, Helmut Schneider wrote:
Michael Scheidell wrote:
On 1/19/11 6:04 AM, Helmut Schneider wrote:
bayes_auto_expire
I recently gave up on greylisting after using it for years as well.
Two reasons really, one was the complaints from users (and I found that
they often asked folks to send mail to me twice to try and get mail to
work better and that was just embarrassing).
The second was that I've found that the
On Wed, 19 Jan 2011 09:56:47 -0500
Lee Dilkie l...@dilkie.com wrote:
The second was that I've found that the other spam-catching filtering
is doing a much better job than it was years ago and turning off
greylisting didn't adversely affect the amount of spam that got
through.
That's possibly
On 1/19/2011 10:02 AM, David F. Skoll wrote:
On Wed, 19 Jan 2011 09:56:47 -0500
Lee Dilkie l...@dilkie.com wrote:
The second was that I've found that the other spam-catching filtering
is doing a much better job than it was years ago and turning off
greylisting didn't adversely affect the
On Wed, 19 Jan 2011, Lee Dilkie wrote:
Don't get me wrong, I liked GL but there are a number of big ISPs that
have quite long retry timeouts (for some reason, sympatico comes to
mind) and it got to be too annoying.
...and when you encounter a big ISP that does this, do you notify their
On 1/19/11 10:17 AM, John Hardin jhar...@impsec.org wrote:
On Wed, 19 Jan 2011, Lee Dilkie wrote:
Don't get me wrong, I liked GL but there are a number of big ISPs that
have quite long retry timeouts (for some reason, sympatico comes to
mind) and it got to be too annoying.
...and when
The legitimate mail that passes through my mail server comes from
hosts / networks I might not hear from again for months, by which
time I have to potentially wait 24 hours for the greylisting / mail
server to try again.
I run greylisting on an email server with several thousand email
This may not be the best place to ask about this issue, but I figure I have
to start somewhere and maybe someone here has encountered it. My problem is
that SpamAssassin appears to not be performing the task of scanning my
incoming mail any longer (appears to have stopped recently). My domain
On Wed, Jan 19, 2011 at 11:14:29AM -0600, Daniel McDonald wrote:
On 1/19/11 10:17 AM, John Hardin jhar...@impsec.org wrote:
On Wed, 19 Jan 2011, Lee Dilkie wrote:
Don't get me wrong, I liked GL but there are a number of big ISPs that
have quite long retry timeouts (for some reason,
On 1/19/2011 9:25 AM, Matt wrote:
The legitimate mail that passes through my mail server comes from
hosts / networks I might not hear from again for months, by which
time I have to potentially wait 24 hours for the greylisting / mail
server to try again.
I run greylisting on an email server
On 1/19/2011 9:27 AM, jrnelli wrote:
This may not be the best place to ask about this issue, but I figure I have
to start somewhere and maybe someone here has encountered it. My problem is
that SpamAssassin appears to not be performing the task of scanning my
incoming mail any longer (appears
The legitimate mail that passes through my mail server comes from
hosts / networks I might not hear from again for months, by which
time I have to potentially wait 24 hours for the greylisting / mail
server to try again.
I run greylisting on an email server with several thousand email
On 1/19/2011 8:06 AM, Lee Dilkie wrote:
On 1/19/2011 10:02 AM, David F. Skoll wrote:
On Wed, 19 Jan 2011 09:56:47 -0500
Lee Dilkiel...@dilkie.com wrote:
The second was that I've found that the other spam-catching filtering
is doing a much better job than it was years ago and turning off
On Wed, 19 Jan 2011, Daniel McDonald wrote:
On 1/19/11 10:17 AM, John Hardin jhar...@impsec.org wrote:
On Wed, 19 Jan 2011, Lee Dilkie wrote:
Don't get me wrong, I liked GL but there are a number of big ISPs that
have quite long retry timeouts (for some reason, sympatico comes to
mind) and
On 1/19/11 2:35 PM, John Hardin jhar...@impsec.org wrote:
On Wed, 19 Jan 2011, Daniel McDonald wrote:
On 1/19/11 10:17 AM, John Hardin jhar...@impsec.org wrote:
On Wed, 19 Jan 2011, Lee Dilkie wrote:
Don't get me wrong, I liked GL but there are a number of big ISPs that
have quite
On Wed, 19 Jan 2011, jrnelli wrote:
You'll see from the SpamAssassin enabling above, the following tags are
included:
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
cloud-dimenoc.webhostdns.info
X-Spam-Flag: YES
X-Spam-Level: *
X-Spam-Status: Yes, score=5.1 required=2.5
28 matches
Mail list logo
