IPAddressManager::OrderList raised an exception.

Raise/discuss any potential issues with MailEnable for consideration in project issue register.
Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 5:41 pm

A user said he could not send email, or emails he had sent had not arrived.
I sent local email to him and myself and that arrived.
I sent email externally and it did not arrive.
I have a few messages in my outbound queue, so that explains it.
But I looked in the smtp debug logs and I found a few messages like this:

12/18/12 09:12:54 IPAddressManager::OrderList raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 238
12/18/12 09:12:54 IPAddressManager::FillSendSocketAddress_V6 raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 424
12/18/12 09:12:54 IPAddressManager::ReleaseAddressList raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 163
12/18/12 09:12:54 SendSMTPMessage handled an exception; session will be dropped.
Command: AC6A29FBFEE2445C912A9D4AAEEB4AFF.MAI12/18/12 09:12:55 ME-I0074: [500] (Debug) End of conversation

Can anyone explain that? Is there something I need to do?
Thanks in advance.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 5:48 pm

Oh, by the way.
I updated to the latest mailenable version yesterday. When this started, I guess.

Also, this is running on an ancient windows 2000 server.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 6:10 pm

Also, I am smarthosting through my ISP's ACL controlled mailserver. There is nothing in the logs that I have seen that would indicate that is a problem.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 7:02 pm

I rolled the installation back to 6.54 standard and it seems to be working again.
Something about 6.74 that would not work on windows 2000?
Could be.

I can do more tests if needed.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 7:06 pm

By the way, I have another installation that I upgraded remotely yesterday, from the same version to 6.74 but it continued to work.
However it has the exact same Ipaddressmanager messages in the debug log.

It's also windows 2000 and has been running for ages in a closet.

On second examination, there is mail stuck in it's outbound queue same as the other one. So same problem and I am going to roll it back.
Version 6.74 is apparently broken in this instance.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Tue Dec 18, 2012 7:42 pm

I rolled back the other installation that failed on installation of 6.74 to 6.54 and it started working. The mail stuck in the outbound queue went through immediately.

On problem i did find with this rollback is the diagnose form, it was apparently not replaced with the previous version. It complains about exchange active sync licensing. Not exactly sure about that but I don't recall any errata on that before.

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Wed Dec 19, 2012 4:07 pm

Hello?
Is anyone there?
No response from the Mailenable peeps on this?

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Re: IPAddressManager::OrderList raised an exception.

Post by MailEnable » Thu Dec 27, 2012 9:53 pm

Hi, would it be possibLe to raise a support ticket under the defect catagory as at http://www.mailenable.com/support.
To diagnose further we would need the SMTP debug and activity logs at the time of the problem occuring.
These can be zipped and attached to the ticket or e-mailed to the ticket response. Thanks
Regards, Andrew

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Mon Jan 14, 2013 5:32 am

Andrew,

I will work on that, as I said I rolled back but I am sure the logs are there.
I did this upgrade on two windows 2000 servers and both had the exact same problem. Mail stuck in the outbound queue and when I rolled back it left immediately.

So a mailenable bug that affects that admittedly ancient environment is confirmed.

However since I have rolled back and it's now working I don't need and can't pay for a support token. I want you guys to know what problems arise if it's a bug but since I am using the free edition I don't have support, except these forums.
I can get those logs together.

So, Andrew, what do you want me to do?

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Fri Feb 01, 2013 11:02 pm

Andrew
No response to this message.
Is there something you want me to do?

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Re: IPAddressManager::OrderList raised an exception.

Post by MailEnable » Fri Feb 01, 2013 11:53 pm

Hi, Did you raise the support ticket? The issue can be raised as a defect (@ no charge). The information about the environment (diagnostic report) and SMTP Debug/Activity logs will help determine what is occuring. We have some test W2K servers in our lab. On Monday I will ask one of the engineers to attempt to reproduce.
Regards, Andrew

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Sat Feb 02, 2013 2:29 am

Andrew, as you requested I tried to put through a support ticket. But class c is grayed out on your form, so it wants money.

When i went back the form was blank.
I would have to write that all again.
It's essentially what I posted here. I am happy to help you find the problem if you need help.
Steve


A user said he could not send email, or emails he had sent had not arrived.
I sent local email to him and myself and that arrived.
I sent email externally and it did not arrive.
I have a few messages in my outbound queue, so that explains it.
But I looked in the smtp debug logs and I found a few messages like this:

12/18/12 09:12:54 IPAddressManager::OrderList raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 238
12/18/12 09:12:54 IPAddressManager::FillSendSocketAddress_V6 raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 424
12/18/12 09:12:54 IPAddressManager::ReleaseAddressList raised an exception.
The exception occured in : ..\Library\LIBIPAddressManager.cpp, line 163
12/18/12 09:12:54 SendSMTPMessage handled an exception; session will be dropped.
Command: AC6A29FBFEE2445C912A9D4AAEEB4AFF.MAI12/18/12 09:12:55 ME-I0074: [500] (Debug) End of conversation

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Re: IPAddressManager::OrderList raised an exception.

Post by MailEnable » Thu Feb 07, 2013 12:51 pm

Thanks, I have not checked to see the state of the ticket, but I can tell you that the current releases will address the problem.

These two fixes are relevant to Windows 2000
FIX: (SMTP) MailEnable would raise an exception and fail to deliver messages on Windows 2000 servers that did not have IPv6 service update installed.
FIX: (WebMail) WebMail may not work on some installations without Version 3.5 of the framework. Fix was to make installation work on Windows 2000, hence Version 2 of framework.

If you have not already done so, then I suggest applying the update.

Thanks Again
Regards, Andrew

Steevo
Posts: 50
Joined: Fri Jul 15, 2005 4:45 pm

Re: IPAddressManager::OrderList raised an exception.

Post by Steevo » Thu Feb 07, 2013 4:39 pm

OK, I will try the latest update.

BTW, one of those Windows 2000 machines has been changed out for a Windows Server 2003 machine. The machine was having other problems, it ran for 10 years faithfully after all.

I had an installation error on that one, or reinstallation actually, where the ME installer did not open the firewall ports.

I opened them manually after determining the nature of the problem. But I am just not sure that is all safe for security reasons.

I posted on it here but I didn't receive a response. If that is a bug it would likely affect many users.

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Re: IPAddressManager::OrderList raised an exception.

Post by MailEnable » Thu Feb 07, 2013 11:20 pm

Do you mean ports 80, 25, 110, 143 and their SSL equivilents?

MailEnable does not open firewall ports. Err... I dont really think it should. An administrator should do this.
At best I think it should test that the ports are open - which the diagnostic report does attempt to do.
We could probably modify the installer to attempt to check which ports are open, but it would be complicated for example in cases where the server is multihomed.
Regards, Andrew

Post Reply