On Thu, 5 Feb 1998, Tabor J. Wells wrote:
> The syntax in 5 above implies that both "@" and no option character need
> to be allowed, and yet exim allows neither. It also seems that from the
> 3rd paragraph of 5.3 above, that using "#" in place of "@" isn't
> appropriate either since that is for cases where the queue doesn't match a
> domain name.
>
> So I guess my question is "What are the plans for ETRN in exim supporting
> '@' and no option character in the near future?" :)
There are some plans. I don't know how near this particular future
actually is, but it might not be too far off in terms of Exim releases.
However, I'm not planning a new release for a while - lots of updating
going on.
> We're going to be
> ditching sendmail in favor of exim on our relays in the near future, and
> the current implementation of ETRN in exim will break some of our dialup
> SMTP customers where their gateways issue ETRN in the form of "@domain" or
> just "domain".
It's a trivial hack to the code to fudge it for @. Line 2192 of
src/smtp_in.c contains
if (smtp_data[0] != '#')
If you change this to
if (smtp_data[0] != '#' && smtp_data[0] != '@')
then it will treat @ the same as #.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
