madExcept Settings (Tab 5)

You can click on the tabs in the left side of the image:

You can click on the 3 tabs "upload to web server", "send via SMTP" and "use local mail client" to get more detailed help.

send settings...

First of all you need to decide which method your program should use to send bug reports to you. There are 3 basic options. The most reliable option is upload to web server. This is so reliable because the data is transferred via HTTP and most firewalls let that pass just fine. However, this method requires you to setup a web server. The second best option is send via SMTP. This method is easy to setup, but some firewalls might block it. The easiest method to setup is "use local mail client". This way madExcept will try to use the mail client software which is installed on the end user's PC to send the bug report to you. Unfortunately doing so is not very reliable because many end users don't have a mail client software installed at all. You can also activate multiple send methods. This way if one method fails, madExcept will try another one.

You can let madExcept send the bug report in a background thread or in the current user interface thread. If you decide to use the background variant, the progress window is shown in the bottom right of the screen, so that the end user can continue working right away. Otherwise the progress bar is shown in the middle of the screen in modal state. Background sending is not possible (automatically turned off) during dll initialization & finalization.

send via SMTP...

You can enter one or multiple mail receiver(s), seperated by a comma.

SMTP mailing is available in either "client" or "server" variations. The act as SMTP client variant behaves just like any mail client does. You have to enter which email server you want to contact to and the type of encryption (none, SSL or TLS). Additionally, depending on your mail server, you probably also have to enter your account and password data. Please note that your password will be stored in your exe file, and although madExcept encrypts it, it is not 100% crack safe. So you should not use your main SMTP account. Instead I'd suggest to setup a dedicated SMTP account just for bug reporting. Alternatively you can of course also ask the end user for his SMTP server and account information and feed that into madExcept at runtime.

The act as SMTP server approach behaves just like an internet SMTP server does. Usually that works without authentication. However, some mail servers don't accept mails from dialup connections. So the SMTP server variant won't always work for all users. In fact, due to the global spam problem, more and more servers decline mails from dialog connections. So if you want to use this solution please make sure that your server is setup to accept emails from dialog connections.