This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dataexchange:what_properties_has_ftp_account [2015/08/03 13:16] – fw | en:dataexchange:what_properties_has_ftp_account [2022/05/12 17:24] (current) – [Security] fw | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | Each client has access to a FTP directory with this structure. | + | Each client has access to a SFTP directory. Import and export processes work with this as source and target. |
| - | {{: | + | ===== Structure ===== |
| + | SFTP directory has this structure: | ||
| + | {{: | ||
| - | ==== Options ==== | ||
| - | If needed, this structure can be divided into | ||
| - | * FTP-server for data exchange | + | ===== Security ===== |
| - | * FTP-server for image files and landingpages | + | |
| - | These servers can be hosted by promio.net | + | Access allowed via encoded secureFTP-process with keyfiles |
| - | This flexibility allows convenient solutions. The promio.mail data directory can be implemented into the user’s desktop as a file share directly. Alternatively, | ||
| + | <WRAP round info 80%> | ||
| + | Data should remain on the server for the purpose of exchange only and should consequentially be deleted afterwards. These servers are not intended to serve as an archive. | ||
| + | </ | ||
| - | ==== Security ==== | ||
| - | Access allowed via FTP or secureFTP (ssh2). We recommend the encoded secureFTP-process with keyfiles. | ||
| - | + | {{tag>SFTP data_exchange imports exports | |
| - | <WRAP center round info 80%> | + | |
| - | Data should remain on the server for the purpose of exchange only and should consequentially be deleted afterwards. These servers are not intended to serve as an archive.</ | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | {{tag> | + | |