|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
1 Dec 2019, 11:17 AM | #61 | |
The "e" in e-mail
Join Date: Jul 2002
Location: VK4
Posts: 3,029
|
Quote:
Yes it will work in my own domain. |
|
1 Dec 2019, 11:24 AM | #62 |
The "e" in e-mail
Join Date: Jul 2002
Location: VK4
Posts: 3,029
|
|
1 Dec 2019, 11:41 AM | #63 |
Essential Contributor
Join Date: Mar 2007
Location: UK
Posts: 270
|
.......
Last edited by Grhm : 1 Dec 2019 at 03:35 PM. |
1 Dec 2019, 04:00 PM | #64 |
The "e" in e-mail
Join Date: Oct 2002
Location: Holon, Israel.
Posts: 4,858
|
|
1 Dec 2019, 08:27 PM | #65 |
Essential Contributor
Join Date: Mar 2007
Location: UK
Posts: 270
|
Yes, but it's worth stressing, for the benefit of the people who have been requesting this as a feature, that if you select a * wildcard sending-identity on any domain, you can then edit the send address, on the compose screen, to anything at all: you're not restricted to addresses on that domain.
|
2 Dec 2019, 03:39 AM | #66 |
Essential Contributor
Join Date: Dec 2008
Location: Canada
Posts: 312
|
The ability to add users at a lower service level than the primary account.
|
2 Dec 2019, 07:30 AM | #67 | |
The "e" in e-mail
Join Date: Jul 2002
Location: VK4
Posts: 3,029
|
Quote:
Its only if you have this already set up. Last edited by Terry : 2 Dec 2019 at 07:54 AM. |
|
2 Dec 2019, 10:25 AM | #68 |
Essential Contributor
Join Date: May 2018
Posts: 478
|
FWIW, when I originally experimented with wildcard aliases I created, for example, the alias xyz@sent.com and then a sending identity *@xyz.sent.com. Selecting that from the compose sender popup produces an editable From (and I assume should still work for everyone). But I gave up on these kind of wildcard sending identities because of some "quirks" I didn't like.
Quirk 1: If you have a number of sending identities in the sender compose popup then whatever is shown as the selection in the popup would supply the name part of an email address to replace the * when you selected the wildcard alias. While you always would have to edit the From anyhow I would have preferred it just left the * in the initial From address and not show an unassociated name. Quirk 2 (most annoying): If the recipient replies to whatever you used, and you want to reply to that, the From in the reply compose doesn't show the sent address you used so you always must edit the From: in your reply to their reply. This is the inconvenient. Why isn't the default reply supplied from the To: of the reply you are trying to reply to? |
2 Dec 2019, 05:04 PM | #69 |
Essential Contributor
Join Date: Mar 2007
Location: UK
Posts: 270
|
Agreed.
(Your "Quirk 2" = My "★3", above) |
2 Dec 2019, 09:24 PM | #70 |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 493
|
Update: I reported the inability to add (eg) *@sent.com as an identity (because of the insistence of the webpage that one then has to define an SMTP server etc) as a bug.
It turns out that (to my mind) it is a bug though FM don't seem to agree. What's happened is that in the Advanced Preferences that you can open at the foot of the definition page, FM have pre-ticked the bit that says "I want to use an external SMTP server". So the bit you do see expects you to provide the server details. If you open Advanced Preferences, and turn off the "I want to use an external SMTP server" setting, you CAN define an asterisk id. |
3 Dec 2019, 02:31 AM | #71 |
The "e" in e-mail
Join Date: Oct 2002
Location: Holon, Israel.
Posts: 4,858
|
One little thing I would like is that in the contacts, in addition to "personal", "work" and "other", there would be "old" (or "obsolete"). Same would be nice in other fields, such as phone, but not as essential as for email addresses.
I do not erase old email addresses from contacts, because when viewing old messages those addresses are associated with the contact they belong to/ on the other hand, when composing they appear as suggested addresses when the contact's name is typed. So what I would like is that addresses designated as "old" (or "obsolete") would be excluded when composing email, but would still identify the right person when viewing archived mail. BTW, is there a way to search for all mail related to a contact? I don't see anything like this in the advanced search screen. I think this can be quite useful: an option to search for email that contains, either in the headers or in the text, any of the email addresses or phone numbers included in a contact entry. I usually search for email by the sender of the current viewed message, by clicking the search field that already has the sender's address displayed as an option. Today I searched this way for my brother's email, and got very little email: only the ones with his current work address. People in hi-tech tend to change email addresses as often as other people change socks... |
3 Dec 2019, 09:56 AM | #72 |
Essential Contributor
Join Date: May 2018
Posts: 478
|
Speaking of contacts, it would be nice if contacts allowed my liberal use of globing. For example at the very least, *@*.domain and name@*.domain.
Currently all that's allowed is *@domain in the contacts but some organizations (at least some I gety mail from) use sub-domains preceding their top domains and I cannot always anticipate what they might use to enumerate them all in the contacts list. I get around this in my Sieve script but I think it would be be preferable in all one place, i.e., the contacts. |