Dotnetpanel Forums

The smartermail integration seems to be working very well for us, however the only thing missing is having the users domain (ie mail.domain.com) added to the smartermail website in IIS. Maybe its there and I'm just missing it?

Also, are there any plans for SmarterStats as well as third party FTP software?

Thanks,
Matt

Hi Matt,

When you create a new mail account, say, mailbox@domain.com the "domain.com" mail domain is added to SmarterMail domains automatically. "Mail.domain.com" domain is the result of DNS A record with the name "mail" which is also added to the appropriate DNS zone.

Let me know if I correctly understood your question.

Yes, we'll add SmarterStats support in the retail release. Serv-U and Gene6 FTP providers will be added too. All major service providers will be added till the end of this year.

I'm not too sure if were on the same page so let me see if can explain a little better. When a new mail domain is created, the domain is created in smartermail & the dns record mail.domain.com is created. I would like the mail.domain.com to be added to the smartermail IIS site. This is how I've always done it when I configured everything manually, see the pic for clarifcation.

http://www.mkilgour.com/iis.gif

Also, great news about 3rd party ftp software support, I despise MS FTP :D

What I have done for Mail Enable in the same scenario is to not use any host headers in the IIS configuration for webmail. Then any request that does not match a host header will go to that site.

 

 

paarlberg wrote:

What I have done for Mail Enable in the same scenario is to not use any host headers in the IIS configuration for webmail. Then any request that does not match a host header will go to that site.

Yes, we do the same thing here at DotNetPark.

But anyway this functionality will be added in the retail release. We call it "Web Interfaces" and it might be suitable for setting up web mail interfaces, mysql, mssql, statistics, etc. interfaces if you do not want to use additional IP address.

Good suggestion, thanks!

paarlberg wrote:

What I have done for Mail Enable in the same scenario is to not use any host headers in the IIS configuration for webmail. Then any request that does not match a host header will go to that site.

Thanks, hadn't thought about doing that :D

paarlberg wrote:

What I have done for Mail Enable in the same scenario is to not use any host headers in the IIS configuration for webmail. Then any request that does not match a host header will go to that site.

Well that worked perfectly, thanks for the tip guys!

This isn't really a solution, though. What if I want stats.domain.com AND mail.domain.com to work for each customer's domains? I realize this is a very old post so maybe by now (using v2.8.12) we can accomplish this?

 

Thanks.