> Date: Wednesday, August 12, 2015 22:22:22 +0100 > From: Dr J Austin <ja at maui.jaa.org.uk> > > > Many thanks to Alexander, Richard, Jonathan and m.roth > > The Magic incandation ! > > portrelease dovecot > service cyrus-imapd restart > > [root at maui:/etc/named]$ cat /etc/portreserve/dovecot > imap > imaps > pop3 > pop3s > > My total ignorance of portrelease/portreserve has been a bit > of a problem! > > Now to fix it permanently and get evolution back in one piece > > But why was cyrus able to use imap, pop3 & pop3S but not imaps? > > John > > Look in /etc/portreserve/ and look at the files there (both the names on the files and their contents). That will give you a sense of what services are covered. Your previous netstat output indicated that portreserve was "holding" both 143 (imap) and 993 (imaps). Since we were focusing on imap I didn't ask for netstat for other ports, so don't know what else it might have been "holding". [snip ... ] > ------------------------------------------------------------------ > -- >> What did you configure in your DNS and set in /etc/hosts? Please >> provide last one. >> > I am running a DNS server on maui that is updated by DHCP as > required > The zone file looks like this at the moment > IPs between range 148.197.29.129 148.197.29.253 ; > are dynamic, the rest are fixed > > [root at maui:/var/named/chroot/var/named/dynamic]$ cat > jaa.org.uk.zone > $ORIGIN . > $TTL 86400 ; 1 day > jaa.org.uk IN SOA maui.jaa.org.uk. ja.jaa.org.uk. ( > 200714349 ; serial > 7200 ; refresh (2 hours) > 300 ; retry (5 minutes) > 604800 ; expire (1 week) > 60 ; minimum (1 minute) > ) > NS maui.jaa.org.uk. > MX 10 maui.jaa.org.uk. > $ORIGIN jaa.org.uk. > $TTL 43200 ; 12 hours > android-54f4af51ba23308b A 148.197.29.251 > TXT > "31d805ae3efb12d6a37351a28b581c9142" > $TTL 86400 ; 1 day > draytek A 148.197.29.254 > $TTL 43200 ; 12 hours > ferrari A 148.197.29.183 > TXT > "310fc27c6e505544502e0a12fb2192d64a" > $TTL 86400 ; 1 day > maui A 148.197.29.5 > $TTL 43200 ; 12 hours > paxos A 148.197.29.159 > TXT > "315dff374b9faae33e5457b537bb671bd9" > $TTL 86400 ; 1 day > zyxel A 148.197.29.2 > ------------------------------------------------------------------- > [root at maui:/etc/named]$ cat /etc/hosts > 127.0.0.1 localhost.localdomain localhost maui ># 127.0.0.1 localhost.localdomain localhost > ::1 maui.jaa.org.uk maui localhost6.localdomain6 localhost6 > 148.197.29.5 maui.jaa.org.uk maui > I'm not certain where that's coming from. That will all work internally (assuming internal consistency), but the outside world has a rather different view. The information returned by whois for jaa.org.uk (which has your name as registrant) shows: Name servers: ns.hosteurope.com ns2.hosteurope.com as the nameservers for that domain. If you do a "dig" against either of those servers for your maui host: dig @ns.hosteurope.com maui.jaa.org.uk you get: maui.jaa.org.uk. 14400 IN A 213.152.52.233 An rDNS lookup on that IPnumber returns: 233.52.152.213.in-addr.arpa. 56246 IN PTR jaa.org.uk. while the rDNS on 148.197.29.5 returns: 5.29.197.148.in-addr.arpa. 50161 IN PTR adarwash1.ee.port.ac.uk which matches the forward lookup: adarwash1.ee.port.ac.uk. 86400 IN A 148.197.29.5 So, the outside world has a rather different view of what your ipnumber(s) are than you seem to be getting/using internally.