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

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.

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.

To correct this, you must enter your own domain in your Tobit David configuration under "Allowed domain names".

Yes, it is very easy, because the POP3 protocol is quite simple. The following commands executed at the command line perform a login to the POP3 server and retrieve the statistics of the POP3 account:

telnet pop-mail.t-online.de
110
USER [YourUsername]
PASS [YourPasswort]
STAT
QUIT

In order to protect our customers, we have decided not to support this feature because it can cause problems and data loss. For this purpose IMAP exists and IMAP is also supported by SmartPOP2Exchange just as it supported by the MS Exchange Server.

You can achieve this by restarting the service with the Service toolbar (at the top of the SmartPOP2Exchange window).

We do not support this setup, because a POP3 is not designed to hold large amounts of mail messages and can get extremely slow. However, you can use the rules engine of SmartPOP2Exchange to send a copy of every incoming message to any email address you want; so you can create a "backup" Exchange account and store your messages there. For leaving mail messages on server the IMAP protocol should be used. IMAP is also supported by SmartPOP2Exchange.

Please be sure that your AV software is configured correctly. (see Antivirus overview)

All entries (Page 6 / 13)