On Wed, July 15, 2009 2:57 pm, Jonathan Angliss wrote: > Oh, it is the filters plugin. The spam portion of it. It's fetching > the RECEIVED headers, then walks through them doing DNS lookups. > That's why there is a massive delay. It's performing DNS lookups > against the messages and the path it took. Yes, you nailed it with this one. It explains why the server was idle: because it will only send out so many requests and then wait for the responses. I set "$AllowSpamFilters = false;" in the filers config and the problem went away: logins now take about 2 seconds. Also, to answer why subsequent logins were fast, there is another global in the filters config: "$SpamFilters_CacheTTL = 7200;". When I changed this to "60" subsequent logins were just as slow as the first. So it all makes sense. And finally, since this resolution was so specific I am able to leave the filters plugin enabled for the users who actually have filters - with this fix we just disable the portion not being used. Thanks for your help! -Eric ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
