dovecot - Aug 2006 - Dynamic server address

Hi!

My mail server (ubuntu breezey badger) is connected by ADSL and has a
dynamic address. I have noticed that, every day after the IP address
changes, dovecot is no longer reachable from the net. Iguess this is because
dovecot doesn't register this change and continues to listen on a
non-existing interface/address.

I'm trying to solve this problem by putting a script in /etc/ppp/ip-up/
dovecot
--===---
#!/bin/sh
# By kresho
# dovecot ip-up script (/etc/ppp/ip-up.d/dovecot)
#

/etc/init.d/dovecot restart
---===---

So far, it seems to work.

I doubt I'm the first one to come across this problem, yet I couldn't
find
anything similar on google.

Any comments?
-- 
kresho
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20060808/2a44db1f/attachment-0001.html>

Kresimir Tonkovic wrote:
> My mail server (ubuntu breezey badger) is connected by ADSL and has a 
> dynamic address. I have noticed that, every day after the IP address 
> changes, dovecot is no longer reachable from the net. Iguess this is 
> because dovecot doesn't register this change and continues to listen 
> on a non-existing interface/address.
> Any comments?
Just make it listen on 0.0.0.0?

johannes

---------- Forwarded message ----------
From: Alan Premselaar <alien at 12inch.com>
Date: Aug 8, 2006 9:56 AM
Subject: Re: [Dovecot] Dynamic server address
To: kresimir.tonkovic at gmail.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kresimir Tonkovic wrote:
>
>
> On 8/8/06, *Johannes Berg* <johannes at sipsolutions.net
> <mailto:johannes at sipsolutions.net>> wrote:
>
>     Kresimir Tonkovic wrote:
>     > My mail server (ubuntu breezey badger) is connected by ADSL and
has
a
>     > dynamic address. I have noticed that, every day after the IP
address
>     > changes, dovecot is no longer reachable from the net. Iguess this
is
>     > because dovecot doesn't register this change and continues to
listen
>     > on a non-existing interface/address.
>
>     > Any comments?
>     Just make it listen on 0.0.0.0 <http://0.0.0.0>?
>
>     johannes
>
>
> Not an option. I want local users to connect by pop3 and remote by pop3s.
>
> --
> kresho
Kreshmir,

  You should still be able to achieve that by using tcpwrappers or
iptables to restrict access on the appropriate networks.

Alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE2EPDE2gsBSKjZHQRAv/jAKDkf/E2nlZ5+aNeTHuMdX2iw46tyACfTp5w
lnQZjQnRtG6O0hB6gFq0tjk=xgKj
-----END PGP SIGNATURE-----

Alan, I believe we should keep the discussion on the list :-) Please "reply
all"

Correct me if I'm wrong, by default POP3 and POP3+SSL both work at the same
port, 110. I want to let local users connect by plain POP3 and external
users to use POP3+SSL. I don't see how I can set this up using iptables and
tcpwrappers. Can you please provide more details?
-- 
kresho
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20060808/95703b47/attachment-0001.html>

Kresimir Tonkovic wrote:
> Correct me if I'm wrong, by default POP3 and POP3+SSL both work at the 
> same port, 110. I want to let local users connect by plain POP3 and 
> external users to use POP3+SSL. I don't see how I can set this up 
> using iptables and tcpwrappers. Can you please provide more details?
Ah, so you don't want to use pop3s but pop3+starttls. Just tell dovecot 
to deny any password when used over insecure connections. local 
connections are considered secure.

johannes