You should use SMTP authentication when posting through your SMTP
server.i guess you are not.
(And the SMTP server should not be on dynamic IP, of course)
On 05.04.11 04:29, rstarkov wrote:
I am using SMTP authentication, and it's on a static IP. It's the PC with my
Thunderbird that's on
On Tue, 5 Apr 2011, Michael Scheidell wrote:
you should disable the compile plugin, not bother compiling. with a
borked perl install, the best thing to do is start from scratch. its
almost impossible to fix.
disable this v320.pre:loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
and
Dear All
I would like to create a rune in order to block messages that contains
more than X recipients in Spamassassin from these fields
To:
CC:
Bcc:
This without any MTA help
How can i do this
Best regards ?
2011/4/6 David Touzeau da...@touzeau.eu
Dear All
I would like to create a rune in order to block messages that contains
more than X recipients in Spamassassin from these fields
To:
CC:
Bcc:
This without any MTA help
How can i do this
Best regards ?
In 2009 i wrote this email to
On Wed, 6 Apr 2011 19:18:39 +0200 (CEST), Marco Beishuizen
mb...@xs4all.nl wrote:
disable this v320.pre:loadplugin
Mail::SpamAssassin::Plugin::Rule2XSBody
and restart spamd. your errors will go away.
you did not listen, but try:
spamassassin 21 -D --lint | less
any unwanted plugins failing
On Wed, 6 Apr 2011, Benny Pedersen wrote:
disable this v320.pre:loadplugin
Mail::SpamAssassin::Plugin::Rule2XSBody
and restart spamd. your errors will go away.
you did not listen, but try:
spamassassin 21 -D --lint | less
any unwanted plugins failing ?, or do you like to use more plugins
On Wed, 6 Apr 2011, David Touzeau wrote:
I would like to create a rune in order to block messages that contains
more than X recipients in Spamassassin from these fields
To:
CC:
Bcc:
This without any MTA help
How can i do this
Dang, I thought these were already in my sandbox:
describe
2011/4/6 John Hardin jhar...@impsec.org
On Wed, 6 Apr 2011, David Touzeau wrote:
I would like to create a rune in order to block messages that contains
more than X recipients in Spamassassin from these fields
To:
CC:
Bcc:
This without any MTA help
How can i do this
Dang, I thought
On 04/06/2011 01:00 PM, John Hardin wrote:
Dang, I thought these were already in my sandbox:
describe TO_TOO_MANY To: too many recipients
header TO_TOO_MANY To =~ /(?:,[^,]{1,80}){30}/
describe TO_WAY_TOO_MANY To: too many recipients
header TO_WAY_TOO_MANY ToCc =~
no. You should just properly configure trusted_networks and
internal_networks so all dnsbl rules would be used as they should.
OK, so I need to add all of my ISPs dynamic IPs as trusted? (as suggested in
http://wiki.apache.org/spamassassin/DynablockIssues)
It sounds backwards though; the
On Wed, 6 Apr 2011, rstarkov wrote:
[snip..]
if your MTA properly marks mail received with authentication and inserts
authentication headers, SpamAssassin will take those headers and dynamic
RBL checks should not apply.
I don't think it does. Here's a sample email in its entirety:
Spamassassin does honor authentication headers that are -properly- added.
(see rfc3848 for an official statement of what needs to be done). In your
example that MTA (qmail?) did not add proper authentication headers.
Ah right. Yes, it's qmail. It appears that RFC3848 is not directly supported
On Wed, 6 Apr 2011, Eduardo Casarero wrote:
2011/4/6 John Hardin jhar...@impsec.org
On Wed, 6 Apr 2011, David Touzeau wrote:
I would like to create a rune in order to block messages that contains
more than X recipients in Spamassassin from these fields
To:
CC:
Bcc:
Can you post an
On Wed, 6 Apr 2011, rstarkov wrote:
Ah right. Yes, it's qmail. It appears that RFC3848 is not directly supported
by my managed server... It runs Plesk, and all I can find are a couple of
lone voices asking for this to become supported (met with silence or people
not knowing what on earth is
14 matches
Mail list logo
