Bug 7947 - All outgoing emails blocked
Summary: All outgoing emails blocked
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: unspecified
Hardware: PC other
: P2 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-13 15:54 UTC by Jeff
Modified: 2021-12-15 03:24 UTC (History)
3 users (show)



Attachment Type Modified Status Actions Submitter/CLA Status
Firehouse Solutions Blocked Email Reply application/pdf None Jeff [NoCLA]
Firehouse Solutions Blocked Email Reply text/plain None Jeff [NoCLA]
Outlooks Details on Spam text/plain None Jeff [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff 2021-12-13 15:54:59 UTC
Created attachment 5758 [details]
Firehouse Solutions Blocked Email Reply

Hello,

I am using Windows 10 with Microsoft Office 365. Our email is SmarterMail provided through Firehouse Solutions which I have set-up Outlook for. For the last four or five days every email I have sent has need returned with a 550 error code "This message cannot be delivered as it was marked as spam." Additional details:
Reporting-MTA: dns;mail.firehousesolutions.com
Final-Recipient: rfc822; **every email sent**
Action; failed
Status: 5.0.0

This has effectively shut down my business.

I contacted our email provider and they checked into this and told me Spam Assassin is blocking my outgoing emails (attached). Incoming emails are working fine.

I went through the check list email is using IMAP format is STMP enabled. Historically I have been using an Outlook interface for several years with very few problems outside of the usual Microsoft frustrations. 

I cannot even use the "reply" feature to an email that has been sent to me by one of my customers. I sent very few emails per day, typically less than 10 unless there is some back and forth on the design of one of the fire truck we are working or I am trying to resolve a fire truck out-of-service problem with a customer.

Than you for your time and consideration with this.

Jeff
Comment 1 Bill Cole 2021-12-13 16:44:42 UTC
The attached PDF seems to use Adobe-only features and isn't accessible by standard PDF readers. If you truly believe that whatever is in it is useful, please use an OPEN format like standard PDF or plain text. 

Or: do not bother.

The Apache SpamAssassin project doesn't control anything about how "Firehouse Solutions" configures their mail system. We can't even be sure whether they are running SpamAssassin or not or whether they have the current version or if they've completely replaced the standard ruleset with one of their own.

Your problem is analogous to having an Excel spreadsheet with bad data in it. Microsoft cannot fix that. We cannot fix (or even know) what exactly is causing your problem.
Comment 2 Bill Cole 2021-12-13 17:13:35 UTC
CORRECTION: 

Apparently your mail is being rejected by next hops AFTER it has been accepted by mail.firehousesolutions.com. This makes it very unlikely that the root cause is in anything related to SpamAssassin at all, since none of the largest email providers (Yahoo/AOL/Oath, Google, Microsoft, etc.) use SpamAssassin. 


Please read https://cwiki.apache.org/confluence/display/SPAMASSASSIN/StopBlockingMyMail for a more verbose explanation and better ways to solve your problem.
Comment 3 John Hardin 2021-12-14 01:57:53 UTC
(In reply to Jeff from comment #0)
> I contacted our email provider and they checked into this and told me Spam
> Assassin is blocking my outgoing emails (attached).

Attaching a password-protected PDF of supporting evidence, and then not telling us the password, is not helpful.

Please try reattaching the content as a plain text file, or multiple plain text files if there are multiple instances.
Comment 4 Jeff 2021-12-14 02:56:45 UTC
Created attachment 5759 [details]
Firehouse Solutions Blocked Email Reply
Comment 5 Jeff 2021-12-14 02:58:00 UTC
Created attachment 5760 [details]
Outlooks Details on Spam
Comment 6 Jeff 2021-12-14 03:15:43 UTC
Mr. Hardin,

Thank you for the clarification and my apologies for the confusion. I selected that the supporting document be saved as .PDF with no special instructions or to be password protected. I supplied the documents as text file.
Comment 7 Bill Cole 2021-12-14 15:07:36 UTC
There's still nothing WE can do about this. 

Other than your provider's statement, I can't even see any evidence that SpamAssassin is involved *IN ANY WAY*. The "Outlook Details" file you attached is incomplete because Outlook makes it very hard to see the full content and headers of such messages, but it does indicate that the intended recipient in this case had a gmail.com address. There is absolutely positively NO WAY for us to address any issues with GMail, because Google does not use SpamAssassin. 

Your provider sensibly directed you to relevant pages on our Wiki, where there are helpful tips. Their suggestion that you address the issue by addressing the content & structure of your messages is especially apt, because nearly all modern anti-spam tools examine messages in full rather than using simplistic metric like the domain of a sender or a specific single word.
Comment 8 John Hardin 2021-12-15 03:24:12 UTC
Echoing what Bill says: there's very little actual evidence there for us to work with.

Where are you seeing "Remote Server returned: '550 This message cannot be delivered as it was marked as spam.'"? That's not in the "outlooks details" file. 

I've contacted you directly to see if we can collect some useful data.