Re: Trouble finding info on Spam issues
On 03.01.10 05:01, stef64 wrote: > I've uploaded the complete raw source into pastebin... > > http://pastebin.com/m68ccb798 > > and here is the spam score... > > Score Breakdown: > > 1.3 URI: URI hostname has long hexadecimal sequence > 0.0 BODY: HTML included in message > 1.7 BODY: Message only has text/html MIME parts > 2.8 BODY: BASE64_LENGTH_79_INF base64 text must be wrapped up to 76 characters per line. This one is not. > 5.8 TOTAL - Any score below 5 is OK to send. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. - Holmes, what kind of school did you study to be a detective? - Elementary, Watson. -- Daffy Duck & Porky Pig
Re: Trouble finding info on Spam issues
On Sun, 3 Jan 2010, stef64 wrote: I've uploaded the complete raw source into pastebin... http://pastebin.com/m68ccb798 That's only the HTML body text. That doesn't include any of the MIME message markup or message headers generated by whatever tool takes that and converts it into an email message, so much of any advice we can provide will only be guesswork. Can you paste a full email that your system is sending out? Or is this evaluation score being generated by a tool that only wants a block of HTML from you? Score Breakdown: 1.3 URI: URI hostname has long hexadecimal sequence Long blocks of unreadable data in a URI can indicate it is a "tracking" URI, used to identify precisely which recipient email address received the message and actually accessed the URI. This is considered a sign of bulk mail. I don't see anything like that in the body text you posted, but I do see what appear to be replacement tags for things like unsubscribe links. That is the likely source for this hit (i.e. the URI that is replacing the tag is encoded in this manner to identify the recipient so that an unsubscribe can be properly processed). As you appear to be using a mailing list service, this is likely a hit you'll just have to live with. Fixing it would be something for your service provider to look into. It would involve changing how they encode their unsubscribe (and other subscriber-specific) links. 0.0 BODY: HTML included in message Informational. 1.7 BODY: Message only has text/html MIME parts Please be considerate of your recipients who do not wish to receive, or due to handicap are unable to read, HTML body parts, and also include a plain text version of your body content in your messages. As you are apparently only providing a block of HTML to your mailing service, it's possible this is an inherent weakness of the mail service you're using to send your messages. Contact your service provider and see if they offer any way to also provide a plain-text body part in addition to the HTML. If they do not, then you'll just have to accept this hit, and also accept that you will not be communicating effectively with some portion of your subscribers. 2.8 BODY: BASE64_LENGTH_79_INF The message includes a part (typically an attachment) whose base64 encoding does not follow the relevant standards. This is a big problem. Again, as this is probably related to the message your provider generates rather than to the content you're trying to send, you should contact them and tell them to fix their BASE64 encoding so that it's done properly. In summary, there's probably little you yourself can do to reduce this score apart from also providing a plain-text body part, assuming the tools your mail provider offers even allow you to do that. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Where We Want You To Go Today 07/05/07: Microsoft patents in-OS adware architecture incorporating spyware, profiling, competitor suppression and delivery confirmation (U.S. Patent #20070157227) --- 14 days until Benjamin Franklin's 304th Birthday
Re: Trouble finding info on Spam issues
stef64 wrote:
>
> I've uploaded the complete raw source into pastebin...
>
> http://pastebin.com/m68ccb798
>
> and here is the spam score...
>
> Score Breakdown:
>
> 1.3 URI: URI hostname has long hexadecimal sequence
> 0.0 BODY: HTML included in message
> 1.7 BODY: Message only has text/html MIME parts
> 2.8 BODY: BASE64_LENGTH_79_INF
> 5.8 TOTAL - Any score below 5 is OK to send.
Grepping through the SA rule-set reveals this:
uri URI_HEX m%^https?://[^/?]*\b[0-9a-f]{6,}\b%i
describe URI_HEXURI hostname has long hexadecimal sequence
/Per Jessen, Zürich
Re: Trouble finding info on Spam issues
I've uploaded the complete raw source into pastebin... http://pastebin.com/m68ccb798 and here is the spam score... Score Breakdown: 1.3 URI: URI hostname has long hexadecimal sequence 0.0 BODY: HTML included in message 1.7 BODY: Message only has text/html MIME parts 2.8 BODY: BASE64_LENGTH_79_INF 5.8 TOTAL - Any score below 5 is OK to send. -- View this message in context: http://old.nabble.com/Trouble-finding-info-on-Spam-issues-tp26685217p27001351.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Trouble finding info on Spam issues
I'm getting exactly the same message as the OP and am struggling to understand it, so a little help here would be awesome. I'm happy to post whatever you need to address this -- View this message in context: http://old.nabble.com/Trouble-finding-info-on-Spam-issues-tp26685217p27001308.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Trouble finding info on Spam issues
On Sat, 2010-01-02 at 14:08 -0800, micliz wrote: > > > On 07.12.09 14:16, JaredDetroit wrote: > > 1.3 URI: URI hostname has long hexadecimal sequence > > Does anyone know what the issue is with the URI? I can't find anything on > > this. I don't see anything that could be an issue in my message. > > apparently it contains long strinc to differentiate recipients. Spammers > use identifiers to verify e-mail addresses. > > > It I could see it that might help. However, if the sequence prefixes each hex. digit pair with % or &# most (all?) web browsers will decode this into ASCII: an easy way to read the string is to create a simple web page with your text editor, past the string into it and then open the file with a web browser. HTH Martin
Re: Trouble finding info on Spam issues
On 07.12.09 14:16, JaredDetroit wrote: > 1.3 URI: URI hostname has long hexadecimal sequence > Does anyone know what the issue is with the URI? I can't find anything on > this. I don't see anything that could be an issue in my message. apparently it contains long strinc to differentiate recipients. Spammers use identifiers to verify e-mail addresses. >>>>>>>>>>>>>>>>>>>>>>>>> Has a solution been found for the URI hostname issue? I have this same issue. What is the URI hostname? -- View this message in context: http://old.nabble.com/Trouble-finding-info-on-Spam-issues-tp26685217p26996980.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Trouble finding info on Spam issues
On 07.12.09 14:16, JaredDetroit wrote: > 1.3 URI: URI hostname has long hexadecimal sequence > Does anyone know what the issue is with the URI? I can't find anything on > this. I don't see anything that could be an issue in my message. apparently it contains long strinc to differentiate recipients. Spammers use identifiers to verify e-mail addresses. > 1.7 BODY: Message only has text/html MIME parts > I believe this is if you only have an HTML version of an email. I have both > a text and HTML version... are they stored in multipart/alternative mail? > 2.8 BODY: BASE64_LENGTH_79_INF > I know that it's because the length of Base64 is longer than 79 but I can't > find any information about what this actually is and what could cause it. base64-encoded lines may be longer 76 chatacters max. Longer lines indicate rfc2045 violation and it's strong indication of spamminess. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. WinError #9: Out of error messages.
Re: Trouble finding info on Spam issues
On 07/12/2009 22:16, JaredDetroit wrote: > Hi, I don't know if I'm posting the right type of content here but I'm sure > I'll find out. I'm trying to create a newsletter and I keep receiving the > following spam assassin scores: > > I'm sending out a basic HTML newsletter with a pdf attachment to subscribers > in Aweber. I've searched extensively for solutions to these scores but I > only find people with the same issues or random SA dumps. > > 1.3 URI: URI hostname has long hexadecimal sequence > Does anyone know what the issue is with the URI? I can't find anything on > this. I don't see anything that could be an issue in my message. > > 1.7 BODY: Message only has text/html MIME parts > I believe this is if you only have an HTML version of an email. I have both > a text and HTML version... > > 2.8 BODY: BASE64_LENGTH_79_INF > I know that it's because the length of Base64 is longer than 79 but I can't > find any information about what this actually is and what could cause it. > > I really appreciate any help. Paste the raw source of an example email into http://pastebin.com/ after it has been processed by SpamAssassin, with the report header, then reply to this email with the link. Then we can look at what is causing the rules to trigger. -- Mike Cardwell - IT Consultant and LAMP developer Cardwell IT Ltd. (UK Reg'd Company #06920226) http://cardwellit.com/ Technical Blog: https://secure.grepular.com/blog/
Re: Trouble finding info on Spam issues
On Mon, 7 Dec 2009, JaredDetroit wrote: I really appreciate any help. We'd be most able (and willing) to help if we had an actual example message to look at. If you can post a complete scored message, including _all_ headers, to a website like pastebin or to a website you control, and send the URI for that sample to the list (_please_ don't send the sample message itself to the list!), then we can take a look at it and perhaps make meaningful suggestions. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- You do not examine legislation in the light of the benefits it will convey if properly administered, but in the light of the wrongs it would do and the harms it would cause if improperly administered. -- Lyndon B. Johnson --- 8 days until Bill of Rights day
Trouble finding info on Spam issues
Hi, I don't know if I'm posting the right type of content here but I'm sure I'll find out. I'm trying to create a newsletter and I keep receiving the following spam assassin scores: I'm sending out a basic HTML newsletter with a pdf attachment to subscribers in Aweber. I've searched extensively for solutions to these scores but I only find people with the same issues or random SA dumps. 1.3 URI: URI hostname has long hexadecimal sequence Does anyone know what the issue is with the URI? I can't find anything on this. I don't see anything that could be an issue in my message. 1.7 BODY: Message only has text/html MIME parts I believe this is if you only have an HTML version of an email. I have both a text and HTML version... 2.8 BODY: BASE64_LENGTH_79_INF I know that it's because the length of Base64 is longer than 79 but I can't find any information about what this actually is and what could cause it. I really appreciate any help. Thanks, Jared -- View this message in context: http://old.nabble.com/Trouble-finding-info-on-Spam-issues-tp26685217p26685217.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
