From: Anthony Chavez (no email)
Date: Fri Feb 03 2006 - 21:59:14 EST
On Thu, 02 Feb 2006 23:55:37 -0500 Jorey Bump <> wrote:
> Anthony Chavez wrote:
>> On Thu, 02 Feb 2006 20:43:04 -0500 Jorey Bump <> wrote:
>>
>>> 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?
>
> Besides the log, you can check a user's mail store to confirm that the
> message file is actually being created:
>
> ls /var/spool/imap/user/anthony
> mail -s 'test' anthony < /some/text/file
> ls /var/spool/imap/user/anthony
I've been doing just that, which works great for one-shot testing, but
in the long term, something that would be syslogged would be more
beneficial. As I've pointed out, I'm aware how configure imapd to log
more information to syslogd, which would accomplish the same thing.
> I only mention this because you seem unsure that cyrus is actually
> getting the message into the user's mail store. My guess is that this
> test will simply confirm that messages are being delivered properly.
Both of these statements are correct. However, based on the other
points made in this thread, it is more likely to be idled or Outlook
itself that is at fault.
> You can certainly check the IMAP connection on the localhost using
> telnet or imtest, but issuing IMAP commands manually will make you
> doubt the sanity of the protocol. It's better to try something
> reliable, like Thunderbird, and see if the problem still occurs.
I don't think that there are connection problems, since I'm seeing
plenty of "login" messages in the logs.
> If you want to use imtest anyway, here is a good page showing some
> interactive IMAP sessions you can mimic:
>
> http://networking.ringofsaturn.com/Protocols/imap.php
Thanks for the link! Should prove handy when debugging. ;-)
> Other culprits for the symptoms you describe include interfering email
> scanning by antivirus programs faulty DNS.
I've been careful to keep a close eye on the virus scanner we're using,
and so far, I don't see any problems with it at all.
> But seriously, try rebooting one of the workstations first to see if
> the problem disappears.
Will do, thanks.
-- 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
|
|
|