On Tue, Dec 14, 2010 at 02:15:33PM +0100, Niels den Otter wrote: > On Tuesday, 14 December 2010, Harry Strongburg wrote: > > I am trying to send an email to a literal IPv6 address in mutt and > > it does not work for me. "To: t...@[2001:470:ffff:aaaa::1]", as an > > example. This won't work though for some reason, though it > > "should". It gets transformed into the editor as "To: t...@[2001: > > 470: ffff: aaaa: ;" Even if the user corrects the malformed > > literal IP in their editor, mutt will say "No recipients are > > specified!" when trying to send. > > > > I read the docs for a bit and couldn't find much on it. Might it > > be a bug, or am I doing something wrong here? > > What would you expect this to do? For IPv4 this isn't valid either I > believe. Just tried what would happen and postfix reports; > > <ot...@10.1.178.225>: bad address syntax > > > -- Niels
Did you wrap it in square brackets? postfix accepts: user1:us...@[127.0.0.1] in the aliases file, so why shouldn't it accept it as a proper email (as it *is* a proper email)? As to the original question, has the RFC been updated to accept IPv6 addresses in that format? It's a little-used format (comparitively) so I would expect that mutt probably only accepts IPv4 addresses in the square brackets if it accepts that format at all. -- Brandon
