Archived Forum Post
Index of archived forum posts
Question:
Archived Forum PostQuestion:
Sending emails with the current Chilkat32 causes gmail to reject the message as not RFC2822 compliant. Unfortunately, they're not saying what is out of compliance.
Message is as follows:
Received: from 3761-SERVER1 ([76.74.252.84]) by mx.CondoConduit.com (IceWarp 11.3.0.4 x64) with ASMTP id 201509241835278589 for <Everyone@SomeDomain.org>; Thu, 24 Sep 2015 18:35:27 -0500 MIME-Version: 1.0 Date: Thu, 24 Sep 2015 18:35:26 -0500 Message-ID: 4BFB45156390F1CAF196ED9F40F6DD4361F98ED0@37610SERVER1 Content-Type: text/html Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) From: WebRobot@SomeDomain.org Subject: Test Message To: "ALL Registered Users" <Everyone@SomeDomain.org> Reply-To: "Michael Hogan" <mhogan@AnotherDomain.com>
<html><head></head><body>Getting Through?</body></html>
Response from gmail is as follows:
<<< 550-5.7.1 [209.15.0.69 11] Our system has detected that this message is not 550-5.7.1 RFC 2822 compliant. To reduce the amount of spam sent to Gmail, this 550-5.7.1 message has been blocked. Please review 550 5.7.1 RFC 2822 specifications for more information. k102si854412ioi.138 - gsmtp
Any suggestions are appreciated
I was not able to reproduce the problem. Everything's working fine for me. You'll have to provide the exact instructions (code snippet) + data for reproducing this problem...
Nevermind - it appears to have been a problem with the mail server processing the messages. All is well. Thx