Ipswitch Forums / Messaging / IMail Server / IMail 2006.22 requires @domain.tld at webmail login / Latest Posts

RE: IMail 2006.22 requires @domain.tld at webmail login

Roeller — Tue, 30 Oct 2007 18:24:33 GMT

Thanks Robbie, you're great!
That worked like a charm!

Note that many customers will experience this issue, in my case it was a customer who had it's mail running at: https://www.mydomain.com. Offcourse www.mydomain.com was not a mail alias.

RE: IMail 2006.22 requires @domain.tld at webmail login

Robbie Boucher — Tue, 30 Oct 2007 13:45:22 GMT

Hey,

The domain alias that you add needs to be whatever your users are navigating too in their browsers. For example:

Official Domain Name: mail.domain.com

URL: http://webmail.domain.com/IClient

Domain alias needed: webmail.domain.com

RE: IMail 2006.22 requires @domain.tld at webmail login

Roeller — Tue, 30 Oct 2007 12:59:00 GMT

Sir,

I'm using Trial/Evaluation software for testing purposes. I do IMail/ICS projects (implementations/migrations, etc.) in The Netherlands for large organisations and ISP's.

Can you please explain which right/permissions or open a ticket for me ?

..I heard it was something with Registry or NTFS permissions.. ?

RE: IMail 2006.22 requires @domain.tld at webmail login

Tom Lewis — Tue, 30 Oct 2007 10:19:39 GMT

Hi Roel,

I think the best thing you could do is give Tech Support a call. They will be able to find a solution to this much quicker than trying to diagnose it on the forum. We have had a few customers with this problem and it has turned out to be permission problems due to system issues. Tech Support will be able to quickly rule out these known problems.

Thanks.

IMail 2006.22 requires @domain.tld at webmail login

Roeller — Mon, 29 Oct 2007 20:29:49 GMT

Although i've read this was fixed in the 2006.22 release.

For me, this error came after upgrading from 2006.21 to 2006.22.
Users (of the main domain) who login into Webmail without the @domain.tld get the error:

Unable to log into the system.
Reason:

There is no text give for the reason.

I've done the regcheck.exe and it didn't gave any errors.
I also tried setting a domain alias for the main domain (which i gave the same domainname as the Master domainname).
I was running a cutomized Login.aspx and web.config before (nothing really special), which were also overwritten by the upgrade.

Is there any specific file (login.aspx or another 'code-behind-file'?) i can check (date/size) to verify the bug is included in my code or not ?