Ipswitch Forums / IMail Server / Ipswitch Products / 2006.21 Bad socket state in web messaging / Latest Posts

RE: 2006.21 Bad socket state in web messaging

tripodal — Tue, 22 Apr 2008 16:19:01 GMT

Please try resetting the webserver on your imail box,

iisreset, in the command prompt.

Thats how I have fixed it the two times it has happened for me in 4 years.

RE: 2006.21 Bad socket state in web messaging

Peter Teipe — Fri, 18 Apr 2008 17:02:01 GMT

I have had an ongoing issue with SMTP crashing for months as well as the previously mentioned "[b]bad socket state[/b]" message appearing in webmail for a pretty long time now. I have worked extensively with Ipswitch Technical support on the issue, but it has not been resolved. We are running what I think is the most recent version - Imail 9.23.

RE: 2006.21 Bad socket state in web messaging

tanswf72 — Wed, 02 Apr 2008 13:02:24 GMT

No. It's still not working.

Bad socket state prompted again.

RE: 2006.21 Bad socket state in web messaging

Holger L — Thu, 26 Jul 2007 04:40:30 GMT

[quote][b]John T (7/26/2007)[/b][hr]
Actually, there are KB articles explaining the proper way to change a host or virtual host of Imail. That is what should have been followed, instead of casually changing domain information.[/quote]
Right. I totally agree. - But when a thing is so important not to change then it might be a good idea to make it a little harder to do so. A simple warning when changing these important values on the primary domain could have been sufficient.

RE: 2006.21 Bad socket state in web messaging

John T — Thu, 26 Jul 2007 04:12:52 GMT

[quote][b]Holger L (7/26/2007)[/b][hr]
In the documentation there should maybe be more emphasis on the importance of keeping the original settings. There were no warnings when I did the changes I did, and the only problem (as far as I could tell) after I did the changes was with sending emails from the web interface.[/quote]

Actually, there are KB articles explaining the proper way to change a host or virtual host of Imail. That is what should have been followed, instead of casually changing domain information.

RE: 2006.21 Bad socket state in web messaging

Holger L — Thu, 26 Jul 2007 02:31:21 GMT

Allright. A reply from Ipswitch support gave the answer.

During my trials I had set the IP of the primary domain to a virtual IP. I changed this to the main IP for the mailserver, changed the OHN in system settings to the same name as the primary domain and restarted the services.
Voila! I can send mail with the web interface again.

In the documentation there should maybe be more emphasis on the importance of keeping the original settings. There were no warnings when I did the changes I did, and the only problem (as far as I could tell) after I did the changes was with sending emails from the web interface.

RE: 2006.21 Bad socket state in web messaging

Holger L — Wed, 25 Jul 2007 02:22:14 GMT

I cannot NOT get the error... :-P I have tried logging onto a number of users and a number of hosts, and even from a number of ISPs. I get the error no matter what I try.

RE: 2006.21 Bad socket state in web messaging

Andy Schmidt — Tue, 24 Jul 2007 18:30:41 GMT

Holger,

if you use the same Webmail URL that the user uses and use their exact logon information (to be certain you are logging into the same domain and account) can you REPRODUCE the user's problem?

Is the problem consistent for that user? Or does it happen only occasionally for that user?

RE: 2006.21 Bad socket state in web messaging

Holger L — Tue, 24 Jul 2007 09:37:32 GMT

It was set up first using one primary domain for test-purposes.

I then added about 35 hosts from an older imail-server and added the users. The user database is an SQL server. All hosts are virtual.

I then added the IP of the old imail-server, and changed the default domain, and I thought the migration had went flawlessly - until I started receiving error-reports about this Bad socket state when sending email using the web-interface.

I immediately searched the KB for answers and found the before mentioned article.
I modified the web.config file according to instructions, and checked that the smtp-service should listen on all IP's. I also checked the domains in registry, and everything looked ok.

Everything works fine using an email-client.

I have tried a lot of stuff - literally spending the whole day trying to fix this, but still nothing.

RE: 2006.21 Bad socket state in web messaging

Tom Lewis — Tue, 24 Jul 2007 09:19:30 GMT

Can I get some more information on your configuration?

Are you using a Virtual Domain? What user database are you using?

RE: 2006.21 Bad socket state in web messaging

Holger L — Tue, 24 Jul 2007 08:13:42 GMT

I already did that, as it was mentioned in the kb-article as well. Still no luck.

RE: 2006.21 Bad socket state in web messaging

Tripp Allen — Tue, 24 Jul 2007 07:51:05 GMT

In the web admin, services, smtp - check the box at the bottom for "Enable SMTP to listen on all IP". Save, then restart smtpd.

2006.21 Bad socket state in web messaging

Holger L — Tue, 24 Jul 2007 07:27:25 GMT

We originally set up a 2006.1-server for testing a while ago before migrating, and we upgraded to 2006.21 when it was released.

I have recently set the server in production and have gotten reports from users who are getting the error "An error occured while attempting to send the message: Bad socket state" when they try to send emails.

All works well using an email client.

I have read this article in the knowledge base http://support.ipswitch.com/kb/IM-20051229-DM01.htm, and have done all what was suggested in the article, but have had no luck in resolving the issue.

This is a serious problem because many of our users are relying on the web interface. I had tested all aspects prior to the migration, but have probably forgot to test sending messages via the web interface. Downgrading is not an option.

Please assist.