Another thing to try is to temporarily insert the line: import pdb; pdb.set_trace() ... on your test system at mabe line 130 in lib/python/Products/MailHost.py (inside the send method). Then, run Zope in debug mode (e.g. "start.bat -D") and try to authenticate with your hacked standard_error_message. You will likely be thrown into the Python debugger. Continue to hit "n"<return> (next statement, skips over subroutines) or "s"<return> (next statement, skips into subroutines) until you find the line or funciton causing the slowdown. (To get out of the debugger, press "c" several times and then press ctrl-C). When you find out where it's slowing things down (or maybe it doesn't even get called!) report back. HTH, - C Jerome Alet wrote:
On Fri, 15 Feb 2002 H.de.Wit@SFK.NL wrote:
More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately.
Are your MailHost instances using the same SMTP host whatever Zope server you test on ?
Could you try to send a message from each host using the MailHost code outside of Zope and see the result ? (I don't know if this is feasable or not, however)
Jerome Alet
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"