...
These comments are not intended as a criticism - I would love to be
educated if there's stuff that can't be done this way. But it seems
like SMTP authentication, and adding complexities to that, is adding
unnecessary features to LedgerSMB. If LedgerSMB can stick to its core
competencies then it can do those better!
...
It has been a while since I have looked into email sending from
LedgerSMB (and LedgerSMB itself) so the following may not be 100%
correct (and may have been updated since). At the time, the built in
email functionality of LedgerSMB was not sufficient for the
environment
the patch was originally written for. I believe this functionality was
carried over from SQL-Ledger. The mail provider would simply reject
the
method of mail transportation used by LedgerSMB. In order to use the
email functionality of LedgerSMB, it was decided to implement the SMTP
authentication needed by the mail host. The result of this
implementation was the desired use of the built in email
functionality -
it worked as desired for that installation and environment.
Is there a common best practice in LedgerSMB for setting up email
functionality?