Mdaemon VS Kerio Connect [message #125204] |
Fri, 23 October 2015 08:50  |
Jeff Lau
Messages: 1 Registered: October 2015 Location: Thailand
|
|

|
|
Sir,
Previously our company all mail account is in GoogleMail. Due to security we now wish to setup mailserver at each site. I had been tested Mdaemon and the below is his interesting point;
1. Header Translation - Where I create a local domain called horizon.net when I smtp out it will carry horizonnetltd.com
2. Mailbox Restriction - I able restricted mailbox to receive mail from which domain only or mailbox user able send to what domain only
3. Multipop where allow me to collecting mail from google mailserver
This is what my R&D result for Mdaemon, For Kerio Connect do they able to do that or had similar feature. Cause as management mention once implemented very hard to change cause resources and downtime issue.
Can anyone answer and guide me on this R&D
|
|
|
Re: Mdaemon VS Kerio Connect [message #125228 is a reply to message #125204] |
Fri, 23 October 2015 18:45   |
Bud Durland
Messages: 586 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
1) Kerio doesn't really have header translation, but you can probably emulate it in the clients. Create the domain 'Horizon.net', and add 'HorizonNetLTD.com' as an alias. The clients will log in to the mail server as 'JohnDoe@horizon.net', but the client can then be configured to sue 'JohnDoe<_at_>HorizonNetLTD.com' as the outgoing e-mail address. We do this with several client programs (OutLook, eMCLient, Thunderbird ) for our domain and it's aliases.
2) Using the admin interface, a user can be restricted to 'send/receive mail from the local domain only'. If you need to limit which external domain a user can send mail to or receive mail from, you would have to define a server-side rule throw messages away.
3) Kerio has done this for quite some time -- see the 'Delivery' group in the admin interface.
|
|
|
|