design - local MTA even if a reliable remote MTA is available -
i had discussion our development team have local mta installed on application server or if should use mta server located on internal network send emails. there pros , cons both solutions.
pros: program sending email can deliver local mta , forget delivery, retries or errors may arise.
cons: user sending email may informed late there issue on sending mail. program detect if remote server not available. cons: security. local mta must configured adequately ensure security of server cons: additional layer of complexity in process.
in view, should keep simple. not talking program talking mta servers not controlled , not know state of it. in view, having local mta necessary if unsure counter parts here, program deliver "known" mta system. think additional layer not necessary. furthermore having local mta on each system trying send emails may lead additional problems/errors , more administrative tasks (maintenance/patching). may on unix system have local mta (sendmail) running in our organisation strip down systems minimum ensure services not running lead potential risk.
however, interested know how design infrastructure keeping in mind talk known/controlled/monitored mta system. or matter of viewpoint?
many feedback.
yves
if remote mta ("... mta server located on internal network ...") under same administration proposed local mta and latter deliver remote mta (acting sort of relaying 'smart host'), there no need local mta.
the question if local applications/users sending mails live potential additional risk of network failure when trying reach remote mta.
Comments
Post a Comment