[Plone-Users] SecureMaildropHost woes

[Sean Fulmer]

I'm trying to get SecureMaildropHost working on a client's site.

It functions, in that it actually queues and sends mail as it should,
but the problem is that when the recipient views the email, the
headers are garbled and the message content is presented as what I
assume is raw base64-encoded text.

If I use the standard SecureMailhost, the emails that Plone sends work
fine (headers are ok, message is readable).

Nasty raw email source follows - I can see that the headers are
different, but my email-header-fu is not strong enough to tell me what
the problem is. Can anyone tell me what I need to do to get
SecureMaildropHost to send readable messages?

Thanks,

Sean

Here is the source of a message sent by SecureMaildropHost:
----------------------------------------------------------------------
Delivered-To: xx...@gmail.com
Received: by 10.78.25.12 with SMTP id 12cs81998huy;
Sat, 28 Jul 2007 16:27:23 -0700 (PDT)
Received: by 10.141.88.3 with SMTP id q3mr1357184rvl.1185665243356;
Sat, 28 Jul 2007 16:27:23 -0700 (PDT)
Return-Path: <xxxx+...@gmail.com>
Received: from yyyyyy ([000.000.000.000])
by mx.google.com with ESMTP id l27si1705348rvb.
2007.07.28.16.27.22;
Sat, 28 Jul 2007 16:27:23 -0700 (PDT)
Received-SPF: neutral (google.com: 000.000.000.000 is neither
permitted nor denied by domain of xxxx+...@gmail.com)
Received: from localhost ([127.0.0.1] helo=[127.0.1.1])
by yyyyyy with esmtp (Exim 4.63)
(envelope-from <xxxx+...@gmail.com>)
id 1IEvhN-0007MM-EU
for xx...@gmail.com; Sat, 28 Jul 2007 17:27:49 -0600
Message-Id: <20070728232749.27489.55921@yyyyyy>
From: xxxx+...@gmail.com
Date: Sat, 28 Jul 2007 17:27:49 -0600

>From nobody Sat Jul 28 17:26:40 2007
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
To: xx...@gmail.com
Subject: =?utf-8?q?Welcome_to_Plone?=
From: xxxx...@gmail.com

ClRoaXMgbGluayBpcyBzZW50IHRvIHlvdSBmcm9tIGh0dHA6Ly8xOTIuMTY4LjAuNTo4MDgwL2Nl
bnRyaXN0CgpZb3UgYXJlIHJlY2VpdmluZyB0aGlzIG1haWwgYmVjYXVzZSBzb21lb25lIHJlYWQg
YSBwYWdlIGF0ClRoZSBDZW50cmlzdCBQYXJ0eQphbmQgdGhvdWdodCBpdCBtaWdodCBpbnRlcmVz
dCB5b3UuCgpJdCBpcyBzZW50IGJ5IHdzZnVsbWVyK2Ryb3BAZ21haWwuY29tIHdpdGggdGhlIGZv
bGxvd2luZyBjb21tZW50OgoiVGhpcyBpcyBhIHRlc3QiCgpXZWxjb21lIHRvIFBsb25lCgpDb25n
cmF0dWxhdGlvbnMhIFlvdSBoYXZlIHN1Y2Nlc3NmdWxseSBpbnN0YWxsZWQgUGxvbmUuCgpodHRw
Oi8vMTkyLjE2OC4wLjU6ODA4MC9jZW50cmlzdC9mcm9udC1wYWdlCgotLQpQb3J0YWwgQWRtaW5p
c3RyYXRvcgoKCg==
----------------------------------------------------------------------

And here is the source of the same message (same sender, recipient,
subject, and content) sent by the standard SecureMailHost:
----------------------------------------------------------------------
Delivered-To: xx...@gmail.com
Received: by 10.78.25.12 with SMTP id 12cs82015huy;
Sat, 28 Jul 2007 16:28:33 -0700 (PDT)
Received: by 10.140.249.20 with SMTP id w20mr1362893rvh.1185665313187;
Sat, 28 Jul 2007 16:28:33 -0700 (PDT)
Return-Path: <xxxx+...@gmail.com>
Received: from yyyyyy ([000.000.000.000])
by mx.google.com with ESMTP id c20si2089157rvf.
2007.07.28.16.28.32;
Sat, 28 Jul 2007 16:28:33 -0700 (PDT)
Received-SPF: neutral (google.com: 000.000.000.000 is neither
permitted nor denied by domain of xxxx+...@gmail.com)
Received: from localhost ([127.0.0.1] helo=[127.0.1.1])
by yyyyyy with esmtp (Exim 4.63)
(envelope-from <xxxx+...@gmail.com>)
id 1IEviS-0007NN-16
for xx...@gmail.com; Sat, 28 Jul 2007 17:28:56 -0600
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
To: xx...@gmail.com
Subject: =?utf-8?q?Welcome_to_Plone?=
From: xxxx...@gmail.com
Date: Sat, 28 Jul 2007 17:28:55 -0600
X-Mailer: Zope/SecureMailHost
Message-Id: <20070728232855.27497.34241.yyyyyy@yyyyyy>

ClRoaXMgbGluayBpcyBzZW50IHRvIHlvdSBmcm9tIGh0dHA6Ly8xOTIuMTY4LjAuNTo4MDgwL2Nl
bnRyaXN0CgpZb3UgYXJlIHJlY2VpdmluZyB0aGlzIG1haWwgYmVjYXVzZSBzb21lb25lIHJlYWQg
YSBwYWdlIGF0ClRoZSBDZW50cmlzdCBQYXJ0eQphbmQgdGhvdWdodCBpdCBtaWdodCBpbnRlcmVz
dCB5b3UuCgpJdCBpcyBzZW50IGJ5IHdzZnVsbWVyK2Ryb3BAZ21haWwuY29tIHdpdGggdGhlIGZv
bGxvd2luZyBjb21tZW50OgoiVGhpcyBpcyBhIHRlc3QiCgpXZWxjb21lIHRvIFBsb25lCgpDb25n
cmF0dWxhdGlvbnMhIFlvdSBoYXZlIHN1Y2Nlc3NmdWxseSBpbnN0YWxsZWQgUGxvbmUuCgpodHRw
Oi8vMTkyLjE2OC4wLjU6ODA4MC9jZW50cmlzdC9mcm9udC1wYWdlCgotLQpQb3J0YWwgQWRtaW5p
c3RyYXRvcgoKCg==
----------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Plone-Users mailing list
Plone...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-users

[Sean Fulmer]

Forgot system info, sorry:

Zope Version (Zope 2.9.6-final, python 2.4.4, linux2)
Python Version 2.4.4 (#2, Apr 12 2007, 21:03:11) [GCC 4.1.2 (Ubuntu
4.1.2-0ubuntu4)]
CMFPlone 2.5.3-final
Maildrophost 1.20
SecureMailhost 1.0.5
SecureMaildropHost 0.1

[Sean Fulmer]

Ok, I sorted this mess out. The problem was in the third line of the
message file generated by the MaildropHost:

##To:xxxx...@gmail.com
##From:xxxx+...@gmail.com
>>>>From nobody Sun Jul 29 15:55:32 2007
Content-Type: text/plain; charset="utf-8"

That line was coming from SecureMaildropHost.py line 36, in
SecureMaildropHost._send, which was calling MaildropHost._send like
so:

MaildropHost._send(self, mfrom, mto, str(messageText))

messageText is an email.MIMEText object, and wrapping it in str()
produces that funky line in the message header. I changed it to the
following:

MaildropHost._send(self, mfrom, mto, messageText.as_string())

And voila, no extra line in the header, and the messages are readable
by the recipient.

Thank you, pdb.set_trace()!