> Next, when you do your TELNET test, do you see an imapd process on > your system? If you do not see an imapd process, then something is > wrong with your inetd and/or firewall setup.
I see no process when telnet hangs in other window: (when telnet to 110, ipop3d *does* spawn a process..... [EMAIL PROTECTED] ~> ps aux | grep imap [EMAIL PROTECTED] ~> I dont see how inetd.conf could be wrong: [core01] # cat /etc/inetd.conf | grep imap imaps stream tcp nowait root /usr/local/libexec/imapd imapd imap stream tcp nowait root /usr/local/libexec/imapd imapd All with correct spacing etc If I do the TELNET it is on the same machine as the proposed imapd, so no FW rules in effect, and the related imap rules are in the same (correct) syntax as for example the pop or smtp rules: $cmd allow tcp from any to me 110 in via $pif setup limit src-addr 15 $cmd allow tcp from any to me 25 in via $pif setup limit src-addr 15 $cmd allow tcp from any to me 143 in via $pif setup limit src-addr 15 $cmd allow tcp from any to me 993 in via $pif setup limit src-addr 15 *seriously losing the plot* Thanks, -Jeffrey > If there is an imapd process, try attaching to it in gdb and getting > a stack trace. I don't see how imapd could be hanging since you say > that ipop3d is running fine and ipop3d does all the same things at > startup that imapd does. But if it is hanging, the stack trace > ought to say what is wrong. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. -- Open WebMail Project (http://openwebmail.org) _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
