On 18.02.2013, at 07:49, Timo Sirainen <tss@iki.fi> wrote:
On Sun, 2013-02-17 at 12:30 +0200, Timo Sirainen wrote:
(So yeah, ideally there should be checks for detecting hostname hash collisions..)
Added to v2.2 hg:
% doveconf -H dovecot%2d No duplicate host hashes in dovecot0 .. dovecot99
With "doveconf -H dovecot%9d" I do end in tons of reported collisions like ... | doveconf: Error: Duplicate host hashes: dovecot1368344 and dovecot2055005 | doveconf: Error: Duplicate host hashes: dovecot2042008 and dovecot2056918 | doveconf: Error: Duplicate host hashes: dovecot1844965 and dovecot2058312
(No wonder, I am running 2.1 replicator with identical local hostnames for some time now.)
... and ending with: | Killed
doveconf -H without the template it attempts to detect it from the current hostname.
mail> doveconf -H doveconf: Fatal: Hostname 'xxx.yyy.tld' has no digits, can't verify
JFTR and regards, Michael