RE: [Exim] 501 malformed address

Top Page
Delete this message
Reply to this message
Author: Troy Settle
Date:  
To: 'Exim Users Mailing List'
Subject: RE: [Exim] 501 malformed address
Yeah, I finally had some time to work on this (since leaving the office
and getting home). I apologize for the last 2 messages, they were
composed while I was concentrating more on another fire.

It seems that the sending MTA is not understanding that my MTA is not
advertising the DSN capability:

ehlo test
250-psknet.com Hello grant.psknet.com [63.171.251.7]
250-SIZE 157286400
250-PIPELINING
250 HELP

Now I get to email this guy and rip him a new one for telling my
customer that my mail server is broke.

=D

--
Troy Settle
Pulaski Networks
http://www.psknet.com
540.994.4254 ~ 866.477.5638
Pulaski Chamber 2002 Small Business Of The Year


> -----Original Message-----
> From: exim-users-admin@???
> [mailto:exim-users-admin@exim.org] On Behalf Of Greg A. Woods
> Sent: Tuesday, June 17, 2003 8:35 PM
> To: Troy Settle
> Cc: Exim Users Mailing List
> Subject: RE: [Exim] 501 malformed address
>
>
> [ On Tuesday, June 17, 2003 at 20:00:11 (-0400), Troy Settle wrote: ]
> > Subject: RE: [Exim] 501 malformed address
> >
> > Does this look like something that would be generated by
> Exim? If so,
> > would it be in the logs? (I can't find it if there is a log entry):
> >
> > 501 <5102715492@???> RET=HDRS ENVID=16792718l:
> > malformed address: RET=HDRS ENVID=16792718l may not
> > follow <5102715492@???>
>
> Yes, from examination of the source it seems Exim-4.20 could have
> uttered that response:
>
>     $ fgrep 'malformed address: ' *.c
>     parse.c:      string_sprintf("malformed address: %.32s
> may not follow %.*s",
>     parse.c:    *errorptr = string_sprintf("malformed
> address: %.32s may not follow %.*s",

>
> > Hmm... Seems that Exim isn't following RFC1891 or maybe I don't have
> > something configured right.
>
> As far as I can tell from the source Exim-4.20 does not
> implement any of
> RFC 1891 and by testing we can also see that it does not
> claim to do so
> in its EHLO response:
>
>     $ telnet mail.exim.org 25
>     Trying 195.92.249.251...
>     Connected to mail.exim.org.
>     Escape character is '^]'.
>     220 exim-colo-01.whoc.theplanet.co.uk ESMTP Exim 4.20
> Wed, 18 Jun 2003 01:29:37 +0100
>     EHLO proven.weird.com
>     250-exim-colo-01.whoc.theplanet.co.uk Hello
> [xupE6xfWuZedc7xjdkxdURYZ5bkrwBEz855fmSRu8LG3FdwTeYJHgn1A88Csf
> 0yeRswmEQ3bUVvqlhpdtrMBxA==] at proven.weird.com [204.92.254.15]
>     250-SIZE 52428800
>     250-8BITMIME
>     250-PIPELINING
>     250 HELP
>     quit
>     221 exim-colo-01.whoc.theplanet.co.uk closing connection
>     Connection closed by foreign host.

>
> What mailer connected to exim and triggered that response from it?
>
> I would suggest whatever mailer it was is the one that
> doesn't properly
> implement RFC 1891! It should not have given RET and ENVID option
> parameters with its MAIL command if it did not see a proper "DSN"
> keyword in the EHLO response.
>
> --
>
> Greg A. Woods
>
> +1 416 218-0098;            <g.a.woods@???>;
> <woods@???>
> Planix, Inc. <woods@???>; VE3TCP; Secrets of the Weird
> <woods@???>

>
> --
>
> ## List details at
> http://www.exim.org/mailman/listinfo/exim-> users Exim details
> at http://www.exim.org/ ##
>
>