FAQs & 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

"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". 

Please make sure, that the SSL certificate of your server is (still) valid. As a system service, SmartPOP2Exchange is bound to assume, that your certificates are valid - so if the POP3 server delivers an invalid certificate, SmartPOP2Exchange cannot proceed without a valid certificate.

This problem does not come from SmartPOP2Exchange. It is a common problem of the 2003 Exchange Server:
If SmartPOP2Exchange changes the email header, i.e., the active Spam-Filter adds the SpamAssassin header field, then SmartPOP2Exchange will recode the header. Therefore, UTF-8 will be used when no code per content-type is indicated.
As long as SmartPOP2Exchange does not change the mail header, then the problem will not occur. That the actual problem comes from the 2003 Exchange Server.

Normally 3 mail messages are generated by the originating mail server and should finally reach the POP3/IMAP catch-all account.
But we have seen a few cases in which the receiving mail server deleted subsequent mail messages and kept only the first message in the catch-all account.
This behavior is incorrect for catch-all accounts, as these mail messages have different entries in the Envelope-To: header line.
Since version 6.1 of SmartPOP2Exchange there is an option for catch-all accounts on servers with such an incorrect behavior. This option replicates mail messages for each recipient of the TO and CC header field.
Of course this problem can also be solved by creating individual POP3/IMAP accounts for the active email addresses.

Yes, using catch-all account may cause messages to get lost!
This is not a problem of SmartPOP2Exchange its a problem of catch-all accounts in general.
Example:
 A customer sends a mail with his own address in the TO field (TO: self@customer.com) und with two users of your company in the BCC field (BCC: a@company.com; b@company.com).
The message it self does not contain the address a@company.com or b@company.com because of using the BCC field. This recipient information is only provided through the SMTP protocol on sending. After this mail arrives at POP3 mailbox those recipient information regarding to the company is lost. When then SmartPOP2Exchange retrieves that message from the POP3 account it is not possible to determine to how many recipients or to which user it was send. So such a message can only be forwarded to a  fallback-adress.

Yes, it is. Set the option "Send messages to the mail address found in their message header" on the POP3  / IMAP  account setup form to automatically forward the mail to the appropriate accounts. The email address specified as target in the SMTP server configuration will only be used as a fallback address in the rare case that the email address could not be extracted automatically.

All entries (Page 5 / 12)