1 |
On Tuesday 28 May 2013 02:39:11 Walter Dnes wrote: |
2 |
|
3 |
> First, let's look at what mutt *ISN'T*. It's not a singing-dancing |
4 |
> all-inclusive "integrated" monstrosity. It reads email, writes email, |
5 |
> and hands it off to your local MTA for delivery. In addition to mutt I |
6 |
> also need "getmail" (or equivalant), procmail, and "ssmtp" (or |
7 |
> equivalant). And the organization of my inboxes controls mutt, not visa |
8 |
> versa. |
9 |
|
10 |
I appreciate that this is/was the starting point of mutt, but over the years |
11 |
I understand that mutt has added smtp and is able to use IMAP or POP servers |
12 |
directly. So, am I right to assume that it is not only a simple file reader |
13 |
any more. |
14 |
|
15 |
I have successfully used it with an IMAP server and was able to send and |
16 |
receive, but I'm not entirely sure how to replicate my Gmail settings from |
17 |
Kmail (it errors out, crashes, etc.) |
18 |
|
19 |
|
20 |
> My setup here at home... |
21 |
> |
22 |
> I can receive email from 3 sources... |
23 |
> my personal domain MX |
24 |
> my Google account |
25 |
> my ADSL ISP |
26 |
> my emergency backup dialup account |
27 |
> |
28 |
> I use maildir format storage. I run a script that calls getmail for |
29 |
> each account. getmail passes the emails to procmail, which passes the |
30 |
> emails to the appropriate inboxes. I set up a separate inbox for each |
31 |
> mailing last or group that I belong to. |
32 |
> |
33 |
> mutt reads the email. It "sends" to ssmtp, which is a very simplified |
34 |
> sendmail. All it does is push the email out the door to my ISP's MTA, |
35 |
> which does the real work. I dislike only one thing about ssmtp. It |
36 |
> *INSISTS* on installing "sendmail" symlinks in 3 or 4 different |
37 |
> locations, all pointing back to /usr/sbin/ssmtp. My most embarressing |
38 |
> moment as a user was when a chatty daemon started sending a bunch of |
39 |
> stuff to "root@" my ISP. I did not appreciate that. After that, I |
40 |
> tightened down what stuff gets sent where by daemons, and set up a |
41 |
> script that wipes the symlinks. I have to rerun it after each ssmtp |
42 |
> update. |
43 |
|
44 |
Are you sure about this? I do not have sendmail installed, but do have ssmtp. |
45 |
There are symlinks from sendmail to ssmtp, so that various programs that call |
46 |
sendmail can eventually use ssmtp to send out their messages: |
47 |
|
48 |
$ ls -la /usr/sbin/sendmail |
49 |
lrwxrwxrwx 1 root root 5 Jul 9 2011 /usr/sbin/sendmail -> ssmtp |
50 |
|
51 |
BTW, I have configured ssmpt to send out messages from root (cron job results) |
52 |
through Gmail, using my gmail account credentials. Will I need to alter this |
53 |
to be able to send out messages from mutt through different smtp relays? |
54 |
|
55 |
|
56 |
Another question: how do you manage your address book? |
57 |
|
58 |
I would need email address autocompletion of some sort and I would also need |
59 |
it to be able to pull in the appropriate public gpg or S/MIME key for the |
60 |
intended recipient and my corresponding private key(s) depending on the |
61 |
account that I am sending from. |
62 |
-- |
63 |
Regards, |
64 |
Mick |