Hey Brian On Wed, Apr 20, 2011 at 09:24:39AM +1000, Brian May wrote: > On 19 April 2011 20:38, Salvatore Bonaccorso <car...@debian.org> wrote: > > > > First of all, thanks for your feedback. I mark this bug as wishlist, > > because this is probably beyond the scope of esmtp. esmtp was never > > intended to be a full MTA, but only a relay-only. It has however nice > > features like the ability for mailing locally, which e.g. is not (yet) > > possible with msmtp (which is surely actively developped). > > > > Thanks for your response. I think logging is very important despite it being > relay only; without logging it is not possible to find out if anything has > gone wrong, or what has gone wrong. e.g. Yesterday I received a > automatic notification that my system was generating too much port 25 > traffic, but I can't diagnose this issue because esmtp doesn't log anything, > and my smart host was off-line at the time. So I would really like to know > what esmtp was doing at the time... > > Unfortunately, it would appear that the msmtp people aren't interested it > having it work correctly with local addresses. See bugs #623294 and #578017.
Yes I see the problem. The Problem is, for esmtp someone needs to step in to take over the development, to add the syslog feature as msmtp has it. On the other side msmtp is really actively developped, but does not have some of the features which esmtp has (and cleary viceversa, e.g. logging!). I will try to look forward on this issue. Best regards Salvatore
signature.asc
Description: Digital signature
