[Zope] Mailhost strangeness

[Lennart Regebro]

This is a multi-part message in MIME format.
--------------020201040902020209060303
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Kevin Carlson wrote:

 > At seeming random times, a Mailhost object becomes corrupted and does 
not allow the sending of mail.  I get an error that states "integer 
expected" -- see full traceback below.


Enter the MailHost and press 'Change' to re-save the settings.
Or upgrade to 2.6.1. In fact, do both. :)

 > According to the source code it looks like the port number is 
becoming corrupted.  To solve the problem, all I have to do is open the 
Mailhost object and save it.  Strange.


Are you sure it gets to be a string again? That should only happen if 
you upgrade from 2.5.x or import an 2.5.x exported mailhost.

For some reason, the port number was changed from an int to a string in 
2.5.1, and this got reverted in 2.6.0 without anybody noticing.:) In 
2.6.1 it should be an integer, but will not fail if it is a string.

--------------020201040902020209060303
Content-Type: message/rfc822;
 name="Re: [Zope] Mailhost strangeness"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Re: [Zope] Mailhost strangeness"

Message-ID: <3E54F0A3.5020104@regebro.nu>
Date: Thu, 20 Feb 2003 16:13:39 +0100
From: Lennart Regebro <lennart@regebro.nu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9
MIME-Version: 1.0
To: Kevin Carlson <khcarlso@bellsouth.net>
Subject: Re: [Zope] Mailhost strangeness
References: <3E54ECD9.7070605@bellsouth.net>
In-Reply-To: <3E54ECD9.7070605@bellsouth.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Kevin Carlson wrote:
> At seeming random times, a Mailhost object becomes corrupted and does 
> not allow the sending of mail.  I get an error that states "integer 
> expected" -- see full traceback below.

Enter the MailHost and press 'Change' to re-save the settings.
Or upgrade to 2.6.1. In fact, do both. :)

> According to the source code it 
> looks like the port number is becoming corrupted.  To solve the problem, 
> all I have to do is open the Mailhost object and save it.  Strange.

Are you sure it gets to be a string again? That should only happen if 
you upgrade from 2.5.x or import an 2.5.x exported mailhost.

For some reason, the port number was changed from an int to a string in 
2.5.1, and this got reverted in 2.6.0 without anybody noticing.:) In 
2.6.1 it should be an integer, but will not fail if it is a string.


--------------020201040902020209060303--