-----Original Message-----
From: owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-mxcomp(_at_)mail(_dot_)imc(_dot_)org]On Behalf Of David
Woodhouse
Sent: Wednesday, September 15, 2004 7:29 AM
To: Graham Murray
Cc: ietf-mxcomp(_at_)imc(_dot_)org
Subject: Re: DEPLOY: Permitting '-all' to be used immediately
represents
aflag day.
On Wed, 2004-09-15 at 11:42 +0100, Graham Murray wrote:
Do not forget that as far as the sender is concerned, the
site doing the forwarding is the intended recipient of the
email. So,
it is the recipient's problem and responsibility to accept mail sent
to addresses which are then forwarded to them.
That may be true, but it is the responsibility of this
working group to
propose a solution for this newly-imposed problem, and ensure that any
necessary changes to current practice become widespread -- _before_
starting to rely on assumptions about it.
There *is* a solution. If your domain does forwarding through SMTP servers
that do not yet have the
mechanism(s) necessary to work, then publish with ~all. For those domains who
don't have/allow any
forwarding and/or the known allowed forwarders have the necessary mechanisms in
place, -all is
perfectly acceptable.
I am not suggesting that '-all' should be permanently
forbidden, merely
that it must be forbidden in the first release of the new
specification,
and must remain so until such time as the proposed solutions are
widespread.
I have to 100% disagree:
If the solution does not start working for at least *some* in the short term,
then there will be
reduced/zero perceived benefit which discourages buy-in from undecided fence
sitters.
--
dwmw2
Terry Fielder
Manager Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
terry(_at_)greatgulfhomes(_dot_)com
Fax: (416) 441-9085