Automated Commands

This functionality allows your users to send certain commands to quickSMTP and these commands will be executed as soon as the email is received, as well as during queue runs. To have this functionality running, you must have properly set the Service Account of your server.

In order to trigger this functionality, your user has to send an email with subject:


Emails with subject different than Commands will be ignored.

Next step is to authenticate. Authentication is performing by specifying the email account and its password. It is not necessary that the sender of the message and the email account specified inside the message are the same. This way one user can manage mailboxes of others.

You can decide individually for each account if Automated Commands are allowed for this particular account. There is a check-box in the account editor that let's you control permission for this activity.

Each command consists of two words - command itself and the value. Each command has to be terminated by semicolon character ( ; ). New lines do not matter - you can write everything on a single line, as long as everything is divided by semicolon. Leading and trailing spaces are also removed automatically.

In order to authenticate, the mesage has to start in the following way:

User ; Pass mypassword ;

In the example above has to be replaced with the actual mailbox address and mypassword with the password for this box. If authentication is not successful or the particular mailbox does not allow Automated Commands, quickSMTP will reply with general message for failed authentication.

Note, that all replies will be sent back to the sender of the message, not to the mailbox being managed!

Currently supported commands

As of version 0.3b1, quickSMTP supports the following commands. Remember that each command has to be terminated with semicolon ( ; )


Allows to change the password. Password change would be immediate, so if you are changing the password on your own account as soon as this request is processed you need to update your email client with the new password in order to be able to connect to POP3 and SMTP.


User ; Pass mypassword ; NewPass mynewpassword ;

quickSMTP news review

Latest Version: 0.3

Important bugfix! There was a bug in version 0.2 that would cause quickSMTP to consume a lot of resources when a client connects to SSL POP3 or SMTP and does not comply with the protocol commands. We recommend you to upgrade

Latest Version: 0.2

Version 0.2 optimizes existing functionality, fixes some bugs and introduces a few new features. Upgrade is highly recommended! 

Version: 0.1

This version is a major upgrade and is not compatible with the previous versions. You need to manually uninstall any previous version before installation!

  • SQLite is being used as back-end storage which means that all .ini files are no longer needed.
  • SSL encrypted POP3 and SMTP protocols are available.
  • New intrusion prevention system that allows you to block nodes who are probing brute force users.
  • Monitoring interface and program that allow you to connect to and monitor your quickSMTP.
  • Statistics with various graphs that can give you a good overview of the operation of your mail server.
  • Quotas for mail storage introduced on per account level.
  • Retention period for local storage of emails.
  • Remote blocking rules have been extended to include expiration time should you need to impose time limited bans.

Click here to learn more and download