Sascha Pollok wrote:
> is it true that only ETRN #addressframent works with Exim? A customer of
> mine got some Mailserver running on NT that sends a
> ETRN domainname which does not cause Exim to start a queue - is this right?
It seems so. (And how surprising, that it's some NT crap server that
can't be configured any differently to use #domain.)
This patch may help, but probably makes Exim non-RFC compliant in some
way.
diff -ur exim-2.053/src/smtp_in.c exim-2.053-bcps/src/smtp_in.c
--- exim-2.053/src/smtp_in.c Mon Nov 9 17:01:45 1998
+++ exim-2.053-bcps/src/smtp_in.c Thu Nov 12 20:18:46 1998
@@ -2727,6 +2738,9 @@
since that is strictly the only kind of ETRN that can be implemented.
Advance the pointer past the #. */
+ if (smtp_etrn_command == NULL && smtp_data[0] == '#') smtp_data++;
+
+#if 0
if (smtp_etrn_command == NULL)
{
if (smtp_data[0] != '#')
@@ -2737,6 +2751,7 @@
}
else smtp_data++;
}
+#endif
/* If a command has been specified, set it up for execution. Place the
argument string in the $value expansion variable. */
--
Ben Smithurst
ben@???
send a blank message to ben+pgp@??? for PGP key
--
*** Exim information can be found at
http://www.exim.org/ ***
