Hi. I have two questions that don't appear to be answered anywhere:
- Many of my users use a fetchmail ssh tunnel to get their mail.
Typically this looks like
poll 140.247.60.120 with proto imap:
plugin "ssh -2 %h /usr/sbin/imapd" auth ssh;
uw-imapd provides a binary /usr/sbin/imapd that can be used for an
ssh-imap tunnel. I found /usr/lib/dovecot/imap (in Debian) which
might work as a replacement, except that it appears that running
/usr/lib/dovecot/imap doesn't properly read in the configuration
file--for example, it is trying to create dotlocks, but in the
configuration I have flock. Is there any way I can do what I want to
do here?
- Dovecot seems to be dying spontaneously in conjunction with
SquirrelMail. Do you have any experience of this? SquirrelMail ends
up reporting that there was no response to the CAPABILITY query. If I
restart Dovecot, everything is fine again. I don't see anything in the
logs to indicate the problem. Any ideas why this might be happening?
Thanks for any pointers...
--
Adam Kessel
http://adam.rosi-kessel.org
On Thu, May 20, 2004 at 11:02:30PM -0400, Adam Kessel wrote:> - Dovecot seems to be dying spontaneously in conjunction with > SquirrelMail. Do you have any experience of this? SquirrelMail ends > up reporting that there was no response to the CAPABILITY query. If I > restart Dovecot, everything is fine again. I don't see anything in the > logs to indicate the problem. Any ideas why this might be happening?I suppose I should have mentioned that this is Debian sid, so Dovecot 0.99.10.4 and SquirrelMail version 1.5.0. Not using pgsql or ldap. -- Adam Kessel http://adam.rosi-kessel.org
> I suppose I should have mentioned that this is Debian sid, so Dovecot > 0.99.10.4 and SquirrelMail version 1.5.0. Not using pgsql or ldap.What happens if you telnet to e.g. port 143 when this is happening? Do you get a response from dovecot? I ask because I was experiencing the same symptom on a Debian (testing) machine a couple of months back. I had some assistance from Jaldhar but didn't get much closer to the answer. Eventually I put it down to low memory problems (it was a virtual-mode Linux server and had memory probs with other apps) and shifted to a real server with plenty of RAM. That's now also running Debian sid, dovecot and Squirrelmail without any problems. Cheers, Julian.
On Fri, 2004-05-21 at 06:02, Adam Kessel wrote:> uw-imapd provides a binary /usr/sbin/imapd that can be used for an > ssh-imap tunnel. I found /usr/lib/dovecot/imap (in Debian) which > might work as a replacement, except that it appears that running > /usr/lib/dovecot/imap doesn't properly read in the configuration > file--for example, it is trying to create dotlocks, but in the > configuration I have flock. Is there any way I can do what I want to > do here?imap doesn't read configuration file at all, it expects all it's configuration to be in environment variables. I've in TODO to make "dovecot --exec-mail imap" or something like work, which would just read the config and execute imap process. For now you could set the config manually, such as MBOX_LOCKS=fcntl. The environments are only listed in src/master/mail-process.c> - Dovecot seems to be dying spontaneously in conjunction with > SquirrelMail. Do you have any experience of this? SquirrelMail ends > up reporting that there was no response to the CAPABILITY query. If I > restart Dovecot, everything is fine again. I don't see anything in the > logs to indicate the problem. Any ideas why this might be happening?Does it try to use SSL? Probably not.. hmm. It needs a restart to get working again? Some people have said that they need to restart dovecot once in a while or it stops responding. I haven't really figured that out yet. What does ls -l /proc/dovecot-pid/fd/ show then? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20040522/f58b0542/attachment-0001.bin>