severity #392831 important # a workaround is available: use a colon-separated list thanks
On Fri, Oct 13, 2006 at 11:42:48PM +0200, Marc Haber wrote: > On Fri, Oct 13, 2006 at 09:34:50PM +0200, Alexandre Fayolle wrote: > > But it is probably better to have both lists use the same separator. > > If exim4 expects colons, the config script could sed s/;/:/ that line > > before writing it in the update-exim4.conf.conf file. > > The actual fix will be a little harder, since older installs might > actually still use a colon-separated list. We need to detect whether > semicolons or colons were used as separator and generate the > appropriately correct replacement value. Actually, your suggested fix is fine. Domain names can neither contain colons nor semicolons, so we can safely replace and pass colon separated lists to exim regardless of what is entered. It's the most easy way. Sorry for not seeing this last night. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]