Is this a well known behaviour or is this to be considered as a bug?
The at-sign ([EMAIL PROTECTED]) is internally used as field separator for the port-number, so that when using a login like [EMAIL PROTECTED] for authentication will lead to this exception, as “domain” is an invalid port number… Has anybody got an workaround or a solution?
