Re: Beginner having difficulty saving to IMAP "sent" folder
!-- On Tue 13.Aug'13 at 16:43:53 BST, Mick (michaelkintz...@gmail.com), wrote:
> You may want to try setting 'record' similar to this for sent messages,
> unless
> you want to keep a local copy:
>
> set record = "+INBOX/sent-mail"
>
> if you haven't already done so. With Gmail you wouldn't need to do this.
> --
> Regards,
> Mick
You don't even need to specify $record like that. You have:
set imap_user=...
set imap_pass=...
set folder=imaps://server.com/ <-- note the trailing slash at the end
set record=+Sent (or)
set record=+"Sent Mail" if that's how the mailbox is named on the server
set postponed=+Draft[s] <-- optional 's' select the correct name there
[ ... ]
set smtp_url=smtps://[user[password]@]server.com:[port]
or
set smtp_pass separately, so you just have the server address and port in
$smtp_url.
Basically your {Drafts,Sent,Trash(patch required),...} are an expansion
of $folder which only needs to be prefixed with a + and quoted if there
is space in the folder name. The same principle for local mailboxes.
mutt does use a local MTA to send mail by default unless $smtp_url is set
and mutt is complied with support for that. Then it connects to the
remote smtp server and authenticates with your credentials and the remote
server then sends the mail. The "Sent" mail is then uploaded and stored
in the remote folder as specified by $record. It can be a local folder if
you want it to be.
Some people like offlineimap to use with remote IMAP mailboxes.
--
James Griffin: jmz at kontrol.kode5.net
A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Bold font in Sent listing
!-- On Tue 13.Aug'13 at 17:23:35 BST, Jostein Berntsen (jber...@broadpark.no), wrote: > On 07.08.13,03:05, David Woodfall wrote: > > I find some mail entries are bold in 'Sent' and some not, but I can't > > find any reason why they should be. > > > > set index_format="%3C %Z %[!%d/%m/%y] %-20.20t %s" > > > > Anything it that that would cause bold fonts? > > > > I'd rather not have them if possible. > > > > If you have color settings in muttrc with bright in the color name, they > might be > displayed as bold: > > color body brightblue white regex > > Check that with: > > grep color ~/.muttrc | grep bright > > > Jostein I think we'd need to see more of your settings to determine what's doing this. Your color settings as set using the 'color' command; and any hooks you have that might include color settings. Also any hooks that alter the $index_format for other folders. Some people change the default $index_format for the $postponed mailbox (sent mail) because of the way it display's your own name for example. Also what terminal software are you using? have you changed its settings wrt color? -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
PGP/MIME encapsulated in multipart/mixed
The IMAP server that I have to use does some strange things to the Content-Type header of PGP-encrypted messages: A correctly sent message (as generated by mutt) with | MIME-Version: 1.0 | Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; | boundary="PmA2V3Z32TCmWXqI" | Content-Disposition: inline (and the two attachments | Content-Type: application/pgp-encrypted | Content-Disposition: attachment [...] | Content-Type: application/octet-stream | Content-Disposition: attachment; filename="msg.asc" ) (which is - of course - handled perfectly if received by mutt) is modified by the IMAP server to this form: | MIME-Version: 1.0 | Content-Type: multipart/mixed; | boundary="_003_20130725160657GB18564hostnamewithoutdots_" (and the attachments: | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: text/plain; charset="us-ascii" | Content-Transfer-Encoding: quoted-printable [...] | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: application/pgp-encrypted; name="ATT1" | Content-Description: ATT1 | Content-Disposition: attachment; filename="ATT1"; size=76; | creation-date="Thu, 25 Jul 2013 15:57:21 GMT"; | modification-date="Thu, 25 Jul 2013 15:57:21 GMT" | Content-Transfer-Encoding: base64 [...] | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: application/octet-stream; name="msg.asc" | Content-Description: msg.asc | Content-Disposition: attachment; filename="msg.asc"; size=2389; | creation-date="Thu, 25 Jul 2013 15:57:21 GMT"; | modification-date="Thu, 25 Jul 2013 15:57:21 GMT" | Content-Transfer-Encoding: base64 ) i.e., the PGP/MIME contents seems to be base64-re-encoded and encapsulated in another MIME layer(?) The problem is: mutt (1.5.21) does not understand/know what to do with this message. On the other hand, icedove/thunderbird + enigmail does understand this strangely encoded message (and asks for the gpg passphrase etc.). Is there anything I can do to make mutt recognize that this is a kind of PGP/MIME message? Or can I patch mutt such that it looks not only after the Content-Type: headers but also into the attachments' Content-Type:s? (I wouldn't mind changing the source of mutt locally if this helps.) Thanks in advance, Olaf
