Quote:
Originally Posted by hadaso
My hunch is that these addresses at <something@mydomain> were set up as identities, when then the catch-all alias for the domain was already defined. So they don't have a target of their own but received email to these addresses is delivered using the catch-all alias targets (it is "shared" so it must have more than one target).
The new way of doing things is that when you define a new address like <something@mydomain> it is set up as an alias (with a corresponding sending identity), with target(s) of its own, that override delivery settings of the corresponding catch-all alias (if there is one). If you choose to set up the same address as "an address you already have" then an alias is not created, and either Fastmail determines that it is already handling the email for the address (there is a catch-all alias that includes it, or it is a subdomain address that comes with an existing alias), or else the address has to be "verified" to become address (an email is sent to the address with a link or code, to ensure the user can receive email at the address).
Perhaps the "dot in address" bug is related to detection of the address being a subdomain address at an existing alias (that is the entire address is searched for a dot instead of just the domain part).
|
I suspect you have hit the nail on the head! Do I infer correctly from your comments that at present, it is no longer possible to set up an address as an "Identity"?