Scott1234 Posted April 1, 2023 Report Share Posted April 1, 2023 Hey, was doing some work recently on moving all mailing to AWS SES and whilst checking how the PBX shapes up I am all ways losing 2.5 points on spam assassin due to HDRS_MISSP "Misspaced headers" I only get this on the pbx. Can you guys look at the header structure and make it complaint ? just so we don't all lose 2.5 points out of the gate, also some of the base e-mail templates are missing alt text's. <img src="https://portal.vodia.com/img/googleplay.png" width="135px" height="40px" /> <img src="https://portal.vodia.com/img/appstore.png" width="135px" height="40px" /> <img src="https://portal.vodia.com/img/msstore.png" width="135px" height="40px" /> <img style="border-top-style: none; border-right-style: none; border-left-style: none; border-bottom-style: none; max-width: 200px" src="data:image/png;base64, Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 1, 2023 Author Report Share Posted April 1, 2023 I think its the placement of headers but I could be wrong, It should be, From: To: Subject: Date: Message-ID: MIME-Version: Content-Type: PBX is, Content-Type: Subject: From: To: Content-Transfer-Encoding:base64 Date: MIME-Version: Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 2, 2023 Report Share Posted April 2, 2023 AFAIK it does not matter which header comes first (see RFC 5322). I tried to Google for the message but it seems to be a problem with an empty line?! Maybe you can attach the content from the email log. Could be something "stupid" — as usual. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 3, 2023 Author Report Share Posted April 3, 2023 yeah I was not 100% sure it was the order, but I also could not find any thing else odd looking to trigger it, unless that part has been stripped out by the time its processed by the remote side and re-rapped. https://www.mail-tester.com/ you can do a test your self there are many like this but I find this one is good. I try to aim for a score of at least 8+ There was as not a whole lot of insightful info on exactly what HDRS_MISSP meant or any examples I could find. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 3, 2023 Author Report Share Posted April 3, 2023 Ha ha, I asked chat GPT and it gave me some directions to go down, the sources it was referencing are no longer published. Q, What would a Misspaced header look like? A, Here's an example of a header with a misspaced header that would trigger the "Misspaced headers" rule in SpamAssassin: From : john.doe@example.com To : jane.doe@example.com Subject : Important message regarding your account Date : Mon, 3 Apr 2023 08:30:00 -0400 In this example, there are extra spaces between the header name and the colon separator in each header field. For instance, there is a space between "From" and the colon separator, which should be "From:". This would trigger the "Misspaced headers" rule in SpamAssassin, and add points to the overall spam score of the message. Q, What should a correctly formatted one look like ? A, Here's an example of a correctly formatted header in an email message: From: john.doe@example.com To: jane.doe@example.com Subject: Important message regarding your account Date: Mon, 3 Apr 2023 08:30:00 -0400 In a properly formatted header, each header field name (such as "From", "To", "Subject", and "Date") should be followed immediately by a colon separator, with no spaces or tabs in between. The field name and value should be separated by a single space. Headers in email messages typically follow the format shown above, and adherence to this standard is important for ensuring that email messages are properly interpreted and processed by email clients and servers. Q, What about the spacing after the : in the header? A, According to the RFC 5322 standard for Internet Message Format, the recommended format for email headers is as follows: field-name: field-value Here, "field-name" refers to the name of the header field, and "field-value" is the value associated with the header field. The colon separator should be followed by a single space. For example, a properly formatted header for an email might look like this: From: john.doe@example.com To: jane.doe@example.com Subject: Example Email Date: Tue, 4 Apr 2023 11:30:00 -0400 Note there is also a single space following the colon separator in each header field. It's worth noting that some email clients or servers may not strictly adhere to the recommended format in RFC 5322, and may allow for variations in header formatting. However, sticking to the recommended format can help ensure that emails are properly interpreted and processed by all email clients and servers. Here is the raw PBX, Content-Type:text/plain Subject:Voice: Test From:<phones@mydomain.com> To:<test-xxxx@srv1.mail-tester.com> Date:Mon, 03 Apr 2023 00:45:59 -0000 MIME-Version:1.0 Message-Id: <20230403004559.CA021E1B60@mydomain.io> This is a test email. Could it simply be the spacing after the : ? The message ID part is added by my server processing the request, formatted with the space. Here is one sent from outlook/o365 that scores 10/10. Date: Fri, 31 Mar 2023 08:52:26 +0000 From: ABC <my@domain.com> Reply-To: ABC <my@domain.com> To: test-123@srv1.mail-tester.com Message-ID: <0101018736de3a32-7dedff49-63aa-49d3-99c2-8ce5307dc9f1-000000@domain.com> Subject: TEST - 123 123 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_64269f465fd_4a1804e18610dc"; charset=UTF-8 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 3, 2023 Report Share Posted April 3, 2023 Yes the colon handling is inconsistent, but the reason for that is probably because the Message-ID was inserted by the mailer. We had already changed that in 69. What we could do is to add the Message-ID also in 68 and even add that space after the colon, so that if any other tool feels like inserting headers they would look the same. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 3, 2023 Author Report Share Posted April 3, 2023 A test from 69 still has the same issue with the Message-ID included, with no other additions added to the header, so it must be the space after the : that is required. I am sure a quick one for you to test and check. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 3, 2023 Report Share Posted April 3, 2023 We did check. There was no colon behind the header name, also not in the Message-ID and it was consistent. Anyhow, it is not a big deal and we'll just have a space everywhere and also a Message-ID in 68. It should appear in a few days with the next build. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 3, 2023 Author Report Share Posted April 3, 2023 Nice I look forward to testing. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted April 19, 2023 Author Report Share Posted April 19, 2023 Happy days! thanks. We are scoring great now on .0.30 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 19, 2023 Report Share Posted April 19, 2023 ... and everything just because of a space its ludicrous! Quote Link to comment Share on other sites More sharing options...
MarkMaddy Posted January 4 Report Share Posted January 4 Hi kindly share the full header please Quote Link to comment Share on other sites More sharing options...
MarkMaddy Posted January 4 Report Share Posted January 4 i have 8.9 score kindly provide a solution....for this Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 4 Report Share Posted January 4 Well the PBX will not publish a SPF record... We initially also sent text views like 15 years ago, but it's a lot of double work and frankly this requirement is antiquated. Quote Link to comment Share on other sites More sharing options...
MarkMaddy Posted January 12 Report Share Posted January 12 Kindly Provide Me a solution boss.... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.