Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
unfortunately it runs only with mail-in database and it doesn't work with user's Mail!
the idea was:
Allow easier use of multiple eMail addresses for user
This was shipped in Notes 12.0.0 !!!!
it runs only with mail-in database and it doesn't work with user's Mail!
This was shipped in Notes 12.0.0
https://help.hcltechsw.com/notes/12.0.0/client/select_alternate_from.html
Sending mail from aliases works in Notes 12.
Been using locataion documents for years to do this, but often forget to switch back to my default. So I end up sending weird reply-to addresses to others.
Would be good to have, as Mos suggested, a list of allowed addresses in the users person document (ie in control of admins).
Pick list appears next to the From field.
Additionally the expectations is that this change will work in:
Notes client using an ID
Verse (iNotes as long as it exists)
Traveler and Verse Mobile App
SMTP clients (allow using different senders for the authenticated user)
It would be really handy, if one could set up a list of allowed email addresses in the users person document in NAB like:
mos@gfi.net
mos@kiag.net
mos@cpmo.de
etc.pp.
When composing an email there should be a default address. Switching should be done through a button at the top of the form. Each email address should have its own signature(!).
When replying to an email, it should automatically choose the right address and signature.
I am currently building such an extension to the mail template for a customer. The concept I have written in 2003....
Thanks!
I have to switch IDs all the time as I work for different organizations. The client seems to choke on this. Just really flaky. I think we don't need new functionality for this; we just need to fix the existing functionality.
Saying you can "fudge this with Location documents" is being kind. Anyone with a basic understanding of the Notes client understands why using location documents is not a viable work-around. The analogy I would use is it's like telling someone "driving your car on rims is a work-around for having tires." Yes, you can do it but it is ugly and no one would put up with the associated limitations and failings..
Notes does support a number of standard mail protocols and you can create and manage accounts where you provide the Notes client with e-mail authentication detail and protocol and then the Notes client will replicate mail by accessing a given mail server (POPx, smtp, imap, etc.).
It is very easy to configure a Notes client to replicate and support multiple e-mail servers (and multiple inbound e-mail addresses/accounts) although it seems like this doesn't receive much attention.
Where Notes fails is in allowing the sending of e-mail messages within this context (meaning from the e-mail address you choose rather than the e-mail address associated with the current location document and mail db). Outlook handles this surprisingly well. Notes should, too.
Additionally, Notes should allow a user to choose from signature options or automatically select a signature based upon the "current account context" (meaning when you work with a given e-mail account in your mail db that isn't your specific Notes e-mail account address). Outlook "tracks" this context simply based upon the currently selected "server and folder." I am sure a more elegant and sophisticated set of options could be implemented within the Notes client to support the current accounts option to replicate from additional/alternate mail servers.
Different lokations will Workaround thi issue...