Interesting SPAM issue
Just wanted to highlight this for you folks since we had a customer report something getting routed to spam.
Also - your email reply was nearly blocked as spam by default
SpamAssassin
scoring rules. The problem is that the from: address has the
form:
which triggers the SpamAssassin rule
2.73 FROM_LOCAL_HEX_2 From: localpart has long hexadecimal sequence
Some companies block or at least quarantine email on scores as
low as 2.5.
We modified the rule so all Barracuda Spam & Virus firewalls
will no
longer score your email like this, but unfortunately, we're not the
only
anti-spam vendor.
You guys might want to look into modifying the from address in a
way that
is more SpamAssassin- friendly
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Tim on 06 Jul, 2011 12:50 AM
Hi Damon,
Thanks for bringing this to our attention. Our system relies on the hexadecimal string in order to make sure that incoming emails get routed to the correct Tender site. Using strings within the subject or within the text of the email itself proves problamatic due to the fact that users often edit those (the result is we would be unable to route their email to the proper location).
We'll take your observation into account, but it is difficult for us to make changes without actually causing more harm than good, and with something as deeply integrated into our system as this, we definitely want to make sure that we're careful and, if we decide to make any changes, that they would be net positive for us and our users.
Tangentially speaking, a spam score as low as 2.5 is very aggressive scoring, and I'd wager that they risk losing a considerable amount of legitimate email at thresholds like that...
Either way, thanks for your observation. We will definitely always take a close look at this as time goes by, but I cannot guarantee we'll make any changes in the first place, and in the second place, if we did make changes, there's no guessing on the timeframe.
Thanks!
Tim
Tim closed this discussion on 06 Jul, 2011 12:50 AM.
damon re-opened this discussion on 06 Jul, 2011 01:59 AM
2 Posted by damon on 06 Jul, 2011 01:59 AM
Hi Tim,
No problem at all. Just wanted to toss it your way.
Regards,
Damon
Amanda closed this discussion on 06 Jul, 2011 06:21 PM.