From: Anthony Chavez (no email)
Date: Thu Feb 02 2006 - 23:02:23 EST
On Thu, 02 Feb 2006 20:43:04 -0500 Jorey Bump <> wrote:
> Anthony Chavez wrote:
>
>> Nevertheless, either Cyrus still doesn't recognize that the mail has
>> been received (even though Postfix logs that it has been passed to
>> Cyrus) or there is an issue with Outlook that prevents the recipient
>> From seeing the message for a variable amount of time---I'd say about 5
>> minutes on average, though sometimes it takes hours.
>
> It's easy enough to monitor a mailbox to see if new messages are being
> delivered.
Okay, besides tcpdump (which really isn't an option in this case because
all of my users are using imap over TLS), what do I have at my disposal?
I had the following configured in /etc/syslog.conf:
!imapd
local6.=info /var/log/maillog
I like to keep it at this level to keep the noise down in maillog. I
changed the line to "*.* /var/log/maillog", SIGHUP'ed, and sent a test
email. The logs that were generated by Cyrus in this new configuration
did little more for me than confirm that the logs generated by
postfix/lmtp framed the entire conversation between it and lmtpd and
that if postfix/lmtp logs "250 2.1.5 Ok," then I can rest assured that
the message has been recorded in Cyrus' mail store.
I guess there really isn't much else to ask for, but I'd still be
interested to know if there is anything else relevant that might be of
assistance.
> Also, you don't mention any other clients -- what happens with
> Thunderbird, for example?
I will be deploying a Webmail server (Horde) for this client in the very
near future. Based on the responses I've received in this thread thus
far, I'm not anticipating any problems.
>> This problem trickled in slowly, but have become increasingly worse, to
>> the point that many of my users are using Yahoo mail because our mail
>> server is "unreliable." As such, I'm *EXTREMELY* interested in fixing
>> this problem.
>
> I have seen such problems occur when Outlook is left running for long
> periods of time. Believe it or not, a complete reboot of Windows is
> often necessary. Simply restarting Outlook is not always sufficient.
I seem to recall reading about some issue with Outlook throwing a temper
tantrum when it can't get its way. I don't remember the exact details,
but it seems like the end result of which is that it floods the server
with multiple connection attempts (or something similar), which bogs
down performance on the server to the point of affecting every user on
the network. Can anyone confirm this?
-- Anthony Chavez http://anthonychavez.org/ mailto: jabber:
---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|