On Wed, 29 Apr 2015 15:12:55 +0100, in article
<mhqot6$77b$
1...@speranza.aioe.org> inv...@invalid.invalid
"Richard Stearn" wrote:
> Question for those who have email with the likes of 123-reg, ...
>
> Do they suffer from the issues that intY have managed to create.
> e.g.
Short answers, from my experience of some of them (see below for more
detail):
> 1) munging everything to "administrator" or similar.
Mostly, yes.
> 2) loosing recipients when there is more than one in the envelope
> (may be a consquence of 1)
For catch-all recipients: almost always, yes. 8-(
More detail: my experiences are with a hosting account with 123-reg
(which provides both mailboxes and mail forwarding rules), and mail
forwarding accounts with NetNames, Gradwell, Namesco and 1&1.
Note that 123-reg behaves differently depending on whether the mail goes
to a mailbox or gets forwarded (you only get the useful extra header
fields if it goes to a mailbox); it's possible the others do too, in
which case my mail forwarding experiences may not represent their mail
hosting products.
Note further that Demon/intY are the only people I've come across with a
mechanism to allow multiple recipient addresses for non-catch-all
mailboxes; the others have one address per mailbox or forwarding rule,
plus a catch-all.
123-reg:
1) Yes: the apparent recipient for catch-all mail is modified to the
mailbox name, so the latest (top-most) "Received:" field contains
"for <catchall-address>" rather than "for original-recipient"
(inconsistent usage of angle brackets faithfully represented).
However, they add an "Envelope-to:" field containing all the
original recipient addresses for the message -- but only if the
message goes to one of their mailboxes. If it's forwarded to an
external address, that field isn't present.
2) Yes: if the message is sent to more than one catch-all recipient,
only one copy enters the catch-all mailbox or gets forwarded. If
recipients have their own mailboxes or forwarding rules, each one of
those gets a copy.
Sample header fields for a single catch-all mailbox recipient:
Delivered-To: <catchall@domain>
Received: from
mail12.atlas.pipex.net ([10.15.14.75])
by
imap-16.mailcore.me (Dovecot) with LMTP id wBMbAujGSVUFEAAA4bejhQ
for <catchall@domain>; Wed, 06 May 2015 08:48:27 +0100
Envelope-to: foo@domain
Delivery-date: Wed, 06 May 2015 08:48:26 +0100
Received: from xxxx ([xx.xx.xx.xx])
by
mail12.atlas.pipex.net with esmtp (Exim 4.71)
(envelope-from <sender@sender-domain>)
id 1Ypu4A-0001Ry-Rp
for foo@domain; Wed, 06 May 2015 08:48:26 +0100
From: Sender <sender@sender-domain>
To: foo@domain
For two catch-all mailbox recipients [foo, bar] and one specific
mailbox [test] (all messages have an identical header; note how
being delivered to multiple mailboxes inhibits the "Delivered-To:"
field):
Received: from
mail4.atlas.pipex.net ([10.15.14.67])
by
imap-16.mailcore.me (Dovecot) with LMTP id K17cNCjGSVW/JAAA4bejhQ
; Wed, 06 May 2015 08:43:39 +0100
Envelope-to: foo@domain,
bar@domain,
test@domain
Delivery-date: Wed, 06 May 2015 08:43:39 +0100
Received: from xxxx ([xx.xx.xx.xx])
by
mail4.atlas.pipex.net with esmtp (Exim 4.71)
(envelope-from <sender@sender-domain>)
id 1YptzX-0003iz-7C; Wed, 06 May 2015 08:43:39 +0100
From: Sender <sender@sender-domain>
To: test@domain, foo@domain, bar@domain
Forwarded messages are handled similarly, except (a) they don't get
the "Delivered-To:", "Envelope-to:" or "Delivery-date:" fields at
all, and (b) if the message is forwarded to more than one address at
the same domain, only a single copy is sent to that domain (with
multiple recipients):
Received: from
mailex.mailcore.me ([94.136.40.146]) by zzzz
with ESMTP id AAnnnnnn; Tue, 05 May 2015 13:24:20 +0100 (BST)
Received: from xxxx ([xx.xx.xx.xx])
by
smtp05.mailcore.me with esmtp (Exim 4.80.1)
(envelope-from <sender@sender-domain>)
id 1YpbtZ-0005ld-Dw; Tue, 05 May 2015 13:24:17 +0100
From: Sender <sender@sender-domain>
To: fwd@domain, foo@domain, bar@domain
For the mail forwarding accounts (NetNames, Gradwell, Namesco and 1&1),
Gradwell are the only people who do it properly:
1) No and yes: the forwarding servers don't write "Received:" fields
once the forwarding have been applied, so *they* don't mung
anything, but of course the servers receiving the forwarded messages
will see the forwarded-to addresses and may put them into
"Received:" fields of their own (which looks like munging once the
dust has settled).
2) All expect Gradwell discard additional recipients for the catch-all
rule; they just keep the first one that matched the rule, and that's
the address that goes into the X-* header field (below). Gradwell
do it properly, with a separate copy of the message for each
catch-all recipient, each with its own "X-Envelope-To:" header
field.
NetNames, Gradwell and Namesco all provide a header field in the
forwarded message telling you who the original recipient was
("X-Originally-To:", "X-Envelope-To:", "X-Original-To:"
respectively).
1&1, like 123-reg, make no such attempt: if you can't work out the
recipient from the standard headers ("To:", "Cc:", "Received:" etc.)
or the post-forwarding recipient address, you have no way to find
out.
It may be worth noting that the NetNames, Gradwell and Namesco
forwarding accounts are all "legacy" ones that may be running on
different physical platforms from their current offerings, and may
therefore not represent the behaviour you would get from a new account.
(Gradwell are moving all their customers to their "cloud" platform, and
have warned that some services will change, so I'll probably find out
soon whether they are still as clueful as they used to be. And NetNames
are moving customers to their new Speednames.uk service, which I
pessimistically suspect will not be as good as the old one was.)