FileZilla Client ↔ FileZilla Server: Can a single XML profile enforce timestamp preservation across FTP and SFTP?

FileZilla Client ↔ FileZilla Server: Timestamp Preservation Across Protocols

The goal is to create a repeatable development environment where a single exported XML from FileZilla Client can drive both client connections and server access control while preserving local file timestamps on the remote side.

FileZilla Client stores site-manager entries in an XML file that includes connection details and the Preserve timestamps setting. FileZilla Server, however, maintains users, groups, and permissions in a separate configuration file. FTP and SFTP protocols interpret and expose timestamps differently, and the server’s ability to honor the client‑requested timestamp depends on protocol support and server configuration.

Unresolved behavior: does a single XML profile suffice to configure both client and server for a fully automated, repeatable setup, and will the remote file’s modification time reliably match the local timestamp on both FTP and SFTP transfers?

Specific questions:

• Is the FileZilla Client XML site‑manager export sufficient to configure FileZilla Server users and permissions for automated repeatable environments?
• Does enabling the “Preserve timestamps” option in FileZilla Client guarantee that the remote file’s modification time will match the local file’s timestamp on both FTP and SFTP transfers?
• What server‑side configuration is required in FileZilla Server to honor the timestamp set by the client during an FTP transfer?