The masked e-mail feature is great, but the resulting addresses are so long and convoluted they are impossible to use e.g. over the phone.
I try to create a new e-mail address for every non-personal contact, so I can track who sells e-mails or is compromised.
Apple’s hide my e-mail addresses are resonably short and readable: [email protected]
Something like that one can tell someone over the phone, and it fits on paper forms.
The kind of addresses Stalwart produces are unusable outside of automatically filled in forms, and even there chances are, that they are longer than the form permits.
Any chance of allowing limits on the length (airline booking codes are six letters long and cover millions of travelers) or use a readable “password” generator?
Thanks
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
Yes, you can control this: when creating a masked email you can set an emailPrefix to specify the local-part prefix yourself (up to 64 characters, lowercase letters, digits, and underscore), instead of letting the server generate the default random 16-character string. The domain can also be chosen via emailDomain from any domain your account has access to.
There’s no built-in short “readable word” generator (like a passphrase-style code), and no setting to shorten the random suffix length beyond supplying your own prefix. If you want something like [email protected], you’d need to supply that prefix yourself each time you create the mask (e.g. via the WebUI Account Manager’s masked email creation form, or the JMAP API), since Stalwart’s auto-generated part is a fixed-length random alphanumeric string appended for uniqueness.
The prefix doesn’t help, if Stalwart then still appends a character salad after the prefix.
What’s needed is either a limit on what Stalwart creates (e.g. 8 characters) or the possibility to supply the full pseudo username, to which nothing is appended, then a readable password generator could be used to supply the user name, like e.g. here:
The code can’t be shortened or dropped as things stand. It carries the address’s id, its expiry and a checksum, which is how the server routes a masked address without a lookup table and why nobody can guess a valid one. Packing all that into base36 is what makes it around 25 characters.
For short, readable per-contact addresses there are two other routes. Sub-addressing is on by default, so you+airline@yourdomain reaches you with no setup and you can filter or block on the tag (RCPT stage | Stalwart). If you’d rather the addresses not point back at your name, put a dedicated domain or subdomain on a catch-all to your account, and any quantum-dog.254@ you make up works on the spot; you block a leaked one with a Sieve rule. A catch-all also accepts spam sent to random local parts, so I’d only use it on a domain reserved for this.
A shorter masked format would be a separate address scheme with its own lookup, so I’m treating it as a feature request.