On 7/11/06 6:52 AM, "Philip Hazel" <ph10@???> wrote:
> What I'm thinking of doing is this:
>
> 1. See if the message matches ^\d\d\d\s(\d\.\d{1,3}\.\d{1,3}\s)?
>
> FOR SMTP MESSAGES:
>
> 2. If not, add the code as now.
>
> 3. Otherwise, if the first digit is the same as the first digit of the
> default code, use the provided code instead.
>
> 4. Otherwise, log an error, and replace with the current code.
>
> FOR NON-SMTP MESSAGES:
>
> 2. If it matches, remove the code from the message.
>
>
> COMPATIBILITY
>
> This change is not backwards compatible. However, how much does this
> actually matter in practice? The only times it will cause a problem is
> if an existing configuration is using messages that start with 3 digits.
> This does not seem very likely.
>
> There could, of course, be a global option to disable this. I propose
> not to implement such a thing because I don't think it would ever be
> used.
>
> What do other people think?
I think you have this right. As you said in a later message, enhanced
status codes is a different "game".
--John
