|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
3 Oct 2021, 11:23 AM | #16 | |
The "e" in e-mail
Join Date: May 2003
Location: mostly in Thailand
Posts: 3,095
|
Quote:
This is one of many issues that is going to arise as soon as you try to simplify what is, when carefully analysed, a complex situation. |
|
3 Oct 2021, 02:21 PM | #17 | ||
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
At any rate, if the actual alias (e.g., service@letterboxes.org) is deleted or disabled then the sending identities would remain but any email sent using these identities will bounce. Quote:
Using your example (but I would want, say, grocery as a form of service) I would define alias services@letterboxes.org target as "services@myFMaccount.fastmail.com. Then when the sender sends to grocery@services.letterboxes.org the X-Resolved-To (where the email is actually delivered) will be myFMaccount+services.grocery@fastmail.com and fuzzy folder matching will try to deliver the message to folder grocery whose parent is services. I can create any number of appropriately named services for corresponding named folders all nested (grouped) under the services folder just by making up names for the local part of @services.letterboxes.org. The services folder itself is only used if the nested folder name doesn't exist (as per "fuzzy folder matching rules). None of this is very complicated so long as you remember "who's on first"! Once set up any names can be chosen to file under the specified target on the fly which no additional work other than creating an appropriately correspondingly named folder, in the example, folders nested under services. Note that deletion of one of the services is one area which does require a little extra work. Since the actual alias cannot be deleted (which is what started this post), because that would wipe out all the other services, I had to add additional Sieve code to selectively check the destination addresses (e.g., grocery@services.letterboxes.org) and appropriately reject (or trash) them if I no longer want them. But it's only a simple edit to a list I keep in the Script. Maybe slightly more work than clicking a button in the UI. Update1: As for choosing a name that could be defined in the sending identity. But it applies to, in this example, all the services unless edited during compose time. Not sure if that's what you were referring to though. Update2: Sorry this post got so long! Last edited by xyzzy : 3 Oct 2021 at 06:51 PM. |
||
3 Oct 2021, 10:12 PM | #18 | |
Senior Member
Join Date: May 2003
Location: Melbourne, Aus
Posts: 116
|
Quote:
When you mentioned it in a recent thread (last week?) I had thought to ask you to expand on the concept. With this explanation I was able to get it to work. (Well, eventually; it took a few tries. It helps to save changes to alias parameters.) Thank you for sharing it. Testing demonstrated the method can be used to have messages sent to a given alias sorted to any folder in your account. Folder name doesn't have to match alias name. Just alter the alias's "Deliver to (send to these addresses)" field (alias target) from: testalias@myFMaccount.FMdomain1.tld to: testfolder@myFMaccount.FMdomain1.tld ...where testfolder was a parent folder created for my test. It worked for child folders of testfolder too when I tried childfolder@testalias.FMdomain2.tld. It's an elegant means of achieving the effect of subdomain addressing. Nifty and versatile! Last edited by Mr David : 5 Oct 2021 at 11:46 AM. |
|
4 Oct 2021, 01:52 AM | #19 | ||
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Quote:
If you decide to delete/unregister service@letterboxes.org then there's no legitimate use for you of the *@service.letterboxes.org identity for /sending/ emails. That's why I think FM would need to look for such definitions and delete them too. The rest of what you describe seems to be about what happens when someone else sends email to one of these addresses, which is not what I was talking about. Quote:
As I said in one of the other posts, the only reason I ever used my wildcard Identity was for one-off changes to the /name/ on an Identity. All my identities have sensible names defined on them. Once in a blue moon I might want to send a mail with a facetious phrase in the sender's "name". The wildcard thing let me do that on the Compose screen for a one-off mail. Now I have to edit the Identity, save it, use it, edit it again back to the sensible value and save that ... which is a whole lot more palaver. |
||
4 Oct 2021, 01:56 AM | #20 | |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Quote:
|
|
4 Oct 2021, 05:45 AM | #21 | ||||
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
Quote:
Quote:
Quote:
Last edited by xyzzy : 4 Oct 2021 at 06:28 AM. |
||||
5 Oct 2021, 12:26 AM | #22 | |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Quote:
But my wildcard was more general, applying to any of my specific letterboxes.org addresses (which had lots of values equivalent to your "service" value). That meant I didn't directly use an identity which specified the "service" part ot the chosen identity. That's why I selected Identities twice on the Compose window's dropdown. I said before that I: - used the Identities dropdown menu first to pick the asterisk identity - used the Identities dropdown menu /again/ to pick the letterboxes identity that I actually wanted to use - the system then showed me the chosen Identity in editable fields My understanding was that I needed to have selected the wildcard to turn on the editable fields, but I needed the second selection to get the required predefined identity loaded into the editable fields. As far as I understand this, you only make/made one selection from the dropdown. To do the same as you I think I'd need to define multiple wildcard identities rather than the single one I had before. I'm not sure it's worth my while doubling the number of defined identities, just for very rare use of the feature. It's simpler just to do the edits the long-winded way. |
|
5 Oct 2021, 05:45 AM | #23 | |||
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
Quote:
Quote:
|
|||
5 Oct 2021, 07:48 AM | #24 | |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Quote:
value: "*.letterboxes.org" and all my other identities were normal - ie a name and a valid email address. |
|
5 Oct 2021, 10:32 AM | #25 |
Essential Contributor
Join Date: May 2018
Posts: 478
|
[quote=JeremyNicoll;622699]name: "Jeremy Nicoll - asterisk fastmail"
value: "*.letterboxes.org" "*.letterboxes.org" ? What does that mean? Or should that have been "*@letterboxes.org"? If so you could use that to "manufacture" a valid email addresses with the letterboxes.org domain. Last edited by xyzzy : 5 Oct 2021 at 04:05 PM. |
5 Oct 2021, 07:45 PM | #26 | |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Well, according to my notes, it meant that exact literal value. I wish I'd kept a screenshot of it before I deleted it a few days ago, because - of course - I can't be certain.
Maybe, but it's not what my notes said. I'm usually careful when I write notes but perhaps I was wrong this time. I can't tell. Quote:
Just now I tried to recreate the identity in the form I thought it had had, and couldn't. But I also then tried to recreate it in the form you suggest - and was allowed to - but its behaviour does not look the same to me as my old one did a few days ago, so I'm not sure it's conclusive. However, this latest one, in the same way as my old one last experimented with a few days ago, no longer supports the load it, then load a predefined non-wildcard identity, then edit the latter one facility that I wanted to have it for. |
|
6 Oct 2021, 11:04 AM | #27 | |
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
The sending alias *@letterboxes.org is not allowed without server settings also. But I already have one like this (with a verify button that cannot be used - who could I verify with) and it still works. I think this because mine existed before this new verify stuff was added so it's sneaking in through the "back door". I don't know what limitations were on creating sending identities before this new verify stuff was added. So whatever you had prior to it they are a lot more restrictive (obsessive?) with making sure you can only use verified stuff now. Wildcard identities involving an alias can only be used when it uses the entire alias (e.g., service@letterboxes.org) so those don't need verification. I was only "probing" you for how you were doing what you said just for my own education of another possible piece of functionality that could maybe be useful to me in the future. What's good about this forum is it can be a great source of tricks others are using. Last edited by xyzzy : 6 Oct 2021 at 11:54 AM. |
|
6 Oct 2021, 11:08 PM | #28 | ||
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 492
|
Quote:
Quote:
that made me try this in the first place. (I kept the URL and the contents of the post in my notes along with (sorry) what now looks like a typo in my notes about what I set up). |
||
7 Oct 2021, 05:09 AM | #29 | |
Essential Contributor
Join Date: May 2018
Posts: 478
|
Quote:
This is different from my pre-existing one which also has a verify button but is not tagged as "unverified" which is probably why it lets me send with it. I don't really have any use for it but I'll keep it in just to see if they ever catch it! |
|
10 Oct 2021, 06:08 AM | #30 | |
The "e" in e-mail
Join Date: Oct 2002
Location: Holon, Israel.
Posts: 4,863
|
Quote:
I had three identities that required verification. One of them was my work email address (at my employer's domain) that I easily verified (but that would not prevent mail sent from it bouncing, since delivering to addresses within the organization fro a source outside would require a different envelope-from, but this feature was cancel long ago). Another is is *@xoxy.net (which is any address at one of SpamGourmet's domains) that I cannot verify because I don't receive all the email for that domain, only email sent to *.user@xoxy.net or *.*.user@xoxy.net (user is one of my two SpamGourmet accounts). I use the identity *@xoxy.net because FastMail identities do not allow the scheme *.user@domain.tld. Right now it still works (I tried it now and it allowed me to send email, and the email was sent and received). The only annoyance is having to retype my username part of the address each time. When verification of identities is enforced It would end one use scenario that I used with FastMail for many years now. The third identity I have that for some unknown reason requires verification is in my own domain, hosted by Fastmail (both DNS and MX), is not a wildcard identity, just a simple email address, and that address is defined as an alias in my account. the alias is bounce@mydomain.tld and it targets bounce+bounce@hadaso.net (it was a scheme that effectively bounced all mail to that address, and to *@bounce.mydomain.tld) before the checkbox to disable delivery to an alias was introduced. As it is a legitimate alias in FastMail, not even set to reject email, I wonder why verification is required for it. |
|