Correct, you need to add the FQDN, not the hostname. This is by design, think broader as in clustering.
-- Jeremy McSpadden Flux Labs, Inc | http://www.fluxlabs.net | Endless Solutions Office : 850-250-5590x101 | Cell : 850-890-2543 | Fax : 850-254-2955 On Jul 12, 2013, at 8:34 AM, Chris Malton <[email protected]> wrote: Hi all, I'm midway through producing a puppetised installation of our mail gateways, which includes, among other things, baruwa & MailScanner. One of the bits that's giving me grief is that when the production.ini configuration file is generated, I end up with something like the following in it: celery.queues = {"mailgate-01":{"exchange": "host", "exchange_type": "direct","binding_key":"mailgate-01",},"msbackend":{"exchange":"ms", "exchange_type":"fanout","binding_key":"mstasks"},"default": {"exchange": "default","binding_key": "default"}} While perfectly valid - this doesn't go down with with the web-UI, which declares that "mailgate-01" is not a valid domain name. If I then go and put mailgate-01.kegs.local (the internal FQDN), it adds in the web ui.... BUT it can't communicate with it. I have to go and tweak the production.ini to contain the internal FQDN, which is a real pain. Is there a reason that only the hostname is used, not the FQDN? If so, is there a reason that it's then impossible to add a non-FQDN in the web interface? Any suggestions on how to fix this (other than a hack with sed)? Cheers, Chris _______________________________________________ http://pledgie.com/campaigns/12056 _______________________________________________ http://pledgie.com/campaigns/12056
