[Scspamcop] Re: ISP's Mailserver Gags on Header; Can't Sub to SC

[Mike Easter]

Michael Brennan wrote:

> I'm posting the sourcefile as a plain textfile attachment as before
> over in .spam.

Your newsagent performs an attachment to a newsmessage differently than
mine does, or that I have seen others do experimenting with this method
in .spam.  The difference is that your attachment is 'inline', whereas
mine is not.  Also, mine does something 'wrong' as well.

yours:
Content-Type: text/plain; charset=us-ascii;
 name="StockSpamSrc033107.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="StockSpamSrc033107.txt"

mine:
Content-Type: text/plain;
 name="StockSpamSrc033107.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="StockSpamSrc033107.txt"

In addition, something about this process is affecting the way /my/
system is attaching the .txt file, which is resulting in my system
performing a transfer encoding as quoted printable, which is not
desirable in this context, as it introduces quotedprintable linewraps
which were not present in the original.

If I take the same .txt file except rename it .eml, which is the way I
have attached .eml files in .spam in the past, then it 'properly'
attaches without the quotedprintable mime structure or linewraps.

mine as eml:
Content-Type: message/rfc822;
 name="StockSpamSrc033107.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="StockSpamSrc033107.eml"

So, I would say the two 'wrong' methods in these 3 examples are your
inline condition, my quoted printable condition, and the only 'right'
method is my attachment condition without QP transfer.

> "An unknown error was returned from the SMTP server. Subject
> 'Penny-Stock "Pump & Dump" UCE Spams', Account: 'pop.hal-pc.org',
> Server: 'smtp.hal-pc.org', Protocol: SMTP, Server Response: '579
> message content is not acceptable here', Port: 25, Secure(SSL): No,
> Server Error: 579, Error Number: 0x800CCC61"

It is somewhat interesting about how your mail is handled.  When mail is
incoming to you, it is handled by postini psmtp.com servers, but when
your mail is outgoing, it is handled by hal-pc.org server.  Your
domainname uses 2 different blocks for its nameservice and outgoing
mail, and it uses the postini service which is another netblock for its
incoming mail.

The reason that is of some significance in this context is that the
postini servers are willing to pass this spamitem incoming to you, but
some feature of the content or how your mailuser agent is attaching it
for the submit is not satisfactory to the hal-pc server, a different
server than incoming.


-- 
Mike Easter
kibitzer, not SC admin