We just upgraded our Xinetd service to a new version. That should not have been problematic. However, we have a special setup. On our servers pop3 service is managed via Xinetd, because it gives us better access control and more flexible logging. Due to our restrictive secure site policy, pop3s service is mandatory for all of our customers. Until now we were able to use Xinetd to run an old-style insecure pop3 service only on localhost. This pop3 service is needed by our webmail application, which is built on top of some PEAR libraries that do not support the secure pop3s service right now.
But what happened after the upgrade? Our webmail application no longer worked. That was, because the local pop3 instances no longer responded. The solution to the problem was to replace
- only_from: localhost
with
- only_from: 127.0.0.1
Simple, isn’t it? It took me just two hours of try and error routine to figure this out. Doh!
Shameless plug: If this post was useful to you, please consider buying yourself something from one of my Amazon stores: US store, UK store, FR store, DE store, CA store. If you're not into Amazon, why not donate something to GNOME, Mozilla or Wikipedia? Thank you!
