Hey John, 

By default, the hostname is used on the SMTP banner. This needs to match what is on your RDNS otherwise you can end up with delivery issues and your IP can be blacklisted. 

I recommend setting this to whatever matches the RDNS on your server. 

Please let me know if this helps.

Kind Regards, 

Yes, I was talking about the "Hostname" in the "General Settings....Server Info tab".

I can access smartermail's login page from a browser on the server using this address:

127.0.0.1:9998

I can't find a "hostname" setting in plesk, so it seems that plesk article is also talking about the "hostname" setting in smartermail. So why is it suggesting to change it to "127.0.0.1"?

Hey John, 

The Plesk addon isn't provided by us at SmarterTools. But if you contact them I'm sure they can help you. 

Something to note is it looks like the version of SmarterMail that you're running isn't supported to work with their SmarterMail addon. 

It says that it requires SmarterMail 15 and up and according to this post you're running version 14.7. 

I recommend that you give us a call at +1 877-357-6278 then we can discuss your upgrading options. 

Looking forward to hearing from you. 

Kind Regards, 

I'm not using a "remote" smartermail installation - I'm installing my v14.7 smartermail on my local server where plesk is also installed.

So, does that mean that the article you mentioned is not applicable with my setup?

Hey John, 

Thanks for the follow-up. Remote refers to outside of Plesk. Plesk uses Mail Enable by default. Using a SmarterMail server would be considered remote even if it's installed on the same server. Because Plesk communicates with SmarterMail over the API it makes sense that it requires using SmarterMail 15 minimum since we changed how our API works in that version. 14.7 uses the legacy API which it looks like Plesk does not support. 

Kind Regards, 

I highly recommend upgrading to SmarterMail 15 (15.7.6970). I still have it running for a couple of my customers, even though I have maintained my license with ST for later version(s). It's essentially bulletproof for email delivery. It -should- upgrade for you with few problems (I went from 13.x to 15 with no major issues a few years ago). But of course, make FULL backups, just in case.

Another way to do it, if you want: spin up 14.7 on a new server, restore the data, upgrade THAT to 15, then change over. Hopefully ST will give you a temporary license for that.

Are you 100% sure that "remote" even applies to smartermail being installed on the same "local" computer that plesk is installed on?

I ask because when I installed smartermail on the local server, plesk not only saw that it was installed and allowed me to configure plesk to use it instead of mailenable, but when I create a new domain in plesk, plesk is able to properly setup a new email account in smartermail directly from plesk.

Hey John, 

Thanks for the follow-up. Plesk likely checked the registry to see what was installed. It would still qualify as a remote installation since it's accessing Smartermail over the API and it isn't using the native email server. 

If it's working for you that's awesome. But since it doesn't meet their minimum specifications you could run into issues in the future. Anyways I wish you the best. 

Feel free to give us a call or email if you'd like to discuss upgrade options for your license. 

Kind Regards, 

 

I just went to the "Default Spam Filter Component" in Plesk and it listed these options:

 Merak Mail Server (not installed)

 SmarterMail Server 14.7.6347

 MailEnable Standard 10.42

 Remote SmarterMail Server (not allowed by license key)

None

So it appears that Plesk does NOT consider Smartermail running on the same local machine a "Remote" Smartermailk server because it specifically has a separate option for a "Remote" smartermail server.