"Sending client does not conform to RFC822 minimum requirements" ?

Hi Group,

I've been using Mercury mail for over a year with no problems.
Sometime last week the server suddenly had trouble getting outbound mail
to recepients.

GMail and my work computer keep receiving the mail as no-subject, no-
from-address, bodyless emails.

The only thing I've been able to find so far is this comment in the
received blank mail that was sent through my problematic mail server:

"X-Comment: Sending client does not conform to RFC822 minimum
requirements"


Here is the whole header (with names changed to protect the innocent):


============================================================ ===========
Microsoft Mail Internet Headers Version 2.0
X-iHateSpam-Checked: Scanned by iHateSpam Server Edition. (0)
Received: from smtp11.intermedia.net ([64.78.21.10]) by ehost011-
7.exch011.intermedia.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 25
Mar 2005 10:35:53 -0800
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by
smtp11.intermedia.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 25 Mar
2005 10:35:52 -0800
Date: Fri, 25 Mar 2005 18:35:51 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum
requirements
X-Comment: Date has been added by Maillennium
Received: from ehlo (c-67-161-37-123.client.comcast.net[67.161.37.123])
by comcast.net (rwcrmhc12) with ESMTP id
<2005032518355101400sci25e>; Fri, 25 Mar 2005 18:35:51 +0000
Received: from Spooler by ehlo (Mercury/32 v4.01b) ID MO001D41; 25 Mar
2005 10:35:51 -0800
From:
Bcc:
Return-Path:
Message-ID:
X-OriginalArrivalTime: 25 Mar 2005 18:35:52.0086 (UTC) FILETIME=
[78F95360:01C53169]
============================================================ ===========


Any ideas?


-Sarah

Re: "Sendingclient does not conform to RFC822 minimum requirements"?

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-commodore.email-scan.com-25400-1111785038-0003
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Sarah writes:

> Hi Group,
>
> I've been using Mercury mail for over a year with no problems.
> Sometime last week the server suddenly had trouble getting outbound mail
> to recepients.
>
> GMail and my work computer keep receiving the mail as no-subject, no-
> from-address, bodyless emails.
>
> The only thing I've been able to find so far is this comment in the
> received blank mail that was sent through my problematic mail server:
>
> "X-Comment: Sending client does not conform to RFC822 minimum
> requirements"

Define "suddenly had trouble".

This informational header appears to be added by your smarthost; it's for
information purposes only and has no apparent effect on mail delivery.

If you believe that your messages simply disappear, then either post your
evidence of that, or request DSNs on your outgoing messages.

If your messages are returned as undeliverable, show the entire non-delivery
report, not just your original message.


--=_mimegpg-commodore.email-scan.com-25400-1111785038-0003
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCRH5Ox9p3GYHlUOIRAvDeAJ9+b+SjH8IL/L6IZHz/JMhryzzkhACd Hxex
0Qkk+4YNw82f8VydOQSMdJ0=
=aTcW
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-25400-1111785038-0003--

Re: "Sendingclient does not conform to RFC822 minimum requirements"?

Sam wrote in
news:cone.1111785038.709684.25400.500@commodore.email-scan.c om:

> Sarah writes:
>

First, I'd like to say how happy I am that I was able to provide an outlet
for whatever problems you seem to be having in life.

Then I'd mention that my mail disappearing is not a matter of faith that I
have to believe. I send an email, and a week later, it is neither here nor
there. It is gone.
Nothing is returned as undeliverable, and as such, it is impossible to post
evidence of this. Unless you'd like to come over and personally spend a
week waiting for mail to not show.

I did not believe that the text I gave would have any affect on delivery.
It was posted as informational to aid in diagnosis. If I showed you a wall
with a smoking hole in it and asked what might have caused it, I wouldn't
be thinking that the smoke caused the hole.

Definition of "Suddenly had trouble":
Things were working. Then they weren't.

Without any apparent change in the system, mail ceased to be making it to
recipients.

Now that you have given me a chance to counter with a release of my own, I
will *plonk* you and we can go about our separate ways.

Re: "Sending client does not conform to RFC822 minimum requirements" ?

On comp.mail.misc, in , "Sarah" wrote:
>
> Any ideas?
>
>
> -Sarah
>

Yes. That your name isn't "Sarah", that you are male, and that
you are a spammer that is trying to get us to help you become a
better spammer.

Spammers are always sending screwed up mail in an attempt to
beat spam filters.

On the Usenet, the use of common first names as an alias is a
way of keeping people from tracking a person through the Usenet
Archives at http://groups.google.com/advanced_group_search.

From seeing where and what they have posted before.

There's no way to figure out _which_ "sarah" (in this case), if
any, you are.

And, not coincidentally, you are using a newsserver to post
from that does not include your IP in the headers. Reputable
newsservers include it in the NNTP-Posting-Host header.

[All of the above would apply to a troll trying to harass
someone(s) through the mails as well as a spammer.]

So have a nice day.

And don't bother trying to spam/troll me. I won't even know you
tried.

Anonymous mail is rejected by my filter, sent to /dev/null,
without even telling me that it happened.

Use your real email address and read the mail you get, or you
have no chance of ever getting me to even see the subject of
your mail.


AC

--
Zero-Tolerance for Spam and Trollmail
Pass-list --> Block-List --> Challenge-Response
http://tinyurl.com/2t5kp

Re: "Sending client does not conform to RFC822 minimum requirements"?

On Fri, 25 Mar 2005, Sarah wrote:
> I've been using Mercury mail for over a year with no problems.

Have you checked with technical support for Mercury mail and comcast.net?

Unfortunately, the information you have provided does not give very much
to go on.

What can be determined doesn't seem to make much sense. The symptoms
point to the mail client not transmitting any header information; that
doesn't make sense since Mercury should have generated it. One
possibility is that some intermediate process (perhaps a virus scanner?)
is interfering with the SMTP protocol negotiation in some way.

As for your messages not reaching the intended recipients, that problem
may be caused by the invalid/missing headers. So, your first task is to
get the invalid/missing headers fixed.

Your best bet would be to find some expert (preferably someone skilled
with Mercury) who is local to you, and who can visit you and inspect your
computer personally. Otherwise, you're in for a long and frustrating
process in debugging it.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

Re: "Sendingclient does not conform to RFC822 minimum requirements"?

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-commodore.email-scan.com-30703-1111800550-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Beavis writes:

> On comp.mail.misc, in , "Sarah" wrote:
>>
>> Any ideas?
>>
>>
>> -Sarah
>>
>
> Yes. That your name isn't "Sarah", that you are male, and that
> you are a spammer that is trying to get us to help you become a
> better spammer.

Beavis, when was the last time you saw a mental health professional?

For more information on Beavis, see the FAQ at
http://groups-beta.google.com/groups?q=beavis

See also: http://angel.1jh.com/nanae/kooks/alanconnor.shtml



--=_mimegpg-commodore.email-scan.com-30703-1111800550-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCRLrmx9p3GYHlUOIRAjUAAJ9vW7h3ecHsDe60wjgkHEEFBOScLgCf Z1ek
SBsXNJN5T3420dJeCHGbQsc=
=cioQ
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-30703-1111800550-0002--

Re: "Sending client does not conform to RFC822 minimum requirements" ?

"Alan Connor" wrote in message
news:Kz21e.4740$H06.4095@newsread3.news.pas.earthlink.net...
> On comp.mail.misc, in , "Sarah" wrote:
>>
>> Any ideas?
>>
>>
>> -Sarah
>>
>
> Yes. That your name isn't "Sarah", that you are male, and that
> you are a spammer that is trying to get us to help you become a
> better spammer.
>
> Spammers are always sending screwed up mail in an attempt to
> beat spam filters.
>
> On the Usenet, the use of common first names as an alias is a
> way of keeping people from tracking a person through the Usenet
> Archives at http://groups.google.com/advanced_group_search.
>
> From seeing where and what they have posted before.
>
> There's no way to figure out _which_ "sarah" (in this case), if
> any, you are.
>
> And, not coincidentally, you are using a newsserver to post
> from that does not include your IP in the headers. Reputable
> newsservers include it in the NNTP-Posting-Host header.
>
> [All of the above would apply to a troll trying to harass
> someone(s) through the mails as well as a spammer.]
>
> So have a nice day.
>
> And don't bother trying to spam/troll me. I won't even know you
> tried.
>
> Anonymous mail is rejected by my filter, sent to /dev/null,
> without even telling me that it happened.
>
> Use your real email address and read the mail you get, or you
> have no chance of ever getting me to even see the subject of
> your mail.
>
>
> AC
>

jeez, your even more pathetic that what the webpage says about you!, your
just a total loser thats just be OWNED!

Re: "Sending client does not conform to RFC822 minimum requirements" ?

In article , Sarah says...

> I've been using Mercury mail for over a year with no problems.
> Sometime last week the server suddenly had trouble getting outbound mail
> to recepients.

> GMail and my work computer keep receiving the mail as no-subject, no-
> from-address, bodyless emails.

> The only thing I've been able to find so far is this comment in the
> received blank mail that was sent through my problematic mail server:

> "X-Comment: Sending client does not conform to RFC822 minimum
> requirements"

That was added by "Maillennium"; as others have noted, that appears to be
the Comcast server. I am going to take a "WAG", and say that you have
something like Norton Anti Virus scanning your outbound email. Look at these
header lines from my server:

> Received: from aosake.net (adsl-64-161-31-129.dsl.sntc01.pacbell.net [64.161.31.129])
> (authenticated bits=0)
> by ylpvm53.prodigy.net (8.12.10 auth mps linux/8.12.10) with ESMTP id j2Q6OBRn016376
> for <********>; Sat, 26 Mar 2005 01:24:13 -0500
> Received: from Spooler by aosake.net (Mercury/32 v4.01b) ID MO00000A;
> 25 Mar 2005 22:24:00 -0800

Now look at the comparable ones from your server:

> Received: from ehlo (c-67-161-37-123.client.comcast.net[67.161.37.123])
> by comcast.net (rwcrmhc12) with ESMTP
> id <2005032518355101400sci25e>; Fri, 25 Mar 2005 18:35:51 +0000
> Received: from Spooler by ehlo (Mercury/32 v4.01b) ID MO001D41;
> 25 Mar 2005 10:35:51 -0800

Two things that I see are:

Your Mercury Mail server included the date/time stamp, but the Comcast
"Maillennium" server failed to pick it up. The Comcast server also entered
"ehlo" instead of your server's Internet name (like my "aosake.net").

Also, there is the matter of the message ID string. From your headers:

> Message-ID:

Actually, I am surprised that the Comcast mail server didn't add one; that
one was added by your (presumably) work server: intermediate.net. From my
message headers:

> Message-ID: <14765633C3B@aosake.net>

Your message apparently was truncated at some point during the sending
phase. This suggests, to me, that you have outbound email scanning with
Norton, rather than a defined AV Policy in Mercury Mail; and Norton, or
whichever AV program, is causing the SMTP transaction to become garbled.
Turn off the anti virus email scan. If you want email scanning, there is a
method using a Policy in Mercury Mail; it works well for me.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

Re: "Sending client does not conform to RFC822 minimum requirements" ?

In article , Alan
Connor says...

> On comp.mail.misc, in , "Sarah" wrote:

> > Any ideas?

> > -Sarah

> Yes. That your name isn't "Sarah", that you are male, and that
> you are a spammer that is trying to get us to help you become a
> better spammer.

Oh, put a sock in it, Alan. And did I tell you that I found a spammer who
just loves C/R systems? She uses Spam Arrest to vet her incoming email, of
all things. And the really odd thing is, she claims I responded to her
challenge when I sent her an email composed, and sent, through the web
interface of my ISP's mail service. Well, ok; SBC Yahoo! DSL Service uses
the same web interface as Yahoo! mail. The message I sent her did not result
in a challenge; my reply to her, through my local server/smarthost
combination, did get a challenge from her. Oh, and she touts a "Spam Filter
Buster" program to break through spam filters.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

Re: "Sending client does not conform to RFC822 minimum requirements"?

On Fri, 25 Mar 2005, Sarah wrote:
> Hi Group,
> I've been using Mercury mail for over a year with no problems.
> Sometime last week the server suddenly had trouble getting outbound mail
> to recepients.
>
> GMail and my work computer keep receiving the mail as no-subject, no-
> from-address, bodyless emails.
>
> The only thing I've been able to find so far is this comment in the
> received blank mail that was sent through my problematic mail server:
>
> "X-Comment: Sending client does not conform to RFC822 minimum
> requirements"
>
>
> Here is the whole header (with names changed to protect the innocent):
>
>
> ============================================================ ===========
> Microsoft Mail Internet Headers Version 2.0

Not a valid header.

> X-iHateSpam-Checked: Scanned by iHateSpam Server Edition. (0)
> Received: from smtp11.intermedia.net ([64.78.21.10]) by ehost011-
> 7.exch011.intermedia.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 25
^^^^^^^^^^^^^^^^^
Not a valid protocol. Must be "atomic" in syntax - and as a two-word entry, it
must be surrounded by double-quotes which are missing. See RFC-2821 (since it
claims to be an SMTP variant). Syntax otherwise valid under RFC-2822.

> Mar 2005 10:35:53 -0800
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
> Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by
> smtp11.intermedia.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 25 Mar
^^^^^^^^^^^^^^^^^ [same as above]
> 2005 10:35:52 -0800
> Date: Fri, 25 Mar 2005 18:35:51 +0000 (GMT)
> X-Comment: Sending client does not conform to RFC822 minimum
> requirements
> X-Comment: Date has been added by Maillennium
> Received: from ehlo (c-67-161-37-123.client.comcast.net[67.161.37.123])
> by comcast.net (rwcrmhc12) with ESMTP id
> <2005032518355101400sci25e>; Fri, 25 Mar 2005 18:35:51 +0000
> Received: from Spooler by ehlo (Mercury/32 v4.01b) ID MO001D41; 25 Mar
> 2005 10:35:51 -0800
> From:
> Bcc:
> Return-Path:
> Message-ID:
> X-OriginalArrivalTime: 25 Mar 2005 18:35:52.0086 (UTC) FILETIME=
> [78F95360:01C53169]
> ============================================================ ===========
> Any ideas?

See the RFC's for required headers. (e.g. "no subject", "no date", etc....).

Re: "Sending client does not conform to RFC822 minimum requirements" ?

[f'ups set to exclusively, where this discussion
really belongs]

On Fri, 25 Mar 2005 20:19:27 GMT, in ,
Sarah wrote:

> Hi Group,
>
> I've been using Mercury mail for over a year with no problems.
> Sometime last week the server suddenly had trouble getting outbound mail
> to recepients.
>
[snip]

To *all* recipients, or just those at certain destination domains?

> GMail and my work computer keep receiving the mail as no-subject, no-
> from-address, bodyless emails.
>
[snip]

So then, since (at least) these destinations are receiving the mail (albeit,
apparently in mangled form), then your server *is* getting it out.

> The only thing I've been able to find so far is this comment in the
> received blank mail that was sent through my problematic mail server:
>
> "X-Comment: Sending client does not conform to RFC822 minimum
> requirements"
>
[snip]

That header is apparently added by one of the receiving MTAs. It very
probably has little or nothing to do with any deliverability problems at your
end.

> Here is the whole header (with names changed to protect the innocent):
>
[snip]

That doesn't help much. It would appear to have been created by a Microsoft
mail client (or, possibly, Exchange). In any event, the key parts are:

--> Received: from ehlo (c-67-161-37-123.client.comcast.net[67.161.37.123])
--> by comcast.net (rwcrmhc12) with ESMTP id
--> <2005032518355101400sci25e>; Fri, 25 Mar 2005 18:35:51 +0000

--> Received: from Spooler by ehlo (Mercury/32 v4.01b) ID MO001D41; 25 Mar
--> 2005 10:35:51 -0800

These two headers, taken together, rather strongly imply that your server is
running off a Comcast "cable modem" line (specifically,
at IP [67.161.37.123] -- which is indeed
Comcast customer IP space), and that it is smarthosting through Comcast's
"real" SMTP server (as it should be, since any competently managed MTA will
reject all mail traffic coming from DHCP space, especially that of Comcast).
It also shows that your outgoing mail *is* being delivered at least that far;
so what happens to it after that point is at least primarily Comcast's
doing/problem, not yours.

However... The

--> X-Comment: Sending client does not conform to RFC822 minimum
--> requirements

and

--> X-Comment: Date has been added by Maillennium

headers imply a problem with your (sending) mail *client* (as opposed to your
local MTA, Mercury), which is the software responsible for generating the
"Date:" header. Mercury should simply pass it on, unscathed, during the DATA
phase of the SMTP transaction.

So first, check (or change) your client (you never mentioned what that
is/was). See if that fixes the problem. If not, can you perhaps use (if only
temporarily) a different smarthost (preferably on a different network), and
see if the mails are still similarly mangled?

--

Jay T. Blocksom
--------------------------------
Appropriate Technology, Inc.
usenet02[at]appropriate-tech.net

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Unsolicited advertising sent to this domain is expressly prohibited under
47 USC S227 and State Law. Violators are subject to prosecution.