using smartermail and smarterstats with plesk

[manos2000]

As i know from previous experience, on both these tools it is better to stop their servers and attach the processes to IIS (it is more secure and uses much less cpu).
If this is done then plesk recognises these as components or not?

thanks

manos

 

[sergius]

You can use SmarterMail and SmarterTools with IIS.
Plesk recognises SmaterMail or SmarterTools as Windows services.
In order to Plesk can connect to it you should specify on page Plesk > Server > Components Management appropriate parameteres login, password and port.

 

[manos2000]

smartetools at 8.2

tried it, attached the process to IIS, it is working fine from web interface but plesk does not recognises it

env: plesk 8.2 / SmarterMail Server 4.3.2760

manos

 

[manos2000]

smartertools

Found this at swsoft kb:
Since version 7.6 Plesk allows selecting web server provider for SM web service: IIS or SM native Web Server

but where can i choose the web server provider? There is no option after installing plesk?

thanks

manos

 

[sergius]

Plesk tries to connect to SmarterMail or SmarterStats on localhost and specifed port.

 

[manos2000]

smartertools

yep but using localhost smartermail and smarterstats servers must have unassigned (all) ips.
i prefered to use unique ips for the servers in order users to not have put 9998 or 9999 ports as many firewalls block these ports

manos

 

[LeaUK]

In plesk 8.1 I had to ensure SM was running on both 80 (for normal access using IIS) and 9998 so Plesk could talk to SM.

I didn't find an option to change the port number as advised above but maybe 8.2 has this new facility?

Lea

 

[sergius]

Originally posted by LeaUK
In plesk 8.1 I had to ensure SM was running on both 80 (for normal access using IIS) and 9998 so Plesk could talk to SM.

I didn't find an option to change the port number as advised above but maybe 8.2 has this new facility?

Lea

Please click on Plesk > Server > Components Management > Mail Server > SmarterMail

 

[LeaUK]

Thanks sergius

You are quite right, there is a port option in 8.1.

But now I remember why I kept 9998 open, it's because I get this error if I choose port 80

"Error: Some fields are empty or contain an improper value."

????


Smarter mail is working fine on port 80, but Plesk cannot talk to it?

 

[manos2000]

smartertools

If u use port 80 then u have to use unique ips for smartermail and smarterstats or if u use shared ips with other sites u have to use different host headers.
In case u use unique ips at port 80 (best option in my opinion) plesk has not a field to declare this ip so can not communicate.It communicates only if u use all (unassigned) ips.
As sergius said they will fix it in next version.


manos

 

[LeaUK]

I run both SM and SS in IIS, both on the same IP and both on port 80, they have different host headers webmail.mydomain.com and stats.mydomain.com

But, Ples fails to talk to SM on port 80 even if configured to do so, the error message above is given by Plesk. However I leave SM running on 9998 and configure Plesk for this port.

The rest of the world can use port 80 to talk to SM

Works for me

Lea

 

[manos2000]

smartertools

i run also attached on IIS SM and SS, use ports 9998 and 9999 so plesk can communicate with these.
The problem is that user has to type www.mydomain.com:port in order ot use webiinterface.
The best would be to use a unique ip at port 80 for each service and add a default A record at server>DNS webmail.domain.com = ip

manos

 

[LeaUK]

Ah, I had to use some tricks to fool Plesk into adding host headers in the SM IIS site....here's how:

Once you've setup a SM IIS implementation you'll find that the host headers wont get updated by Plesk anymore. However the way around this is to cheat and point the Home Directory for the 'webmail(default)' site to the SM folder on C:\..... then delete the SmarterMail IIS web if you haven't already. Go back into the properties of default webmail IIS site and amend to suit SM, ie., ASP 2, and repoint to the application pool for SM you've previously configured.

Now Plesk is fooled into updating the host headers automatically and I have SM running on port 80 BTW - you still need the SM default 9998 server running as that's how Plesk configures SM.


Works a treat