At 10:09 PM -0800 12/21/00, Jason wrote:
> I think the reason why it was even connecting and showing up in netstat
> -ta printout was because I had ipop3d running through inetd.conf.
>
> I want popper to run in server mode. So it should be an always running
> process, right? Like httpd. When I do popper -s nothing seems to happen.
Server mode and standalone mode are different. You can use either,
both, or none.
If you didn't compile with '--enable-standalone' then it's in inetd
mode. You need to have inetd launch it. See the INSTALL file for
details. If you want it to be always running then you need to
compile with '--enable-standalone' and launch it (and have it
launched on system start).
>
> I also commented the ipop3d from inetd.conf and now pop3 isn't open, so
> it wasn't popper that was working before. So, how do I even get popper
> started?
>
> -juka
>
> Kenneth Porter wrote:
>
>> [Please use a meaningful subject line.]
>>
>> On Thu, 21 Dec 2000 21:33:27 -0800, Jason wrote:
>>
>> >I'm on an internal machine right now testing it out, the ip is
>> >10.0.0.1. When I use netscape to connect to the router/pop server,
>> >either using it's external ip address, or it's internal one I get an
>> >error from netscape saying please contact the administrator.
>>
>> Try telnet'ing to port 110 of either interface and see if you get
>> qpopper's banner.
>>
>> Since you're running ipchains, do you have port 110 open?
>>
>> Ken
>> mailto:[EMAIL PROTECTED]
>> http://www.sewingwitch.com/ken/
