|
 |
sharpResponse - Documentation - Configure gateway for sending emails SMTP |
|
 |
This article describes how to configure SMTP protocol to allow sharpResponse to send emails. We also discuss the problems you could face with firewalls and anti-virus software, that can prevent the application from sending the emails intact.
|
 |
Description |
|
Configure SMTP
The sharpResponse takes in one single SMTP configuration and uses it to send all emails from all mailboxes. To configure the SMTP protocol, click SMTP Configuration button from the toolbar. Specify the gateway server name. This is the server that will initially act as a email delivery agent. It is worth noting that in most cases this would be restricted to your broadband or cable provider. If using commercial LAN, you need to find out the allowed gateways from your network administrator. The restriction to use mail delivery gateway is normally imposed by internet providers to stop spammers. However, this does not apply to all internet providers, some choose to give you a complete freedom. For example, if your provider is BT Internet (or whatever they are called now) the mail gateways is mail.btinternet.com or Tiscally mail.tiscally.com.

Discussion – Credentials
Sometimes the gateway provider requires you to authenticate your connection for sending emails. This requires you to enter user name and password.
The use of credentials are not very common, especially if your internet provider imposed their own SMTP gateway. However, if you use
third party one then it is most likely you will need to use authentication.Commercial networks force you to use Windows Authentication
to connect to SMTP providers. If so, your Windows login name and password will be used to connect to the SMTP protocol.
Discussion – Firewalls and anti-viruses
You computer is most likely protected by firewall and anti-virus. Since sharpResponse
will be unknown application for firewalls and anti-viruses the internet connection will be blocked by your firewall. If you are having trouble getting connected to the SMTP server or generally getting sharpResponse connect to the internet, check your firewall settings.
Generic Windows Firewall will normally prompt you that the application is attempting to access Internet.
For a good measure it is a good idea to restrict sharpResponse to specific ports on the network. We use common ports
- 25 – SMTP
- 110 – POP3
- 143 – IMAP
- 80 – HTTP fallback
- 443 – HTTPS for IPN connections
We also use 256Bit encryption additional encryption to communicate with Instant Payment Notifications services. Some clever firewalls will be able to detect the encryption and warn you about it.
The software uses standard protocols for communication, therefore you can track packets with Net utilities, to ensure the authenticity of the connections.
None of the ports or connections are kept alive or for listening, so there is no thread from outside penetrations.
With regards to anti-viruses, some clever anti-viruses scan whatever flows on email ports (25,110 or 143), therefore the email downloading or most commonly email sending will be blocked by your anti-virus software. Not blocked as such, but held until application is closed. For example, we have found that Norton Antivirus will capture outgoing emails and hold them until sharpResponse is completely closed, only then emails are sent. The reason for such behaviour is to ensure the port closure and avoid threading the application resources, this is quite normal however prevents sharpResponse from sending response emails properly.
You can keep the anti-virus software holding emails. When you turn your computer off the emails will be sent prior to disconnecting from the Internet. However, sudden connection termination may cause loose of sent emails, even though the sharpResponse reports that the email has been sent successfully.
Alternatively, you can configure your anti-virus software to allow sharpResponse’s SMTP and POP3 communication.
<< Back | Next >>
|