On 08/09/2013 04:28 AM, Patrick Nommensen wrote:
>>> I have imap_proxy listening on port 21849. The important settings in the
>>> proxy conf file are:
Do you get a connection if you telnet to that port:
# telnet localhost 21849
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE AUTH=LOGIN XIMAPPROXY]
(...)
>>> listen_port 21849
>>> listen_address 127.0.0.1
>>> server_port 143
I guess you have server_address somewhere too... :)
What does "pimpstat" say?
You can also check if imapproxy is really listening and on what port:
# netstat -lnp | grep imapproxy
tcp 0 0 127.0.0.1:143 0.0.0.0:* LISTEN 28267/in.imapproxyd
This means that the process with pid 28267 is in.imapproxyd and it is
listening on port 143 on the address 127.0.0.1. (This is as how we run it.)
Regards,
/skitta
--
Tomas 'Skitta' Lindroos.
UNIX systemadministratör, Åbo Akademi, Datacentralen
E-post: [email protected]. Telefon: 02-215-4469, +358-40-5177716
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
-----
squirrelmail-imapproxy mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy