FAQ & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: SmartPOP2Exchange | Show all categories

A connection abort was caused by the server or some software in between (e.g. firewall, proxy). Turn off any proxy (check if your antivirus software installed a proxy) and firewall for testing.

This error results of invalid DNS settings. To solve it add the local server's IP to our hosts file (C:\Windows\System32\drivers\etc\hosts):
 192.168.1.5 server
 192.168.1.5 server.domain.local
Then restart "Microsoft Frontend Transport" and "Microsoft Exchange Transport" services.

This error may occur if you only have 1 domain controller and put a router as secondary DNS server on all configurations.
Simply remove the secondary DNS which does not point to the internal DNS/Domain Controller.
Forwarding typically would be handled by the DNS servers in your environment, so a secondary public DNS would not be configured in a typical production environment.

If this does not correct the error, try to create a reverse lookup zone on the DNS server.

Please ensure that the Exchange SMTP receive connector allows anonymous sending of emails, this is important for incoming emails. And please turn off SMTP authentication in the SmartPop2Exchange SMTP configuration if the problem persists and it is turned on.

Your Exchange/SMTP server is not configured to receive mail for yourdomain.com. From your Windows Start Menu, select Start | Programs | Microsoft Exchange | System Manager. There select: Recipients | Recipient Policies | Properties. Click on the "email Addresses" tab, under Generation rules, select SMTP, and then click Edit and change the value to "@yourdomain.com". Please also make sure that the email addresses of all users are specified in their Active Directory entries on the "email Addresses" tab.

"unable to relay..." means your SMTP server does not allow SmartPOP2Exchange to send mail to it (as a SMTP relay server). Please first check the entered mail addresses in the "SMTP settings" of SmartPOP2Exchange. Make sure that these addresses also exist on your SMTP server. If you like your SMTP Server to send/forward that mail to an external server then set your SMTP server to allow all SMTP relays or at least relaying from SmartPOP2Exchange. (For MS Exchange Server you will find this setting in the properties of the "virtual SMTP server")

This notification is typical for Exchange Server 2007/2010 because they both have a standard option limiting email sizes to 10MB. These can be modified by changing the limitations of the Receive Connector. This occurs over the Powershell: Help article at Microsoft  (Set-ReceiveConnector  --->  MaxMessageSize)

Enter the following lines in the command line to simulate sending an email via SMTP to the Exchange Server:

telnet [Your Exchange server's IP] 25
HELO
MAIL FROM: smartpop2exchange@jam-software.com
RCPT TO: [your email address]
DATA
Test
.
QUIT

This error message means that  SmartPOP2Exchange tries to send out a message through the Exchange Server but the Exchange Server doesn't allow this.
To enable this please try the following:
The relaying permission for Exchange Server 2007/2010 and 2013 needs to be set using exchange powershell:
 Get-ReceiveConnector "<you receiveconnector id/name>" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
[See Help article at Microsoft]
Restricting the receive connector to localhost only is not possible; you need to accept at least the local network too: 127.0.0.0/8 (loopback) and 192.168.0.0/16

To solve this problem you have to do a workaround using a rule. Create a global rule using the condition "Messages with a size bigger than [enter size limit here]". As action choose "Save attachments to [enter a save path here]" and check the "Add path of save attachments to message body" option. Also add the action "Forward without attachments". 

All entries (Page 5 / 13)