On 17/07/10 01:37 PM, Stroller wrote: > On 17 Jul 2010, at 00:11, Schmiechen wrote: >> ... >> Nice patch however it seems you can have only one mail configuration >> per >> installation of Ledgersmb if you store the data in Sysconfig.pm. >> >> When hosting more than one business on a server is it typical to >> have a >> different domain or folder for each business? Thus a different >> install of >> Ledgersmb for each business? I wonder is this what ledger123 does? > If hosting multiple instances of Ledger-SMB, shouldn't the hosting > provider simply make SMTP accommodations? > > > On 17 Jul 2010, at 01:52, Schmiechen wrote: >> Well it apparently does not work with TLS. >> I guess I need to modify it to use Net::SMTP::TLS? > Likewise, who cares? LedgerSMB should throw email at Postfix or ssmtp > on the local machine, and that should figure out how to handle the > mail upstream. > > 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! > > Stroller. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Ledger-smb-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Thanks for the comments. I am in complete agreement about sticking to the core competencies and not adding features/complexities that are neither the goal nor the nature of the application. 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? I am in the process of setting up LedgerSMB again and looking into email sending. This discussion has spiked my interest. Ryan MacFarlane ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
