LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   outlook users having "your imap server has closed the connection" problems (https://www.linuxquestions.org/questions/linux-server-73/outlook-users-having-your-imap-server-has-closed-the-connection-problems-527843/)

fedora_user 02-12-2007 11:23 AM
outlook users having "your imap server has closed the connection" problems
 
im running postfix on rhel4 and the problem is that all the outlook 2003 users connecting to it to check for mail get this error "your imap server has closed the connection. this may occur if you have ledt the connection idle for too long". This happens when left idol. Its happening to shared as well as non shared inboxes.
i've made sure that the server timeout period settings in outlook are as longest but still have the same problem.
Can someones please help. It will be much appreciated.
Kind regards

fedora_user 02-13-2007 03:46 AM
more info
 
please let me know if there is mo info required- i heard on another website that it might be to do with the inbox format- ie if it was to be converted to mbx type then the users may not get the outlook error. But it was only a suggestion by someones and had not been tried.
Thanks in advance

fedora_user 02-26-2007 05:56 AM
any idea on this?? im sure there are lots of people who have this problem?
regards

unSpawn 02-26-2007 07:09 AM
the problem is that all the outlook 2003 users connecting to it to check for mail get this error "your imap server has closed the connection. this may occur if you have ledt the connection idle for too long".
Could retrieve the accompanying error number and look it up in the MS KB.

fedora_user 03-01-2007 07:35 AM
help
 
Thanks Unspawn

thanks for your response.
im amazed that no one has a problem as this one.
In regards to your advise there is no such error given. It simpyy says imap has closed the connection. When i request for details i get the following description:

Lost mailbox lock
Protocol: IMAP
Server: imap.ggls.edu
Port: 143

Thats all!

I think there is a setting somewhere in postfix, whereby i can increase the timout but am not sure where i can find this setting.
I will be greatful if someone can point me in right direction.

Thanks

Berhanie 03-01-2007 11:05 PM
I had a similar problem with Courier-IMAP. That problem was solved by increasing MAXPERIP, the maximum number of connections per IP address, in the imapd config file.

fedora_user 03-08-2007 08:49 AM
still no luck.....
 
unfortunately berhane i was unable to find such a parameter in postfix which will increase such a value. I still find it quite shocking that there are not many ppl out there who have this type of problem. Its getting quite annoying ot only for me but for the users as well. I hope i find an answer soon....

fedora_user 03-08-2007 10:11 AM
little more info
 
I think i might know whats causing the problem:
It seems to me that this error of imap closing conenction only occurs to inboxes that are being accessed by more than one person at any one time. A test by myself proves that. This leaves the remaining question how can an email account in postfix_ procmail be configured for multiple users to access it at once without getting the annoying outlook error?
any help??

Berhanie 03-08-2007 07:21 PM
The config file I was talking about is part of Courier-IMAP, not postfix. Which IMAP server are you using and how are you storing your mail (mbox, maildir?)

fedora_user 03-09-2007 04:58 AM
Hello

Its stored as mbox. I read somewhere that i should try changing it to mbx format. This will allow better locking of the imap inbox allowing multiple ppl to access it at any one time.
First of all, im not sure how easy that is and secondly what side affects this may have?
any suggestions..
thanks in advance

Berhanie 03-15-2007 08:31 PM
Quote:
any suggestions..
No. If you have to use UW-IMAP, then mbx might be your only choice(?) to get around the concurrency problem (although you still can't use it over NFS, from what I read). Maildir is supported by Courier and Dovecot and stores each mail in a single file. Cyrus does the same but uses a nonstandard format.

fedora_user 03-16-2007 05:58 AM
hmmm, i really didnt think it was gonna be such a lengthy issue. So basically mbx is only supported by uw-imap?
Im not sure whether its worth changing mta? Im gonna just see how bad it gets. If i get more ppl complaining then i might just have to make some changes...
thanks ne way for all the info....appreciate it.

Berhanie 03-17-2007 12:28 AM
Quote:
So basically mbx is only supported by uw-imap?
Can't say for sure, but I haven't seen it mentioned with any other IMAP server. As for the MTA, that should be less of problem, since delivering to an mbx can be effected by using a third-party delivery agent.

billymayday 03-17-2007 01:39 AM
I'm pretty sure it's an Outlook "feature" I use Dovecot and it has a specific workaround parameter for this and a couple of other client issues.

From dovecot.conf

Quote:
# Workarounds for various client bugs:
# delay-newmail:
# Send EXISTS/RECENT new mail notifications only when replying to NOOP
# and CHECK commands. Some clients ignore them otherwise, for example
# OSX Mail. Outlook Express breaks more badly though, without this it
# may show user "Message no longer in server" errors. Note that OE6 still
# breaks even with this workaround if synchronization is set to
# "Headers Only".
# outlook-idle:
# Outlook and Outlook Express never abort IDLE command, so if no mail
# arrives in half a hour, Dovecot closes the connection. This is still
# fine, except Outlook doesn't connect back so you don't see if new mail
# arrives.
# netscape-eoh:
# Netscape 4.x breaks if message headers don't end with the empty "end of
# headers" line. Normally all messages have this, but setting this
# workaround makes sure that Netscape never breaks by adding the line if
# it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..]
# commands. Note that RFC says this shouldn't be done.
# tb-extra-mailbox-sep:
# With mbox storage a mailbox can contain either mails or submailboxes,
# but not both. Thunderbird separates these two by forcing server to
# accept '/' suffix in mailbox names in subscriptions list.
# The list is space-separated.
imap_client_workarounds = outlook-idle

Berhanie 03-17-2007 11:15 AM
Putting aside problems that are specific to a particular imap client, concurrency is limited by the type of mailbox used. This is what the UW-IMAP documentation says about unix mbox:
Code:
. unix        This is the traditional UNIX mailbox format, in use for nearly
        30 years.  It uses a line starting with "From " to indicate
        start of message, and stores the message status inside the
        RFC822 message header.

        unix is not particularly efficient; the entire mailbox file
        must be read when the mailbox is open, and when reading message
        texts it is necessary to convert the newline convention to
        Internet standard CR LF form.  unix preserves UIDs, and allows
        the creation of keywords.

        Only one process may have a unix-format mailbox open
        read/write at a time.
Getting back to Dovecot, it's something I'd like to try when it ends its RC cycle.


All times are GMT -5. The time now is 04:32 PM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page