[Zope] oddity in MailHost queue processor thread

Hi all, I was surprised by the behavior of asynchronous mailing in zope 2.11.3 MailHost product. It creates a thread by instance of MailHost by the mean of using self.absolute_url(1) as key for the queue_threads dictionnary. It seems obviously wrong, IMO, if several instances share the same que

Re: [Zope] oddity in MailHost queue processor thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maric Michaud wrote: > Hi all, > > I was surprised by the behavior of asynchronous mailing in zope 2.11.3 > MailHost product. It creates a thread by instance of MailHost by the > mean of using self.absolute_url(1) as key for the queue_threads dictio

Re: [Zope] oddity in MailHost queue processor thread

Tres Seaver a écrit : >> I was surprised by the behavior of asynchronous mailing in zope 2.11.3 >> MailHost product. It creates a thread by instance of MailHost by the >> mean of using self.absolute_url(1) as key for the queue_threads dictionnary. >> >> It seems obviously wrong, IMO, if seve

[Zope] problems with emergency user

Hi all, I'm using Zope (version 2.10.11) through Plone. I lost my admin password to access ZMI. I created a file named "access" using the zpassword.py script, as described here: http://docs.zope.org/zope2/zope2book/Security.html?highlight=password#creating-an-emergency-user I tried to place

Re: [Zope] problems with emergency user

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nuno Carvalho wrote: > Hi all, > > I'm using Zope (version 2.10.11) through Plone. I lost my admin > password to access ZMI. > I created a file named "access" using the zpassword.py script, as > described here: > http://docs.zope.org/zope2/zope2b