| Request | MaildropHost -- question -- by MJM |
| Posted on | Mar 17, 2006 5:20 pm |
| Subscribe |
| Comment by Jens Vagelpohl on Mar 19, 2006 2:53 pm | |
|
> Look what I found: http://plone.org/products/securemailhost/roadmap/1 I wonder why no one ever thinks about simplifying things. Instead of seeing if whatever SecureMailHost does can be integrated into MaildropHost so you don't have to install both products they want to keep things separate and just add both to the clutter of products that Plone ships with. Oh well, no change there then. |
|
|
|
| Comment by =?ISO-8859-1?Q?Marcel_Mar=E9?= on Mar 19, 2006 2:41 pm | |
|
Look what I found: http://plone.org/products/securemailhost/roadmap/1 M.J. Maré WebToTheMax |
|
|
|
| Comment by Jens Vagelpohl on Mar 19, 2006 12:38 pm | |
|
>> MaildropHost is a full replacement for MailHost. I don't know what >> "SecureMailHost" does. >> > > The problem is not MDH but SecureMailhost which is used in Plone > 2.1.2. It uses a method secureSend (or similar) instead of send. Ah, and I bet Plone expects this non-standard API in places, right? That would be a typical case of Plone components extending the standard API in incompatible ways and then relying on the incompatibility. |
|
|
|
| Comment by =?ISO-8859-1?Q?Marcel_Mar=E9?= on Mar 19, 2006 7:10 am | |
|
> > MaildropHost is a full replacement for MailHost. I don't know what > "SecureMailHost" does. > The problem is not MDH but SecureMailhost which is used in Plone 2.1.2. It uses a method secureSend (or similar) instead of send. > I just released version 1.16 so you can run off a fixed released > version: > > http://www.dataflake.org/software/maildrophost/maildrophost_1.16 > > This one also carries a comment in config.py about the possible > pitfalls with ADD_MESSAGEID. > great. Thx MJM |
|
|
|
| Resolve by Jens Vagelpohl on Mar 19, 2006 6:19 am | |
|
MaildropHost is a full replacement for MailHost. I don't know what "SecureMailHost" does. I just released version 1.16 so you can run off a fixed released version: http://www.dataflake.org/software/maildrophost/maildrophost_1.16 This one also carries a comment in config.py about the possible pitfalls with ADD_MESSAGEID. |
|
|
|
| Comment by =?ISO-8859-1?Q?Marcel_Mar=E9?= on Mar 19, 2006 5:51 am | |
|
You're right! I indeed used the latest version of MDH (1.15). Switching to trunk solved the problem. Maildropping is now blazingly fast. Turning ADD_MESSAGEID=1 made the slowness return. Maybe add a comment to the config file? Am I right that MDH is no longer a drop in replacement for (Secure) Mailhost? RFE: prevent that start_maildrophost starts a second instance, because stop_maildrophost will only stop the last one started. Thanks for your great product! M.J. Maré WebToTheMax On 19-mrt-2006, at 11:10, JTracker wrote: > Issue followup (Comment) by Jens Vagelpohl (jens@dataflake.org): > > "Why is maildropping so slow?" > http://www.dataflake.org/tracker/issue_00495 > > ---------- > > Can you provide a bit more information, like what version of > MaildropHost you are using? > > My suspicion would be, if you use the latest version, that creating > a Message-Id header slows you down since it involves a DNS lookup > if I remember correctly. The latest MaildropHost has a bug where > turning the ADD_MESSAGEID flag off in config.py would not turn it > off, and they would still be created. > > Grab the latest code from the Subversion repository and run your > test again with ADD_MESSAGEID turned off. > > > ---------- > > Sent automatically by JTracker "Report Bugs" at http:// > www.dataflake.org/tracker |
|
|
|
| Comment by Jens Vagelpohl on Mar 19, 2006 5:10 am | |
|
Can you provide a bit more information, like what version of MaildropHost you are using? My suspicion would be, if you use the latest version, that creating a Message-Id header slows you down since it involves a DNS lookup if I remember correctly. The latest MaildropHost has a bug where turning the ADD_MESSAGEID flag off in config.py would not turn it off, and they would still be created. Grab the latest code from the Subversion repository and run your test again with ADD_MESSAGEID turned off. |
|
|
|
| Initial Request by MJM on Mar 17, 2006 5:20 pm | |
|
I got MDH to work, but I wondered why dropping the mail messages is still slow. I would have expected the mail messages to be written quickly to files, and then to be send slowly. Writing 1 mail message to the spool folder takes 2 seconds (reproducably). I can see the spoolfiles appearing in the spool folder so I'm sure MDH is used. I tested with a small python script: message="The message" send_to_address='debug%d@mydomain.com' subject='test subject' send_from_address='test@mydomain.com' envelope_from=send_from_address host = context.MailHost for i in range(10): sendto=send_to_address % i host.send(message, mto=sendto,mfrom=send_from, subject=subject) print "done" return printed I'm using Plone 2.1.2 on OS X 10.4.5 TIA |
