1 |
On Mon, Mar 12, 2012 at 08:20:08PM +0000, Robin H. Johnson wrote: |
2 |
> On Mon, Mar 12, 2012 at 10:07:48PM +0200, Samuli Suominen wrote: |
3 |
> > ssmtp has been quiet project for quite a while, where as msmtp is |
4 |
> > maintained one. |
5 |
> > |
6 |
> > sure, ssmtp might be just mature, but msmtp is equally small and has |
7 |
> > more features. |
8 |
> > |
9 |
> > any thoughts? |
10 |
> +1 to getting rid of ssmtp. But I'm not sure that msmtp is the best |
11 |
> replacement. |
12 |
> |
13 |
> One of the greatest things that bugs me about ssmtp is that if the |
14 |
> mailserver is not available, it hangs for a while, and then it loses the |
15 |
> email. |
16 |
> |
17 |
> Where I need a simple mail relay, I've gone with nullmailer instead, |
18 |
> because it supports the features, and it explicitly has a lightweight |
19 |
> daemon mode that queues mail to send. |
20 |
|
21 |
At isolated places where i don't integrate my host into an existing mail |
22 |
setup, i use esmtp because it allows me to do local delivery of system |
23 |
mails (cron or similar jobs) by using a very simple setup: |
24 |
|
25 |
~ $ cat /etc/esmtprc |
26 |
mda="/usr/bin/procmail -d %T" |
27 |
|
28 |
That's about the only config i need for this. Ok, it's not perfect |
29 |
because it requires procmail (no setup task required though) and cannot |
30 |
write the files directly. |
31 |
|
32 |
I think as an initial setup, something that just does local delivery |
33 |
for system mails out of the box is better than something that doesn't |
34 |
work unless you start configuring smart relay hosts etc. You can still |
35 |
do this if you integrate yourself into an existing mail setup. |
36 |
|
37 |
Christian |