On Thu, Sep 03, 1998 at 04:17:17PM +0100, Paul Mansfield wrote:
> beware, MSoft ETRN doesn't send the hash, not RFC compliant!!!
Are you sure Exim is compliant? I guess Exim should rather
expect a '@' instead of a hash.
RFC 1985 says:
...
5.3 Use Of ETRN to release mail for a subdomain or queue
If the requesting server wishes to release all of the mail for a
given subdomain, a variation on the ETRN command can be used. To
perform this request, the option character '@' should be used in
front of the node name. In this manner, any domain names that are
formed with a suffix of the specified node name are released.
For example, if the command ETRN @foo.com was issued, then any
accumulated mail for fred.foo.com, a.b.c.d.e.f.g.foo.com or foo.com
may be released. It should be noted that the receiving side of the
ETRN command should make a decision based on the client in question
and only allow certain combinations for each of the nodes. This is
more of a security issue than anything else.
...
This perfectly fits Exims behaviour. The hash is intended somehow
different:
...
In a similar vein, it might be necessary under some circumstances to
release a certain queue, where that queue does not correspond to a
given domain name. To this end, the option character '#' can be used
to force the processing of a given queue. In this case, the node
name would be used as a queue name instead, and its syntactical
structure would be dependant on the receiving server. An example of
this would be using the command ETRN #uucp to force the flush of a
UUCP queue. Note that the use of this option is entirely a local
matter and there is no way for a client to find a list of any such
queues that exist.
...
Greetings,
Georg
--
*** Exim information can be found at
http://www.exim.org/ ***
