View previous topic :: View next topic |
Author |
Message |
tparker Tux's lil' helper
Joined: 03 Oct 2002 Posts: 85
|
Posted: Sun Jun 01, 2003 10:27 am Post subject: IMAP problem after update |
|
|
After updating my IMAP server (uw-imap 2002d) users can now no longer check mail with either IMAP nor POP (both using SSL and non-SSL).
The system logs appear with the entries:
Jun 1 19:19:44 [xinetd] START: imap2 pid=5973 from=81.101.209.128
Jun 1 19:19:44 [xinetd] FAIL: imap2 address from=81.101.209.128
Jun 1 19:19:44 [xinetd] EXIT: imap2 pid=5973 duration=0(sec)
I'm assuming that the problem is authentication related, but do not know. I have checked /etc/xinetd.d/imap (and imaps , pops etc...) but they have not been changed. They worked before, on the following settings (allowing for obvious differences between the SSL / non-SSL versions):
service imaps
{
socket_type = stream
wait = no
user = root
server = /usr/sbin/imapd
server_args = /etc/mail/mail.pem
# log_on_success += DURATION USERID
log_on_success += HOST DURATION
log_on_failure += USERID
disable = no
}
On another note, when I originally installed IMAP (months ago, when it worked) I had to change DURATION USERID (the default) to HOST DURATION. I don't actually know what this does, but this change worked. Neither work now.
I do notice that /etc/pam.d has updated imap and pop files since my emerge -u of uw-imap. Problem is, I don't know what was changed or if this has screwed things up. They now read:
#auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
- the first line was included too, which I have now commented (thinking this would work) but it made no difference.
I'm now out of ideas. Anyone know what's wrong? Webmail continues to work.
Thanks!
Terence |
|
Back to top |
|
|
tparker Tux's lil' helper
Joined: 03 Oct 2002 Posts: 85
|
Posted: Mon Jun 02, 2003 7:21 am Post subject: Problem Fixed |
|
|
Just for reference to say that i've found the source of the problem... it has nothing to do with uw-imap.
For some reason, /etc/xinetd.conf has been changed such that only_from = localhost. I don't know how that happened but presumably it was with a recent upgrade of xinetd.d (though... it worked after the upgrade UNTIL I updated uw-imap, which shouldn't change xinetd.conf anyway).
But anyways... nevermind... that now reads only_from=0.0.0.0 and all is fine. |
|
Back to top |
|
|
nitro322 Guru
Joined: 24 Jul 2002 Posts: 596 Location: USA
|
Posted: Tue Jun 03, 2003 6:55 pm Post subject: |
|
|
I just wanted to say thanks for the heads-up on this. I got hit by this too, but for some reason it wouldn't even allow connections from 127.0.0.1, so Squirrelmail quit working. I kept thinking it was an IMAP problem, but after reading this post I check xinetd.conf, and sure enough that was it. Thanks! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|