Summary | mail sent via horde tagged as spam by spamassassin |
Queue | Horde Base |
Queue Version | 3.1.1 |
Type | Bug |
State | Not A Bug |
Priority | 2. Medium |
Owners | |
Requester | manager (at) scronline (dot) com |
Created | 06/05/2006 (6989 days ago) |
Due | |
Updated | 06/15/2006 (6979 days ago) |
Assigned | |
Resolved | 06/05/2006 (6989 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
been worked out. I appreciate the information you're gave, however
that doesn't really help much with the problem bogus or not. In the
interest of helping those that might find this problem in the future....
vi /usr/share/spamassassin/50_scores.cf
find:
score HELO_DYNAMIC_IPADDR 3.520 2.754 4.070 4.400
And adjust it accordingly or comment it out. That will at least make
your webmail stop getting tagged by spamassassin.
State ⇒ Not A Bug
In short, old versions of spamassassin are broken. Not much we can do
about it.
from mostly are SBC/AT&T IP range which ARE known to harbor spam, but
that doesn't change the fact that legit email is getting tagged.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ mail sent via horde tagged as spam by spamassassin
Queue ⇒ Horde Base
New Attachment: horde-sa.txt
it. However that doesn't change the fact that when people are sending
mail using Horde to my mail server if they are on a known dynamic IP
address it gets tagged by spam assassin. However when using SASL for
SMTP authentication there is no problem. There is no option in horde
that I can use (that I can see) to alter this such as using the php
mail function and people using the server vary greatly. Setting a
single user to handle all authentication isn't really an options.
Either rate, the end result is I'm having a large amount of outgoing
mail getting blocked.