Is there any way to make the e-mail processing part asynchronous so that the trac doesn't have to wait for every single email to get processed?
On 3/15/06, Alec Thomas <[EMAIL PROTECTED]> wrote: > Trac notifications are generally only as slow as your mail server, so > you likely have something configured in your mail server that is causing > this issue. This could obviously be any number of things, but I'd check > for any kind of spam control, DNS lookups, sender verification, as a > start. > > I'd check your mail server logs, and possibly also enable Trac debug > logging. > > On Wed, Mar 15, 2006 at 11:22:34AM +0800, Mark wrote: > > Hi, > > > > I was able to successfully set-up trac in our server yesterday. I'm > > presently using Trac 0.9.4. Before I enabled email notifications, > > creating or updating a ticket worked just fine. But when I enabled > > email notifications, the process suddenly took a long time to finish. > > I modified the trac.ini file twice. The first time i set it to use a > > remote smtp server, the second time I used the local stmp server found > > in the same machine as trac. > > > > With two emails being sent (one to the owner and another to the > > reporter) updating or creating a ticket takes about 30~35 seconds to > > complete which is not acceptable to our developers. > > > > Is there workaround for this? I was thinking of making the > > notification component asynchronous but didn't know how to go about > > doing that. Or am I just missing a configuration item? > > > > Mark > > _______________________________________________ > > Trac mailing list > > [email protected] > > http://lists.edgewall.com/mailman/listinfo/trac > > > > -- > Evolution: Taking care of those too stupid to take care of themselves. > _______________________________________________ > Trac mailing list > [email protected] > http://lists.edgewall.com/mailman/listinfo/trac > _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
