OK...so I managed to restart my system and tried again to access.

Now I have Winscp 1.4.8 (build 415), and now everything works.

For me the bug is dead. Thanks!

Hi, I'm expecting the same annoyance too.

My hoster gave me an FTP username with the @ symbol inside it.

I have Vista X64 + Winscp 4.1.6 (build 412)

Whenever I try to access my site using FTP mode, I figured Winscp automatically change my username, converting it to the part before the @ symbol.

Example:
my username is "[email protected]"
when I set winscp connection up and try to connect, the username sent to the FTP server becomes just "whatever".

Thanks anticipately for every response and keep up the good work!

P.S.: I've already updated to 4.1.8, but right now I can't simply restart my PC, sry!

Can you provide me your email address, so I can send you a debug version of WinSCP to track the problem? If you do not want to post the address here, you can send me an email. You will find it (if you log in) in my forum profile. Please include link to this topic. Thanks.

Ok, I did some further testing myself... I ran the latest WinSCP version on my old computer, and... I can login!

The only difference I see between these 2 environments is that the old computer runs XP SP3 and that my new one is a downgraded Vista (to XP SP3).

I don't know if there could be any difference (functionality/code/api wise) between XP SP3 and a downgraded Vista? Does WinSCP use Windows libraries for FTP connectivity?

There's definitely no test.
I'll test it myself later.

I tried it with 4.1.5 (I still have it on my old computer) and it works.

Can you confirm that there is check on the username? I.e. if you try to connect to a server, that normally takes a while to respond, do you get an immediate error message saying that the username is invalid when you put an @ in the username? (that would be a good indication that there is an actual client side check on the username)

I give in the username via the Login dialog. I tested the command line, and I get the same error screen.

BTW, where do you type the username? On command-line or on Login dialog?

Can you try again with 4.1.5? I'm not aware of similar change.

Hi,

I have to connect to an ftp server with a username that contains an @ sign. (I know, stupid idea to put @ signs in usernames, not my decision...)

Thing is, that used to work perfectly under WinSCP 4.1.5, but not with the latest version (4.1.7). It complains, immediatly after I click Login:

Connection failed.
Wrong user name format was entered. For more information, press help button of your control panel.

So I think WinSCP now has a filter for 'invalid' usernames. I tried replacing the @ sign with %40, but that doesn't work either:

Connection failed.
Domain is not recognized. Please contact your hosting provider to resolve this issue.

I suggest WinSCP removes this check for invalid usernames in the next release.

Thank you for an otherwise perfect product :)

Hopla