Hi everybody,
we have been using and enjoying spamassassin for years now, and recently
received an email abuse report/complain from an external party.
It seems that the external party is also using spamassassin in some form
in their spam filtering systems, according to the spam report header
b
On Thu, 13 May 2010 09:49:11 +1200, Jason Haar wrote:
> On 05/13/2010 01:17 AM, Timo Schoeler wrote:
> >
> > and the worst thing was that they sent no SERVFAIL but NXDOMAIN what
> > will cause a lot of bounces...
> >
> Yeah - I'd like to know what crappy DNS server they are running that
> does tha
On 05/13/2010 01:17 AM, Timo Schoeler wrote:
>
> and the worst thing was that they sent no SERVFAIL but NXDOMAIN what
> will cause a lot of bounces...
>
Yeah - I'd like to know what crappy DNS server they are running that
does that. We've had issues in the past with a New Zealand ISP whose DNS
serv
Is SA 3.3.1 no longer compatible with POPAuth? After upgrading, we're
seeing these errors in the logs:
spamd[29369]: Pseudo-hashes are deprecated at
/etc/mail/spamassassin/POPAuth.pm line 195, line 54.
spamd[29369]: plugin: eval failed: Can't coerce array into hash at
/etc/mail/spamassassin/POPAu
On Wed, May 12, 2010 at 11:31 AM, Gary Smith wrote:
>> We've found that our MyISAM tables being used with Bayes in MySQL have
>> caused some bottlenecks on our busier mail servers. We're
>> contemplating using inooDB just for the Bayes database. If MySQL will
>> only be using innoDB, does anyone h
when you get spammed by a youtube member, I like the 'report spam'
button. I hope that is actually used. Its a great idea.
However, I would also like a 'don't ever, evev ever ever ever' send me
an email again
(eg: there is no way to initiate a us federal law mandated opt-out of
youtube emai
> We've found that our MyISAM tables being used with Bayes in MySQL have
> caused some bottlenecks on our busier mail servers. We're
> contemplating using inooDB just for the Bayes database. If MySQL will
> only be using innoDB, does anyone have any recommendations for innoDB
> settings in my.cnf t
We've found that our MyISAM tables being used with Bayes in MySQL have
caused some bottlenecks on our busier mail servers. We're
contemplating using inooDB just for the Bayes database. If MySQL will
only be using innoDB, does anyone have any recommendations for innoDB
settings in my.cnf to optimize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thus Robert Schetterer spake:
> Hi,
> there was/is a Problem with the denic .de root servers
> this might give you some Problems with mail
Hi,
and the worst thing was that they sent no SERVFAIL but NXDOMAIN what
will cause a lot of bounces...
> it l
Hi,
there was/is a Problem with the denic .de root servers
this might give you some Problems with mail
it looks like that it is recent partly working again
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
10 matches
Mail list logo