FTP Queue Server
Design Overview
The goal was to develop a revision to the standard FTP server which allows people to request permission to upload or download files. The permission request is done by sending specially formatted email commands to a predefined email address (like FTP@YOURDOMAIN.COM). This would then allow the FTP server which polls the mail server for new email requests to generate a reply with a User ID and Password which are generated on-the-fly by the FTP Queue Server.
Upon completion of upload or download, the notification list of email address(es) is informed that the new file exists, or the download was successful.
Our initial market was for the print industry, allowing them to manage their FTP better. In said industry, consumers will actually upload files without informing the business that the file is there, when it is due, and what to actually do with the file. This design allows the business to enforce their own "Submission Form" before the consumer can actually upload. At first, this may be confusing to the user, but in the long-run eliminated stray files and upset customers.
Technical Overview
The goal was to develop a revision to the standard FTP server which allows people to request permission to upload or download files. The permission request is done by sending specially formatted email commands to a predefined email address (like FTP@YOURDOMAIN.COM). This would then allow the FTP server which polls the mail server for new email requests to generate a reply with a User ID and Password which are generated on-the-fly by the FTP Queue Server.
Upon completion of upload or download, the notification list of email address(es) is informed that the new file exists, or the download was successful.
Our initial market was for the print industry, allowing them to manage their FTP better. In said industry, consumers will actually upload files without informing the business that the file is there, when it is due, and what to actually do with the file. This design allows the business to enforce their own "Submission Form" before the consumer can actually upload. At first, this may be confusing to the user, but in the long-run eliminated stray files and upset customers.
Technical Overview
- Configuration is initially done during installation. Contains information like listener port, ip address to the mail server, email login credentials, etc. Once the server has started, the configuration file is removed and all configuration changes are managed via email. (Once you have established two communications between the administrator and the the FTP Queue Server email account).
- Listener is on standard port 21, however when a connection is received the listener looks to see if it was expecting any new connections (Queue). If not, it optionally informs the visitor to email the account the FTP Queue server monitors. Like FTP@YOURDOMAIN.COM
- Notification List upon completion of any task, the FTP Queue server will inform the addresses found in the notification list. This is great to let one or more people know to pull a file and match it to the upload request. (Which is done automatically via the email notification).