Knowledgebase : eMail > SmarterMail

When you send an email through SmarterMail, you receive following error in bounc back email.

Remote host said: 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

Soltution:

  • Login as admin
  • Settings/General Settings/Server Info
  • Set the hostname to 'mailserver.mydomain.xxx'
  • Point an A record of 'server1' to the ip of your server
  • Create a Reverse DNS PTR record for the server ip to resolve back to mailserver.mydomain.xxx

Cannot create domain: mailmng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL) MEAOPO.PostOffice.AddPostOffice failed

 
APPLIES TO:
  • Parallels Plesk Panel for Windows

Symptoms

Domain cannot be created with following error reported in Parallels Plesk Panel interface:

Error: Unable to update domain data: Failed mail post-configuration: Can't create mail domain servie: mail_Facade->createDomain() failed: mailmng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL) MEAOPO.PostOffice.AddPostOffice failed for name domain.tld [domain.tld]

Cause

It may be caused by previously failed attempt to add or remove domain with the same name, which resulted in domain being absent from Parallels Plesk Panel, but MailEnable postoffice exists due to unsuccessful rollback of domain creation/removal.

Resolution

Postoffice should be removed from MailEnable manually.

  1. Open MailEnable control panel using Start → All Programs → Mail Enable → MailEnable Administrator or Start → Run... →mailenable.msc on the server.

  2. Go to Messaging manager → Post Offices and remove/rename postoffice of domain that causes error.

Error: Set default component failed: defpackagemng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL)
Unable to assign port to IP address. Reason: Unknown IP Address: 169.254.16.152


Follow the below given steps to solve this issue :

  1. Go to Regedit.
  2. Go to the path: Local_Machhine >> Software >> Wow6432Node >> Plesk >> Psa config >> config 
  3. Locate the record MAIL_PROVIDERW_DLL and change it to: C:\Program Files (x86)\Parallels\Plesk\admin\bin\smartermailprovider.dll
  4. Locate the path: Local_Machhine >> Software >> Wow6432Node >> Plesk >> Psa config >> config >> Packages >> Mailserver and set Default regisrty entry to smartermail
  5. Save the registry. 
  6. Open Plesk using admin login, go to  Tool and setting >> Server components >> and click on refresh.

The iPhone supports IMAP. IMAP will allow you to retrieve emails and folders from SmarterMail and leave the emails on the server. 

Follow these steps to create a SmarterMail IMAP connection to an iPhone or iPhone 3G with Firmware 2.0.x:

  1. On the iPhone, tap Settings.
  2. Tap Mail, Contacts, Calendars.
  3. Tap Add Account.
  4. Tap Other.
  5. Tap Add Mail Account.
  6. Complete the Name, Address (email address), Password and Description fields.
  7. Click Next.
  8. Ensure IMAP is selected.
  9. Enter your incoming mail server information:
    • Hostname is generally mail.yourdomainname.com. If you aren't sure, contact your email hosting company
    • Username is your full email address
    • Password is the same password used to access webmail.
  10. Enter your outgoing mail server information:
    • Hostname is generally mail.yourdomainname.com. If you aren't sure, contact your email hosting company
    • Username is your full email address
    • Password is the same password used to access webmail.
  11. Tap Next.
  12. The iPhone will attempt to establish an SSL connection to your IMAP and SMTP servers. If this succeeds, you will be done and can proceed to step 13. If this fails, you will see the prompt, "Do you want to try setting up the account without SSL?"
    • Tap No.
    • Tap Save.
    • When prompted, "This account may not be able to send or receive emails. Are you sure you want to save," tap Save.
  13. Tap the account you just added (identified by your email address)
  14. Scroll down and tap the SMTP button.
  15. Select the server you just added, identified by the hostname from step 9.
  16. Select OFF for Use SSL.
  17. Select Password for Authentication
  18. Select 25 for Server Port.
  19. Tap the SMTP button to go back.
  20. Tap your email address to go back.
  21. Tap Advanced.
  22. Scroll down to Incoming Settings.
  23. Select OFF for Use SSL.
  24. Select Password for Authentication.
  25. Select 143 for Server Port.
  26. Tap your email address to go back.
  27. Tap Mail to go back.
  28. Tap the Home button.
  29. Tap the Mail App to check your configuration.

Overview:

When you browse webmail.yourdomain.xxx you receive the following error:

No connection could be made because the target machine actively refused it 127.0.0.1:17001
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:17001

Solution:

  1. Make Sure that SmarterMail Mail Service is not stopped.
  2. Recycle Application Pool in IIS.
The best way to access webmail is to go to the webmail URL. It is just the domain name with "webmail" appended to the start.
    http://webmail.yourdomain.xxx

This article presents an easy method of transferring email from one server to another, using matching IMAP email accounts in your favorite local email software. This is important because when you migrate to a new server, your old emails will not be available unless you migrate them.

You will transfer emails from a single mail account on one server to another. Using IMAP avoids formatting and permissions problems that may result from moving the raw mail files.

Requirements

  • Both of your servers must support IMAP email. 
  • The password for the email account you are trying to migrate.
  • An IMAP-capable local email client. Most email clients like Outlook, Apple Mail, and Thunderbird support IMAP mail accounts.
    • If you don't have a favorite email client, download Thunderbird for free.

Instructions

  1. Create the same email account on your new server that you had on your old server. Use the same spelling and capitalization.
  2. Give the new email account the same password that you used on your old server. You can change the password after the migration process is done, if desired.
  3. In your local email client, create two new email accounts.
    1. They will both be for the same email address.
    2. They will both use the same password.
    3. They must both use IMAP.
    4. The incoming server (or IMAP server) will be different for each account.
  4. With both accounts online, open up the inbox for the account that connects to your old server. Drag and drop messages from this inbox to the inbox on your new server.

We recommend the following settings for SmarterMail 4.x and higher.  

  1. Login as the System Admin
  2. Go to Security
  3. Go to Anti-Spam Administration and click the Spam Checks tab 

 We also recommend that when assigning weights to the various SPAM Checks that you use increments of 10.

Declude (Leave unchecked if you not have Declude)
Low Probability of Spam weight = 10
Medium Probability of Spam weight = 20
High Probability of Spam weight = 30

SPAMAssassin
This is a single Thread Windows client that can handle approximately 20,000 emails per day.  If your server processes more than this you may want to use SPAMAssassin in a stand-alone Linux configuration.

Bayesian Filter

Weight = 10 (SPAM weight assigned to an email if it fails Bayesian filter test)
Max. Memory to allocate for filtering = 10MB
Message required for filter update  = 500

SPF       
Pass     weight = 0     Senders IP is valid for senders domain
Fail     weight = 30     Senders IP is not valid for senders domain
Soft Fail     weight = 10     Senders IP is questionable for senders domain
Neutral     weight = 0     No strong statement can be made for or against senders IP
PermError     weight = 0     The SPF record could not be processed.
None     weight = 0     SPF is not commonly adopted therefore, we suggest setting this to 0

Reverse DNS
weight = 10

RBL: SpamCop
weight = 10

RBL: SpamHaus SBL
weight = 10

RBL: SpamHaus XBL
weight = 10

Additional RBL’s can be added and weights applied.

To enable a SPAM Check, click the check box associated with the various SPAM filtering option you want applied to your incoming emails.

You can also enable “Blocking” of emails that fail individual SPAM checks.  As an example, enable Blocking for Reverse DNS, if an incoming email message fails only the Reverse DNS test then, the message is assigned a weight of 10, if the SMTP Blocking Weight Threshold is set to 10 then the message is Blocked.

In order to adjust the weights of the various SPAM checks, click on the Edit link on the right of each SPAM Test item.  You can edit the values and then click Save to implement the changes or clicking Cancel to close the Edit dialog without saving changes.

On the Filtering tab the default settings are shown below:

Low Probability of Spam weight = 10
Default Action:     Prefix subject with text
Text to Add:     SPAM-LOW

Medium Probability of Spam weight = 20
Default Action:     Move to Junk E-Mail folder
Text to Add:     SPAM-Medium

High Probability of Spam weight = 30
Default Action:     Move to Junk E-Mail folder
Text to Add:     SPAM-High

Once, you are comfortable with your SPAM settings you may want to change the default action on the High Probability from “Prefix subject with text” to “Delete the Message”.

Enable Greylisting
This feature bounces unrecognized incoming emails that are not included in either the Trusted Sender list or the White Lists. 

If the incoming message is received by an unknown sender the server will bounced the initial message, when a valid email server retries sending the message after the Block period (default 12 minutes) and within the Pass period (default = 240 minutes) then the email is accepted.  This creates a Record expiration for that email which is by default = 36 days.  If another email is received from this same sender then this resets the Record expiration to 36 days.    

If the messages is received by someone in the Trusted Sender list or the White Lists then the message bypasses Greylisting feature and is then processed by only Anti-Virus Administration settings and then delivered.

Block Incoming and Outgoing SMTP connections 
The idea behind SMTP Blocking of Incoming and Outgoing email is to filter out Spam messages before they are delivered to the Spool.

To enable Incoming and Outgoing SMTP Blocking, log in as the System Administrator, go to Security, Anti-Spam Administration, and Spam Check page.

Enabling Incoming SMTP Blocking can apply Spam filter checks such as SPF, Reverse DNS and RealTime Blacklist.

To configure Blocking of Incoming SMTP connections, select the Spam checks you want applied to Incoming email from the Spam Check page. Once, your selections are made, click the SMTP Blocking tab.  The Spam filtering checks that were selected on the Spam Checks page will be displayed under the Current Incoming Weights.  In order to actually enable the Blocking feature, click the Spam Blocking Enabled Check Box.  Next, you can edit the Weight Threshold under Incoming Options, so that when an email arrives and it exceeds the Weight Threshold value the email is blocked and never delivered to the Spool.

For the SMTP Blocking of Outgoing email, Spam filter checks are applied to outgoing email prior to being put in the Spool.  There are additional Spam checks that can be selected such as: Declude, SpamAssassin, Custom Headers, and the Bayesian Filters in addition to those available for blocking of Incoming SMTP connections.

To configure the blocking of Outgoing SMTP connections, select the Spam checks you want applied to outgoing email from the Spam Checks page. Once, your selections are made, click the SMTP Blocking tab.  The Spam filtering checks that were selected on the Spam Checks page will then be displayed under the Current Outgoing Weights.  In order to actually enable the Blocking feature, click the Spam Blocking Enabled Check Box.  Next, you can edit the Weight Threshold under the Outgoing Options, such that when an outgoing email exceeds the Weight Threshold value the email is blocked and never delivered to the Spool.

Then finally, click the Save.

This article was orginally published at http://tinyurl.com/7j59969

This article goes over setting up TLS for SmarterMail.  The server must have a SmarterMail Enterprise License in order to use this feature.  This article applies only to Cloud and Dedicated Servers.

  1. Log into the server via Remote Desktop.  If you are unsure of how to do this, please see Connecting to a Server via Remote Desktop.
  2. Open Internet Information Services (IIS).  Find the SSL that will be used to set up TLS and export it to a PFX file.
  3. Next, log into SmarterMail as the server administrator.  This is typically http://127.0.0.1:9998 orhttp://mail.yourdomain.com depending on the server configuration.
  4. Within SmarterMail admin, navigate to Security SSL and choose Add SSL.  Enter in the following information:
    • IP Address: IP of the site in IIS under the SmarterMail site
    • SMTP: 25
    • POP: 110
    • IMAP 143
    • Type: TLS
    • Certificate Path: the path to the PFX file generated
  5. Now you can test the setup of TLS.  Open a command prompt and type the following: 
  6. telnet mail.yourdomain.com 25 (where yourdomain.com is a domain on the server)
  7. The test will reply with the server name and look similar to the following:
  8. Trying <xx.xx.xx.xx> 
    Connected to mail.yourdomain.com
     
    220 mail.yourdomain.com
     
  9. At the prompt, type ehlo and a response similar to the following will show:
  10. 250-mail.yourdomain.com Hello [xx.xx.xx.xx]
    250-SIZE 104857600
     
    250-AUTH LOGIN CRAM-MD5
     
    250-STARTTLS
     
    250 OK
  11. If you see the line about STARTTLS, TLS is setup correctly for the domain.

When you create a new domain or update an existing one in Plesk you receive the following error:

"Unable to call SOAP server: (-2147467259) Unspecified error"

This error will occur if you have SmarterMail installed on your server and its not properly configured, or (smwebmail) site is stopped in IIS.

SOLUTION:

  1. Check to make sure that Plesk is configured properly to connect with SmarterMail
  2. "smwebmail" site in IIS is not stopped
  3. Be sure you have bind 9998 port with all assigned IPs in the webmail site if using IIS.
Any change to mail server configuration using Plesk control panel results in the following error message:

SOAP failed. Failed in sending message at (SmarterMail::checkResult line 175) 

Cause

SmarterMail Web Server is stopped.

Resolution

Restart SmarterMail Web Server.