1 |
On Tue, May 28, 2013 at 12:55:54PM +0100, Mick wrote |
2 |
> |
3 |
> I appreciate that this is/was the starting point of mutt, but over |
4 |
> the years I understand that mutt has added smtp and is able to use |
5 |
> IMAP or POP servers directly. So, am I right to assume that it is |
6 |
> not only a simple file reader any more. |
7 |
|
8 |
I did say I'm a long time user of mutt ;) I didn't realize that it has |
9 |
added smtp. |
10 |
|
11 |
> Are you sure about this? I do not have sendmail installed, but |
12 |
> do have ssmtp. There are symlinks from sendmail to ssmtp, so that |
13 |
> various programs that call sendmail can eventually use ssmtp to send |
14 |
> out their messages: |
15 |
> |
16 |
> $ ls -la /usr/sbin/sendmail |
17 |
> lrwxrwxrwx 1 root root 5 Jul 9 2011 /usr/sbin/sendmail -> ssmtp |
18 |
|
19 |
I get ssmtp symlinks to... |
20 |
/usr/bin/sendmail |
21 |
/usr/sbin/sendmail |
22 |
/usr/lib64/sendmail |
23 |
|
24 |
> BTW, I have configured ssmpt to send out messages from root (cron |
25 |
> job results) through Gmail, using my gmail account credentials. |
26 |
> Will I need to alter this to be able to send out messages from mutt |
27 |
> through different smtp relays? |
28 |
|
29 |
I have one main machine at home, and I *DON'T* want daemons mailing |
30 |
stuff out all over the place, so my problem is quite different from |
31 |
yours. I think that daemons *EXPECT* a file or symlink called sendmail |
32 |
to accept their email. If you want daemons sending log mails, then you |
33 |
need something that emulates sendmail. |
34 |
|
35 |
> Another question: how do you manage your address book? |
36 |
> |
37 |
> I would need email address autocompletion of some sort |
38 |
|
39 |
The file ~/.mutt/.aliases is where addresses are stored. E.g. the line |
40 |
for this mailing list is... |
41 |
|
42 |
alias gentoo gentoo-user@l.g.o (Gentoo Users List) |
43 |
|
44 |
I hit "m" for "mail compose". When prompted for "To:", I type in... |
45 |
|
46 |
gen |
47 |
|
48 |
...and hit {TAB}, which gives "gentoo". This is replaced with... |
49 |
|
50 |
gentoo-user@l.g.o (Gentoo Users List) |
51 |
|
52 |
|
53 |
> and I would also need it to be able to pull in the appropriate public |
54 |
> gpg or S/MIME key for the intended recipient and my corresponding |
55 |
> private key(s) depending on the account that I am sending from. |
56 |
|
57 |
I don't do PGP, so I'm not able to answer that question. Here's |
58 |
something from the mutt manual that might be what you're looking for... |
59 |
|
60 |
http://www.mutt.org/doc/manual/manual-3.html#ss3.19 |
61 |
|
62 |
> 3.19 Choosing the PGP key of the recipient |
63 |
> |
64 |
> Usage: pgp-hook pattern keyid |
65 |
> |
66 |
> When encrypting messages with PGP, you may want to associate a certain |
67 |
> PGP key with a given e-mail address automatically, either because |
68 |
> the recipient's public key can't be deduced from the destination |
69 |
> address, or because, for some reasons, you need to override the |
70 |
> key Mutt would normally use. The pgp-hook command provides a method |
71 |
> by which you can specify the ID of the public key to be used when |
72 |
> encrypting messages to a certain recipient. |
73 |
|
74 |
-- |
75 |
Walter Dnes <waltdnes@××××××××.org> |
76 |
I don't run "desktop environments"; I run useful applications |