Dear Mark,

Replies interleaved with your message, below:

On Fri, 28 Oct 2005, Mark Crispin wrote:

> The first thing is that the ipop[23]d and imapd daemons do *NOT* listen on 
> the ports; they just do stdio.  The listener is either inetd, xinetd, or 
> launchd.

Now that is something I did not know.  That explains why they
would not "listen" on the ports even when I started them manually.

Question: do pop2 and pop3 both have to be started, or is one
or the other optional to have POP working?

> 
> Since the daemons do not listen, they don't do any hosts.allow processing 
> either.  That is done entirely by TCP wrappers, inetd, xinetd, or launchd 
> depending upon how your system is setup.
>

OK, but the service labels used in hosts.allow would be (if
any) things like imap, pop, etc., not xinetd and launchd, no?
 
> In your case, the answer is probably "launchd".
>

Correct, though I might be able to use xinetd if need be.
 
> I can't vouch for any third-party distributions. Have you tried obtaining 
> the software directly from the UW FTP server on:
>       ftp://ftp.cac.washington.edu/mail/imap.tar.Z
> and then building using the command:
>       make oxp
>

Actually, I thought that it was the very same thing.
 
> For what it's worth, I have a Mac Mini at home and run the servers using 
> xinetd instead of launchd.  I didn't want to be bothered to learn how to 
> use launchd; it's enough effort to keep track of inetd and xinetd.
>

It does appear to be some Byzantine in structure and usage.
 
> However, someone once sent me a launchd script that he claimed works for 
> imapd.  I haven't looked to see how it differs from yours.
> 
> <plist version="1.0">
>    <dict>
>       <key>Disabled</key>
>       <false/>
>       <key>Label</key>
>       <string>imap4</string>
>       <key>ProgramArguments</key>
>       <array>
>         <string>/usr/local/libexec/imaps</string>
>       </array>
>       <key>inetdCompatibility</key>
>       <dict>
>         <key>Wait</key>
>         <false/>
>       </dict>
>       <key>Sockets</key>
>       <dict>
>         <key>Listeners</key>
>         <dict>
>               <key>SockServiceName</key>
>               <string>imaps</string>
>               <key>Bonjour</key>
>               <false/>
>         </dict>
>       </dict>
>    </dict>
> </plist>
> 

This did the trick, as far as startup goes!

I find that imap refuses to accept my login, and pop3 does
not appear to be doing anything.  Do both of these rely on 
pam.d?

Rich

> -- Mark --
> 
> http://staff.washington.edu/mrc
> Science does not emerge from voting, party politics, or public debate.
> Si vis pacem, para bellum.
> 

-- 
************************************************
Richard Bonomo
UW Space Astronomy Laboratory
ph: (608) 263-4683 telefacsimile: (608) 263-0361
SAL-related email: [EMAIL PROTECTED]
all other email: [EMAIL PROTECTED]
web page URL: http://www.cae.wisc.edu/~bonomo
************************************************

_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to