Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: synchronizing directories/files with "illegal" names

Is this a bug, or have I missed something important?

Windows does not support colons in filename. WinSCP is not yet able to cope with synchronization of such files.
Antony

Re: synchronizing directories/files with "illegal" names

Hi,

Having a similar problem.

Am tyrying to synchronize files with names like

1218094619.P8894Q0M368114.excalibur:2,S

from a .maildir directory of an IMAP server.

The files move OK and are renamed to (as expected)

1218094619.P8894Q0M368114.excalibur%3A2,S

Unfortunately, repeat synchronisation sees them as new filename and "synchronises" then again.

Is this a bug, or have I missed something important?

Many thanks

Antony
martin

Re: synchronizing directories/files with "illegal" names

This issue is being tracked already.
dberger

synchronizing directories/files with "illegal" names

Windows can't handle directory names ending in "." (dot), and forbids the use of certain characters in file/directory names (?, for example).

I'm going to describe the problem in terms of a directory with a trailing dot, but the same problem applies to files with restricted characters in their names.

When WinSCP is synchronizing a remote directory structure, such names are written locally without the trailing dot, which is fine.

Unfortunately, on subsequent synchronizations, WinSCP wants to delete the local directory (without the trailing dot) and re-transfer the remote directory (with the trailing dot).

So if I sync my music between a linux machine and a windows machine for example, WinSCP wants to delete "r.e.m" and re-transfer "r.e.m." every time, even if nothing in that directory has changed.