I don't see the big deal here. After initial setup, on every account you can select which SMTP server you wish to use and in the "Outgoing Server (SMTP)" section you define/edit them - very handy and straightforward to me. Is there really a need to go to all the hassle of rewriting this?
I know this is a 4 weeks old thread, but as a heavy Epyrus user and SMTP sysadmin, here are a few missing factoids:
- At least on the authenticated SMTP servers I run, each authentication account is explicitly limited to a small subset of organizational mail addresses, for example, the login I use from Epyrus on my main office PC can send from multiple mail addresses whose incoming mail appear in different folders on the matching IMAP login (using Epyrus "identities"), this includes both my primary mail account and various role accounts such as Postmater@domain.tld. In particular, I cannot send from mail addresses of other users except by abusing mail server admin privs outside Epyrus.
- Unauthenticated incoming mail has a different path through the system that set relevant Spam detection headers that I would love to integrate with Epyrus .
- NNTP accounts in Epyrus are mentally associated with a mail address that exists elsewhere in Epyrus for the Reply to sender option, but are set to use a mangled mail address in public posts as a traditional antispam measure
- The New account wizard in Epyrus 2.1.2 seems to have badly broken logging of its actions. In particular, setting the logging options from old Tb discussions will not log the initial undocumented HTTP lookups and do not say anywhere precisely what aspect of a non-california mail server account access failed to make the wizard block account creation.
- I have seen rumors that this broken old wizard will be gone in the next release.