This is a discussion on Problems accessing mailbox from pop3 within the alt.comp.mail.qmail forums, part of the Mail Servers and Related category; I'm having some problems with qmail set-up. Here is the output after installing. I can't connect from ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I'm having some problems with qmail set-up. Here is the output after
installing. I can't connect from a pop3 mail client. Where should I be looking to see if I've properly configured? [jjb@localhost jjb]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK <19384.1064170892@xxx.net> user postmaster@xxx.net +OK pass xxxxx +OK quit +OK Connection closed by foreign host. [jjb@localhost jjb]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK <19812.1064170978@xxx.net> user postmaster@xxx.net +OK pass xxxxx +OK list +OK 1 913 2 5102 3 4483 4 5053 5 2322 6 1721 7 1763 8 1663 9 2006 10 1944 .. quit +OK Connection closed by foreign host. [jjb@localhost jjb]# |
|
|||
|
"jbottero" <jbottero@botteronet.com> writes:
> I'm having some problems with qmail set-up. Here is the output after > installing. I can't connect from a pop3 mail client. Where should I be > looking to see if I've properly configured? From the tests you ran, you can see that the service itself is working. So the problem could be either on the client, or somewhere between the client and the server--i.e., a firewall at your ISP or on the server itself. If you're running iptables/ipchains or some other packet filtering software, make sure that's not blocking the connection. If that's not it, check with your ISP. -- Dave Sill Oak Ridge National Lab, Workstation Support Author, The qmail Handbook <http://web.infoave.net/~dsill> <http://lifewithqmail.org/>: Almost everything you always wanted to know. |
|
|||
|
Dave Sill <MaxFreedom@sws5.ornl.gov> wrote in message news:<wx0d6dt7zyc.fsf@sws5.ornl.gov>...
> "jbottero" <jbottero@botteronet.com> writes: > > > I'm having some problems with qmail set-up. Here is the output after > > installing. I can't connect from a pop3 mail client. Where should I be > > looking to see if I've properly configured? > > From the tests you ran, you can see that the service itself is > working. So the problem could be either on the client, or somewhere > between the client and the server--i.e., a firewall at your ISP or on > the server itself. If you're running iptables/ipchains or some other > packet filtering software, make sure that's not blocking the > connection. If that's not it, check with your ISP. The machine is sitting behind a router / firewall in the room next to me, and the guy who controls the router assures me that the proper ports are open. I think I have very minimal iptable filtering at the moment (though it's very high on the list of things getting done, I also have a hardware firewall that should not be giving me issues). Perhaps I'm simply not understanding how qmail is configured. For example, if I wish to use some mail client for pop3 access, what is the server name? I believe that the only info that I fed it was ../config-fast xxx.net where, of course, xxx.net is a FQDN. Is an MX record even necessary since I'm not having some other (for example a service) domain handle my mail? |
|
|||
|
Dave Sill <MaxFreedom@sws5.ornl.gov> wrote in message news:<wx0d6dt7zyc.fsf@sws5.ornl.gov>...
> "jbottero" <jbottero@botteronet.com> writes: > > > I'm having some problems with qmail set-up. Here is the output after > > installing. I can't connect from a pop3 mail client. Where should I be > > looking to see if I've properly configured? > > From the tests you ran, you can see that the service itself is > working. So the problem could be either on the client, or somewhere > between the client and the server--i.e., a firewall at your ISP or on > the server itself. If you're running iptables/ipchains or some other > packet filtering software, make sure that's not blocking the > connection. If that's not it, check with your ISP. Nevermind. I'm an idiot. I went back and checked iptables and that was where my problem was. Thanks... |