Re: .muttrc: Accessing attachment filename and quoting

[Kevin J. McCarthy]

On Thu, Aug 24, 2023 at 05:10:39PM +0200, Orm Finnendahl wrote:

Hi,

1. I try to write a macro allowing to open an attachment with another
   than the default program. Is there a way to refer to the filename
   of the attachment in the macro definition (like the %s in
   mailcap)?


No.  You might play around with the `test=` field in the 
mailcap and see if you can use that somehow.  For example, one idea 
(untested) would be using setenv in the macro around the attachment 
opening:


macro ,a 'setenv ATTPROGRAM 
foounsetenv ATTPROGRAM'
macro ,b 'setenv ATTPROGRAM 
barunsetenv ATTPROGRAM'

And in your .mailcap

application/baz; fooprogram %s; test=test x$ATTPROGRAM = xfoo
application/baz; barprogram %s; test=test x$ATTPROGRAM = xbar
...
application/baz; defaultprogram %s


2. When piping an attachment to an external program, filenames with
   spaces don't work. is there a way to enclose the filename with
   quotes before submitting it to the pipe?


You'll have to be more specific about what you are doing and how it's 
failing.


--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

.muttrc: Accessing attachment filename and quoting

[Orm Finnendahl]

Hi,

 1. I try to write a macro allowing to open an attachment with another
than the default program. Is there a way to refer to the filename
of the attachment in the macro definition (like the %s in
mailcap)?

 2. When piping an attachment to an external program, filenames with
spaces don't work. is there a way to enclose the filename with
quotes before submitting it to the pipe?

--
Orm

Re: sample muttrc file for AOL email...

[Sam Kuper]

On Thu, Apr 13, 2023 at 04:22:01AM -0500, Lester Rees wrote:
> Damn, I never thought getting help configuring Mutt for my AOL email
> account would be such a big hassle.  I used to use mutt for my Gmail
> accounts, but Google, as you know [is phasing out app-specific
> passwords].

As others in this thread have noted, Mutt can indeed be used
successfully with AOL and with GMail.

That said, GMail is not terribly friendly towards people who prefer
traditional email clients like Mutt, and given that Yahoo keeps changing
hands, it's hard to predict what Yahoo (AOL's owner) will do in future.

IMO, the best way to avoid such headaches is to switch to a more
ethical, more user-friendly email provider.  As you can tell from my
email address, I use Posteo, but there are other options, too.  For
instance, Drew DeVault recommends Migadu.com or Mailbox.org :

https://drewdevault.com/2020/06/19/Mail-service-provider-recommendations.html


> Instead, I get a whole bunch of hassle from everyone.   Leave it human
> beings to make things more complicated than they should be!!! 
> Damn!!!  You know, the less I have humans involved with my life, the
> less stress and fewer problems I have.

It's important to distinguish between:

1.  Human beings who are making your life harder and who may not
actually care. (E.g. maybe product managers at Google, and perhaps
AOL too; miscreants whose abuse of traditional authentication in the
past & present has encouraged Google to migrate fully to OAuth.)

2.  Human beings who are trying to help you & others like you, because
they *do* care. (Volunteers on this mailing list!  The authors &
maintainers of Mutt!  People who run ethical, user-friendly email
service providers!)

Learning to distinguish between the two groups helps reduce stress.

Good luck in your quest.

Sam

Re: sample muttrc file for AOL email...

[Patrick Shanahan]

* Steve Karmeinsky  [04-13-23 09:14]:
> On Thu, Apr 13, 2023 at 05:26:06AM -0500 or thereabouts, Lester Rees wrote:
> 
> >No, Gmail no longer allows Mutt to be used for it.  Google considers it
> >to be a "less secure app."  Hence, they do not allow Mutt to be used
> >with it.  I have tried and have failed since Google made that change to
> >Gmail.
> 
> Well that is strange as this email is using mutt and a Google Workspace
> account and I'm guessing you're getting it fine (yes you do need an app
> password).

yes, same here for quite some time.


-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet oftc

Re: sample muttrc file for AOL email...

[Steve Karmeinsky]

On Thu, Apr 13, 2023 at 05:26:06AM -0500 or thereabouts, Lester Rees wrote:

>No, Gmail no longer allows Mutt to be used for it.  Google considers it
>to be a "less secure app."  Hence, they do not allow Mutt to be used
>with it.  I have tried and have failed since Google made that change to
>Gmail.

Well that is strange as this email is using mutt and a Google Workspace
account and I'm guessing you're getting it fine (yes you do need an app
password).

ignore *
unignore From:
unignore To:
unignore Reply-To:
unignore Mail-Followup-To:
unignore Subject:
unignore Date:
unignore Organization:
unignore Newsgroups:
unignore CC:
unignore BCC:
unignore Message-ID:
unignore X-Mailer:
unignore User-Agent:
unignore X-Junked-Because:
unignore X-SpamProbe:
set realname = "Steve Karmeinsky"
set from = "st...@gbnet.net"
#set use_from = yes
set envelope_from = yes
set smtp_url = "smtp://st...@gbnet.net@smtp.gmail.com:587/"
set smtp_pass="thisisverysecret"
set imap_user = st...@gbnet.net
set imap_pass="thisisverysecret"
set imap_list_subscribed=yes
set folder = "imaps://imap.gmail.com:993"
set spoolfile = "+INBOX"
set postponed = "+[Gmail]/Drafts"
set trash = "=[Gmail]/Bin"
#set trash = "+[Gmail]/Trash"
#set trash = "+Trash"
set ssl_force_tls = yes
set ssl_starttls = yes
set smtp_authenticators = "login"
#set record="+[Gmail]/Sent Mail"
set record=""
# Activate caching, as it can greatly improve speed
set header_cache = "~/.mutt/cache/headers"
set message_cachedir = "~/.mutt/cache/bodies"
set certificate_file=~/.mutt/certificates
set mail_check = 30
set move = no
set imap_keepalive = 900

Seems to work for me

Steve

-- 
NetTek Ltd  UK mob +44 7775 755503
UK +44 20 3432 3735  /  US +1 (650) 423 1390
social id stevekennedyuk
Euro Tech News Blog http://eurotechnews.net

Re: sample muttrc file for AOL email...

[Lester Rees]

No, Gmail no longer allows Mutt to be used for it.  Google considers it 
to be a "less secure app."  Hence, they do not allow Mutt to be used 
with it.  I have tried and have failed since Google made that change to 
Gmail.


On 4/13/23 04:31, D.J.J. Ring, Jr. wrote:
No, mutt can use Gmail because mutt has Oauth support built in. It's a 
bit complicated but you can search for instructions. That's the 
preferred way to use mutt with Gmail as the other method "app specific 
passwords" will eventually be phased out.


Please do not write me again, write to the email list.

Your questions will help many but only if they're sent to the email list.

Thank you.

David

On Thu, Apr 13, 2023, 05:22 Lester Rees  wrote:

Damn, I never thought getting help configuring Mutt for my AOL
email account would be such a big hassle.  I used to use mutt for
my Gmail accounts, but Google, as you know, stopped allowing Gmail
to be used with Mutt. Configuring Mutt to be used with my Gmail
accounts was as easy as modifying my .muttrc file, nothing else. 
Why can't someone just tell me what changes I need to make to my
.muttrc file in order to use my AOL email account with Mutt!?  I
copy & pasted the contents of my .muttrc file to this email group,
didn't I?  Shouldn't it be as easy as telling me what changes I
need to make to my .muttrc file, just like I did with my Gmail
accounts? Instead, I get a whole bunch of hassle from everyone.
Leave it human beings to make things more complicated than they
should be!!!  Damn!!!  You know, the less I have humans involved
with my life, the less stress and fewer problems I have.

On 4/13/23 04:05, D.J.J. Ring, Jr. wrote:

Yes, but you didn't tell them what it was and you posted an email
containing our back and forth which will be totally confusing to
them.

I don't think because of that you'll get a response from them,
but they are a very exceptional group, so maybe they will take
the time to figure out what's going on. I personally doubt it.

You could have taken my suggestion but maybe you have more
experience with them.

DR

On Thu, Apr 13, 2023, 05:02 Lester Rees  wrote:

Yeah, I forwarded them to mutt-users@mutt.org.

On 4/13/23 04:00, D.J.J. Ring, Jr. wrote:

Do NOT send to me, send to mutt-users@mutt.org

Again, do NOT, NOT, NOT, send email to me send to
mutt-users@mutt.org and attach both files and tell them what
they are.

Regards,

David



On Thu, Apr 13, 2023, 04:53 Lester Rees 
wrote:

Oh, I thought you needed the output that's in the .log
file from executing that command.  Okay, I'll then
attach that .log file to this email.  Sorry about the
misunderstanding.

On 4/13/23 03:47, D.J.J. Ring, Jr. wrote:

Please send to mutt-users@mutt.org email so everyone
can help you.

Unless I'm not mistaken, the command Jude gave you
produces a file. That's what is needed, not the
contents pasted into an email message.

Please send again but send the email to mutt-users@mutt.org


Kind regards,
David






On Thu, Apr 13, 2023, 02:33 Lester Rees
 wrote:

Okay, here's what's in my .muttrc file right now
with my username & password Xed out:

set from = ...@aol.com
set realname = "xxx "

#IMAP Settings
##
# activate TLS if available on the server
set ssl_starttls=yes
# always use SSL when connecting to a server
set ssl_force_tls=yes
# Don't wait to enter mailbox manually
unset imap_passive
# Automatically poll subscribed mailboxes for new
mail (new in 1.5.11)
set imap_check_subscribed

# My credentials
set smtp_url = smtp://smtp.aol.com:465/
set smtp_pass = 
set imap_user = ...@aol.com"
set imap_pass = 

# My mailboxes
set folder = imaps://imap.aol.com:993
<http://imap.aol.com:993>
set spoolfile = +INBOX


# Where to put the stuff
set header_cache = ~/.mutt/cache/headers
set message_cachedir = ~/.mutt/cache/bodies
set certificate_file = ~/.mutt/certificates

# Etc
set mail_check = 30
set move = no
set imap_keepalive = 900
set sort = threads
set editor = nano

# GnuPG bootstrap
# source ~/.mu

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

That is not accurate, Lester.

At the moment this answer is written there are currently TWO methods to use
mutt with Gmail.

First is using an "application specific password" and the second is using
the recently added "Oauth" support that is now provided in mutt.

Could someone point Lester to a tutorial on how to set up mutt using  both
of these  methods?

I suspect that Google owner of Gmail will drop "application specific
password" authorizations first, so even though both still work, that new
users just use Oauth method.

Also Lester has recently sent the list a copy of the error file that was
produced by Jude's command but to my eyes it looks all scrambled as if
Lester has his locals set to a non standard format. He also sent a copy of
his muttrc file with his username and password removed.

He is looking for help in getting mutt working.

Kind wishes,

David

Thank you,



On Thu, Apr 13, 2023, 06:26 Lester Rees  wrote:

> No, Gmail no longer allows Mutt to be used for it.  Google considers it to
> be a "less secure app."  Hence, they do not allow Mutt to be used with it.
> I have tried and have failed since Google made that change to Gmail.n
> On 4/13/23 04:31, D.J.J. Ring, Jr. wrote:
>
> No, mutt can use Gmail because mutt has Oauth support built in. It's a bit
> complicated but you can search for instructions. That's the preferred way
> to use mutt with Gmail as the other method "app specific passwords" will
> eventually be phased out.
>
> Please do not write me again, write to the email list.
>
> Your questions will help many but only if they're sent to the email list.
>
> Thank you.
>
> David
>
> On Thu, Apr 13, 2023, 05:22 Lester Rees  wrote:
>
>> Damn, I never thought getting help configuring Mutt for my AOL email
>> account would be such a big hassle.  I used to use mutt for my Gmail
>> accounts, but Google, as you know, stopped allowing Gmail to be used with
>> Mutt.  Configuring Mutt to be used with my Gmail accounts was as easy as
>> modifying my .muttrc file, nothing else.  Why can't someone just tell me
>> what changes I need to make to my .muttrc file in order to use my AOL email
>> account with Mutt!?  I copy & pasted the contents of my .muttrc file to
>> this email group, didn't I?  Shouldn't it be as easy as telling me what
>> changes I need to make to my .muttrc file, just like I did with my Gmail
>> accounts?  Instead, I get a whole bunch of hassle from everyone.   Leave it
>> human beings to make things more complicated than they should be!!!
>> Damn!!!  You know, the less I have humans involved with my life, the less
>> stress and fewer problems I have.
>> On 4/13/23 04:05, D.J.J. Ring, Jr. wrote:
>>
>> Yes, but you didn't tell them what it was and you posted an email
>> containing our back and forth which will be totally confusing to them.
>>
>> I don't think because of that you'll get a response from them, but they
>> are a very exceptional group, so maybe they will take the time to figure
>> out what's going on. I personally doubt it.
>>
>> You could have taken my suggestion but maybe you have more experience
>> with them.
>>
>> DR
>>
>> On Thu, Apr 13, 2023, 05:02 Lester Rees  wrote:
>>
>>> Yeah, I forwarded them to mutt-users@mutt.org.
>>> On 4/13/23 04:00, D.J.J. Ring, Jr. wrote:
>>>
>>> Do NOT send to me, send to mutt-users@mutt.org
>>>
>>> Again, do NOT, NOT, NOT, send email to me send to mutt-users@mutt.org
>>> and attach both files and tell them what they are.
>>>
>>> Regards,
>>>
>>> David
>>>
>>>
>>>
>>> On Thu, Apr 13, 2023, 04:53 Lester Rees  wrote:
>>>
>>>> Oh, I thought you needed the output that's in the .log file from
>>>> executing that command.  Okay, I'll then attach that .log file to this
>>>> email.  Sorry about the misunderstanding.
>>>> On 4/13/23 03:47, D.J.J. Ring, Jr. wrote:
>>>>
>>>> Please send to mutt-users@mutt.org email so everyone can help you.
>>>>
>>>> Unless I'm not mistaken, the command Jude gave you produces a file.
>>>> That's what is needed, not the contents pasted into an email message.
>>>>
>>>> Please send again but send the email to mutt-users@mutt.org
>>>>
>>>>
>>>> Kind regards,
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Apr 13, 2023, 02:33 Lester Rees  wrote:
>>>>
>>>>> Okay, here's what's in my .muttrc fi

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

No, mutt can use Gmail because mutt has Oauth support built in. It's a bit
complicated but you can search for instructions. That's the preferred way
to use mutt with Gmail as the other method "app specific passwords" will
eventually be phased out.

Please do not write me again, write to the email list.

Your questions will help many but only if they're sent to the email list.

Thank you.

David

On Thu, Apr 13, 2023, 05:22 Lester Rees  wrote:

> Damn, I never thought getting help configuring Mutt for my AOL email
> account would be such a big hassle.  I used to use mutt for my Gmail
> accounts, but Google, as you know, stopped allowing Gmail to be used with
> Mutt.  Configuring Mutt to be used with my Gmail accounts was as easy as
> modifying my .muttrc file, nothing else.  Why can't someone just tell me
> what changes I need to make to my .muttrc file in order to use my AOL email
> account with Mutt!?  I copy & pasted the contents of my .muttrc file to
> this email group, didn't I?  Shouldn't it be as easy as telling me what
> changes I need to make to my .muttrc file, just like I did with my Gmail
> accounts?  Instead, I get a whole bunch of hassle from everyone.   Leave it
> human beings to make things more complicated than they should be!!!
> Damn!!!  You know, the less I have humans involved with my life, the less
> stress and fewer problems I have.
> On 4/13/23 04:05, D.J.J. Ring, Jr. wrote:
>
> Yes, but you didn't tell them what it was and you posted an email
> containing our back and forth which will be totally confusing to them.
>
> I don't think because of that you'll get a response from them, but they
> are a very exceptional group, so maybe they will take the time to figure
> out what's going on. I personally doubt it.
>
> You could have taken my suggestion but maybe you have more experience with
> them.
>
> DR
>
> On Thu, Apr 13, 2023, 05:02 Lester Rees  wrote:
>
>> Yeah, I forwarded them to mutt-users@mutt.org.
>> On 4/13/23 04:00, D.J.J. Ring, Jr. wrote:
>>
>> Do NOT send to me, send to mutt-users@mutt.org
>>
>> Again, do NOT, NOT, NOT, send email to me send to mutt-users@mutt.org
>> and attach both files and tell them what they are.
>>
>> Regards,
>>
>> David
>>
>>
>>
>> On Thu, Apr 13, 2023, 04:53 Lester Rees  wrote:
>>
>>> Oh, I thought you needed the output that's in the .log file from
>>> executing that command.  Okay, I'll then attach that .log file to this
>>> email.  Sorry about the misunderstanding.
>>> On 4/13/23 03:47, D.J.J. Ring, Jr. wrote:
>>>
>>> Please send to mutt-users@mutt.org email so everyone can help you.
>>>
>>> Unless I'm not mistaken, the command Jude gave you produces a file.
>>> That's what is needed, not the contents pasted into an email message.
>>>
>>> Please send again but send the email to mutt-users@mutt.org
>>>
>>>
>>> Kind regards,
>>> David
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Apr 13, 2023, 02:33 Lester Rees  wrote:
>>>
>>>> Okay, here's what's in my .muttrc file right now with my username &
>>>> password Xed out:
>>>>
>>>> set from = ...@aol.com
>>>> set realname = "xxx "
>>>>
>>>> #IMAP Settings
>>>> ##
>>>> # activate TLS if available on the server
>>>> set ssl_starttls=yes
>>>> # always use SSL when connecting to a server
>>>> set ssl_force_tls=yes
>>>> # Don't wait to enter mailbox manually
>>>> unset imap_passive
>>>> # Automatically poll subscribed mailboxes for new mail (new in 1.5.11)
>>>> set imap_check_subscribed
>>>>
>>>> # My credentials
>>>> set smtp_url = smtp://smtp.aol.com:465/
>>>> set smtp_pass = 
>>>> set imap_user = ...@aol.com"
>>>> set imap_pass = 
>>>>
>>>> # My mailboxes
>>>> set folder = imaps://imap.aol.com:993
>>>> set spoolfile = +INBOX
>>>>
>>>>
>>>> # Where to put the stuff
>>>> set header_cache = ~/.mutt/cache/headers
>>>> set message_cachedir = ~/.mutt/cache/bodies
>>>> set certificate_file = ~/.mutt/certificates
>>>>
>>>> # Etc
>>>> set mail_check = 30
>>>> set move = no
>>>> set imap_keepalive = 900
>>>> set sort = threads
>>>> set editor = nano
>>>>
>>>> # GnuPG bootstrap
>>>>

Re: sample muttrc file for AOL email...

[Lester Rees]

Damn, I never thought getting help configuring Mutt for my AOL email 
account would be such a big hassle.  I used to use mutt for my Gmail 
accounts, but Google, as you know, stopped allowing Gmail to be used 
with Mutt.  Configuring Mutt to be used with my Gmail accounts was as 
easy as modifying my .muttrc file, nothing else. Why can't someone just 
tell me what changes I need to make to my .muttrc file in order to use 
my AOL email account with Mutt!?  I copy & pasted the contents of my 
.muttrc file to this email group, didn't I?  Shouldn't it be as easy as 
telling me what changes I need to make to my .muttrc file, just like I 
did with my Gmail accounts?  Instead, I get a whole bunch of hassle from 
everyone.   Leave it human beings to make things more complicated than 
they should be!!!  Damn!!!  You know, the less I have humans involved 
with my life, the less stress and fewer problems I have.


On 4/13/23 04:05, D.J.J. Ring, Jr. wrote:
Yes, but you didn't tell them what it was and you posted an email 
containing our back and forth which will be totally confusing to them.


I don't think because of that you'll get a response from them, but 
they are a very exceptional group, so maybe they will take the time to 
figure out what's going on. I personally doubt it.


You could have taken my suggestion but maybe you have more experience 
with them.


DR

On Thu, Apr 13, 2023, 05:02 Lester Rees  wrote:

Yeah, I forwarded them to mutt-users@mutt.org.

On 4/13/23 04:00, D.J.J. Ring, Jr. wrote:

Do NOT send to me, send to mutt-users@mutt.org

Again, do NOT, NOT, NOT, send email to me send to
mutt-users@mutt.org and attach both files and tell them what they
are.

Regards,

David



On Thu, Apr 13, 2023, 04:53 Lester Rees  wrote:

Oh, I thought you needed the output that's in the .log file
from executing that command.  Okay, I'll then attach that
.log file to this email.  Sorry about the misunderstanding.

On 4/13/23 03:47, D.J.J. Ring, Jr. wrote:

Please send to mutt-users@mutt.org email so everyone can
help you.

Unless I'm not mistaken, the command Jude gave you produces
a file. That's what is needed, not the contents pasted into
an email message.

Please send again but send the email to mutt-users@mutt.org


Kind regards,
David






On Thu, Apr 13, 2023, 02:33 Lester Rees 
wrote:

Okay, here's what's in my .muttrc file right now with my
username & password Xed out:

set from = ...@aol.com
set realname = "xxx "

#IMAP Settings
##
# activate TLS if available on the server
set ssl_starttls=yes
# always use SSL when connecting to a server
set ssl_force_tls=yes
# Don't wait to enter mailbox manually
unset imap_passive
# Automatically poll subscribed mailboxes for new mail
(new in 1.5.11)
set imap_check_subscribed

# My credentials
set smtp_url = smtp://smtp.aol.com:465/
set smtp_pass = 
set imap_user = ...@aol.com"
set imap_pass = 

# My mailboxes
set folder = imaps://imap.aol.com:993
<http://imap.aol.com:993>
set spoolfile = +INBOX


# Where to put the stuff
set header_cache = ~/.mutt/cache/headers
set message_cachedir = ~/.mutt/cache/bodies
set certificate_file = ~/.mutt/certificates

# Etc
set mail_check = 30
set move = no
set imap_keepalive = 900
set sort = threads
set editor = nano

# GnuPG bootstrap
# source ~/.mutt/gpg.rc

Now, here's the output from that mutt.log file after
running that command given to me by Jude DaShiell:


^[[?1049h^[[22;0;0t^[[1;24r^[(B^[[m^[[4l^[[?7h^[[39;49m^[[?1h^[=^[[?1034h^[[39;49m^[[37m^[
[40m^[[H^[[2J^[[39;49m^[[24d^[[K^[[24;1H^[[?1049l^[[23;0;0t
^[[?1l^[>^[[39;49m^[[K^[[24;1H^[[?1049l^[[23;0;0t

^[[?1l^[>^[[?1049h^[[22;0;0t^[[1;24r^[[39;49m^[]104^G^[(B^[[m^[[4l^[[?7h^[[39;49m^[[37m^[[

40m^[[37m^[[40m^[[H^[[2J^[[K^[[2d^[[K^[[3d^[[K^[[4d^[[K^[[5d^[[K^[[6d^[[K^[[7d^[[K^[[8d^[[

K^[[9d^[[K^[[10d^[[K^[[11d^[[K^[[12d^[[K^[[13d^[[K^[[14d^[[K^[[15d^[[K^[[16d^[[K^[[17d^[[K

^[[18d^[[K^[[19d^[[K^[[20d^[[K^[[21d^[[K^[[22d^[[K^[[23d^[[K^[[24d^[(B^[[m^[[39;49m^[[37m
^[[40mReading imaps://imap.aol.com:993/INBOX..

<http://imap.aol.com:993/INBOX..>.^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[4
0m
Looking up
imap.aol.com...^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[4

Fwd: sample muttrc file for AOL email...

[Lester Rees]

 Forwarded Message 
Subject:Re: sample muttrc file for AOL email...
Date:   Thu, 13 Apr 2023 03:53:48 -0500
From:   Lester Rees 
To: D.J.J. Ring, Jr. 



Oh, I thought you needed the output that's in the .log file from 
executing that command.  Okay, I'll then attach that .log file to this 
email.  Sorry about the misunderstanding.


On 4/13/23 03:47, D.J.J. Ring, Jr. wrote:

Please send to mutt-users@mutt.org email so everyone can help you.

Unless I'm not mistaken, the command Jude gave you produces a file. 
That's what is needed, not the contents pasted into an email message.


Please send again but send the email to mutt-users@mutt.org


Kind regards,
David






On Thu, Apr 13, 2023, 02:33 Lester Rees  wrote:

Okay, here's what's in my .muttrc file right now with my username
& password Xed out:

set from = ...@aol.com
set realname = "xxx "

#IMAP Settings
##
# activate TLS if available on the server
set ssl_starttls=yes
# always use SSL when connecting to a server
set ssl_force_tls=yes
# Don't wait to enter mailbox manually
unset imap_passive
# Automatically poll subscribed mailboxes for new mail (new in 1.5.11)
set imap_check_subscribed

# My credentials
set smtp_url = smtp://smtp.aol.com:465/
set smtp_pass = 
set imap_user = ...@aol.com"
set imap_pass = 

# My mailboxes
set folder = imaps://imap.aol.com:993 <http://imap.aol.com:993>
set spoolfile = +INBOX


# Where to put the stuff
set header_cache = ~/.mutt/cache/headers
set message_cachedir = ~/.mutt/cache/bodies
set certificate_file = ~/.mutt/certificates

# Etc
set mail_check = 30
set move = no
set imap_keepalive = 900
set sort = threads
set editor = nano

# GnuPG bootstrap
# source ~/.mutt/gpg.rc

Now, here's the output from that mutt.log file after running that
command given to me by Jude DaShiell:


^[[?1049h^[[22;0;0t^[[1;24r^[(B^[[m^[[4l^[[?7h^[[39;49m^[[?1h^[=^[[?1034h^[[39;49m^[[37m^[
[40m^[[H^[[2J^[[39;49m^[[24d^[[K^[[24;1H^[[?1049l^[[23;0;0t
^[[?1l^[>^[[39;49m^[[K^[[24;1H^[[?1049l^[[23;0;0t

^[[?1l^[>^[[?1049h^[[22;0;0t^[[1;24r^[[39;49m^[]104^G^[(B^[[m^[[4l^[[?7h^[[39;49m^[[37m^[[

40m^[[37m^[[40m^[[H^[[2J^[[K^[[2d^[[K^[[3d^[[K^[[4d^[[K^[[5d^[[K^[[6d^[[K^[[7d^[[K^[[8d^[[

K^[[9d^[[K^[[10d^[[K^[[11d^[[K^[[12d^[[K^[[13d^[[K^[[14d^[[K^[[15d^[[K^[[16d^[[K^[[17d^[[K

^[[18d^[[K^[[19d^[[K^[[20d^[[K^[[21d^[[K^[[22d^[[K^[[23d^[[K^[[24d^[(B^[[m^[[39;49m^[[37m
^[[40mReading imaps://imap.aol.com:993/INBOX..

<http://imap.aol.com:993/INBOX..>.^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[4
0m
Looking up
imap.aol.com...^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[40m
Connecting to imap.aol.com...
SSL/TLS connection using TLS1.3 (ECDHE-RSA/AES-256-GCM/AEAD)
Authenticating (PLAIN)...^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[40m
Logging in...^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[40m^G
Login failed.^[[?25l^[[H^[(B^[[0;1m^[[32m^[[44mq:Quit d:Del 
u:Undel  s:Save  m:Mail  r:R
eply  g:Group  ?:Help^[[K
^[[23d---Mutt: (no mailbox)
[Msgs:0]---(threads/date)-(all)---^[[2
;80H^[(B^[[m^[[39;49m^[[37m^[[40m^[[?1h^[=

If you ask me, it looks just like a bunch of gibbereish.


On 4/13/23 00:44, D.J.J. Ring, Jr. wrote:

What we need are the errors.

Use the command that Jude posted, that will tell us exactly what
is wrong.

The muttrc file is not of much use, unless you want to give us
your email password to try mutt and find out what the problem is.

Best wishes,

David


On Wed, Apr 12, 2023, 18:10 Bush Nest  wrote:

I'm at work right now, so I won't be able to copy & paste
what I have in my .muttrc file at this point.  Until I get
off of work.  I'll do that then.
On Apr 12, 2023, at 11:32 AM, "D.J.J. Ring, Jr."
 wrote:

I believe Storm Dragon's fleacollar supports AOL.

https://git.2mb.codes/~lilmike/fleacollar
script URL
https://git.2mb.codes/~lilmike/fleacollar/blob/master/fleacollar.sh


Use wget to download this.

Then chmod fleacollar.sh to be executable and run it and
give all answers, including the password and gpg
questions, it won't make a gpg for your email itself, it
just protects your passwords on your computer.

wget
https://git.2mb.codes/~lilmike/fleacollar/blob/master/fleacollar.sh


Best wishes,
David


On Wed, Apr 12, 2023, 11:44 Lester Rees <
bushn...@gmail.com> wrote:

Does anyone, by any chance, happen to have a sample
.muttrc file that I
could use for AOL ema

Re: sample muttrc file for AOL email...

[Jude DaShiell]

When linux or unix software will produce errors in this case a command
like:
mutt 2>&1|tee mutt.log
will produce mutt.log where all output from the command including errors
will be captured.
If more than a single run is needed:
mutt 2>&1|tee -a mutt.log
will append output to mutt.log.
The 2>&1 redirects stderr to stdout so tee can catch it for you.
Cleaner than running script since ansi codes don't get included.
For graphics software where ansi is both desired and important your best
bet is to use script rather than tee to catch output input and errors.


-- Jude  "There are four boxes to be used in
defense of liberty: soap, ballot, jury, and ammo. Please use in that
order." Ed Howdershelt 1940.

On Wed, 12 Apr 2023, D.J.J. Ring, Jr. wrote:

> On Wed, Apr 12, 2023 at 2:11 PM Lester Rees  wrote:
>
> > Well, I need to take a little nap right now b4 I go to work this
> > afternoon.  Talk atcha later.
> >
> Hello Lester,
>
> Making mutt work isn't just a matter of a configuration file, there are
> other things like making directories which must be done.  You will either
> have to do this manually, or use a script.
> Otherwise, mutt will fail. As mentioned, mutt has imap support but it needs
> to be manually configured by you, it's not as simple as just a muttrc file,
> there are a few steps to getting it to work.
>
> If you don't want to use fleacollar.sh script, here are some good
> instructions on how to set up mutt.https://wiki.archlinux.org/title/Mutt
>
> Just ignore that it's for Arch Linux - the instructions are generic, but
> you have to follow all the steps and instructions or mutt just will not
> work.  It would have helped greatly if you had supplied the errors instead
> of saying simply "it doesn't work" - usually the errors will point to the
> misconfiguration and the misconfiguration can be fixed.
>
> You might look into offlineimap or isync to download your imap mail from
> aol.  They are both python programs.
>
> isync https://isync.sourceforge.io/
> offlineimap https://www.offlineimap.org/doc/installation.html
>
> If you're running Linux, your distro will have these to be installed.
>
> David
>

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

On Wed, Apr 12, 2023 at 2:11 PM Lester Rees  wrote:

> Well, I need to take a little nap right now b4 I go to work this
> afternoon.  Talk atcha later.
>
Hello Lester,

Making mutt work isn't just a matter of a configuration file, there are
other things like making directories which must be done.  You will either
have to do this manually, or use a script.
Otherwise, mutt will fail. As mentioned, mutt has imap support but it needs
to be manually configured by you, it's not as simple as just a muttrc file,
there are a few steps to getting it to work.

If you don't want to use fleacollar.sh script, here are some good
instructions on how to set up mutt.https://wiki.archlinux.org/title/Mutt

Just ignore that it's for Arch Linux - the instructions are generic, but
you have to follow all the steps and instructions or mutt just will not
work.  It would have helped greatly if you had supplied the errors instead
of saying simply "it doesn't work" - usually the errors will point to the
misconfiguration and the misconfiguration can be fixed.

You might look into offlineimap or isync to download your imap mail from
aol.  They are both python programs.

isync https://isync.sourceforge.io/
offlineimap https://www.offlineimap.org/doc/installation.html

If you're running Linux, your distro will have these to be installed.

David

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

On Wed, Apr 12, 2023 at 1:48 PM Lester Rees  wrote:

> Just give me a sample .muttrc file and I'll just plug in the
> username,password, and email address.  e.g. .imap.aol.com.
> It's not really that hard to do.  Boy, you're just trying hard to push this
> bash script on me, aren't you!?  It makes me kinda suspicious!
>
Lester,

Send the errors you're having with mutt to the list, maybe we can help you.

I'm not "pushing" the fleacollar scrip, but it works nicely and it's all
set up to work with AOL.

David

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

On Wed, Apr 12, 2023 at 12:40 PM Lester Rees  wrote:

> The thing doesn't even work.  Anyways, I don't see why any sort of
> app/bash script should be necessary.  All I need is a simple example
> .muttrc file to use to be able to configure Mutt to use an AOL email
> account, nothing else.
>
The fleacollar script will work. Script URL
https://git.2mb.codes/~lilmike/fleacollar/blob/master/fleacollar.sh

OK then otherwise, just follow the CONFIG settings from the mutt menu in
mutt.  It will do the configuration for you, just supply the needed
information.

The script is easier, and it works for me and many others.

If it doesn't work, send a bug report to Storm Dragon <
storm_dra...@linux-a11y.org>

Regards,
David

Re: sample muttrc file for AOL email...

[D.J.J. Ring, Jr.]

I believe Storm Dragon's fleacollar supports AOL.

https://git.2mb.codes/~lilmike/fleacollar
script URL
https://git.2mb.codes/~lilmike/fleacollar/blob/master/fleacollar.sh

Use wget to download this.

Then chmod fleacollar.sh to be executable and run it and give all answers,
including the password and gpg questions, it won't make a gpg for your
email itself, it just protects your passwords on your computer.

wget https://git.2mb.codes/~lilmike/fleacollar/blob/master/fleacollar.sh

Best wishes,
David


On Wed, Apr 12, 2023, 11:44 Lester Rees  wrote:

> Does anyone, by any chance, happen to have a sample .muttrc file that I
> could use for AOL email?  And no, I do not want a conversation or a
> lecture, just a sample .muttrc file that I could use for AOL email.
> Thank you very much!  
>

sample muttrc file for AOL email...

[Lester Rees]

Does anyone, by any chance, happen to have a sample .muttrc file that I 
could use for AOL email?  And no, I do not want a conversation or a 
lecture, just a sample .muttrc file that I could use for AOL email.  
Thank you very much!  

Re: test shell env in .muttrc

[Jon LaBadie]

On Mon, Dec 05, 2022 at 06:18:05PM -0800, Will Yardley wrote:

On Mon, Dec 05, 2022 at 08:26:16PM -0500, Jon LaBadie wrote:


Perhaps I've overlooked the facility.  Is there a way to test the
shell environment in .muttrc?  Basically an "if" statement.

I enter mutt in several ways (direct, aliases, shell scripts,
functions, etc) and from several devices.  My smart phone needs a
different color scheme than the other devices.


I think there may be an internal way as well, but one option would be to
set an env var (e.g., TYPE) depending on the type of session, and then
do something like (untested):

source ~/.mutt/colors.${TYPE:-default}


Nice suggestion Will, tnx.

I chose XDG_SESSION_TYPE (automatically set: so far to either x11 or 
tty) and it seems to be doing what I was looking for.


--
Jon H. LaBadie j...@labadie.us
 154 Milkweed Dr (540) 868-8052 (H)
 Lake Frederick, VA 22630(703) 935-6720 (M)

Re: test shell env in .muttrc

[Kevin J. McCarthy]

On Mon, Dec 05, 2022 at 06:18:05PM -0800, Will Yardley wrote:

I think there may be an internal way as well, but one option would be to
set an env var (e.g., TYPE) depending on the type of session, and then
do something like (untested):

source ~/.mutt/colors.${TYPE:-default}


See also  for some examples of 
MuttLisp.  For example:


source (concat "~/.mutt/colors." (or $TYPE default))

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: test shell env in .muttrc

[Will Yardley]

On Mon, Dec 05, 2022 at 08:26:16PM -0500, Jon LaBadie wrote:

> Perhaps I've overlooked the facility.  Is there a way to test the
> shell environment in .muttrc?  Basically an "if" statement.
> 
> I enter mutt in several ways (direct, aliases, shell scripts,
> functions, etc) and from several devices.  My smart phone needs a
> different color scheme than the other devices.

I think there may be an internal way as well, but one option would be to
set an env var (e.g., TYPE) depending on the type of session, and then
do something like (untested):

source ~/.mutt/colors.${TYPE:-default}

Or you could key it on hostname, similar to this example:
https://lwn.net/Articles/587348/

You can also source a shell script to do some stuff
https://mutt-users.mutt.narkive.com/WovuIH31/conditionally-include-a-file-in-the-configuration

there may be some patches to support more within the config itself.
neomutt (which I don't use personally) has some support via this hook:
https://neomutt.org/feature/ifdef

test shell env in .muttrc

[Jon LaBadie]

Perhaps I've overlooked the facility.  Is there a way to
test the shell environment in .muttrc?  Basically an "if"
statement.

I enter mutt in several ways (direct, aliases, shell scripts,
functions, etc) and from several devices.  My smart phone
needs a different color scheme than the other devices.

It is easy enough to use a macro I have to rotate among
several color schemes, but I would prefer to automate it
on entry if possible.

Jon

--
Jon H. LaBadie j...@labadie.us
 154 Milkweed Dr (540) 868-8052 (H)
 Lake Frederick, VA 22630(703) 935-6720 (M)

Re: muttrc for gmx.com emails

[Kevin J. McCarthy]

On Sat, Aug 06, 2022 at 12:00:19PM -0400, D.J.J. Ring, Jr. wrote:

On Sat, Aug 6, 2022 at 8:05 AM José María Mateos  wrote:

I don't use `record`, but I think you need either a + or a = sign in 
front of the mailbox name.


set record="+Sent"


If I put the + as you suggest, mutt wants to save a copy to 
/home/username/Mail/Sent but I want it to send a copy to the IMAP 
folder which I can see is named "Sent" by pressing c in mutt.


'=' or '+' will substitute the value of $folder at the beginning of 
$record.


However, $folder must be set before $record, in order for it to work 
properly.  Otherwise the default value of $folder, which is "~/Mail", 
will be used instead.


It sounds like that might be the problem in this case.

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: muttrc for gmx.com emails

[D.J.J. Ring, Jr.]

On Sat, Aug 6, 2022 at 8:05 AM José María Mateos  wrote:

> I don't use `record`, but I think you need either a + or a = sign in
> front of the mailbox name.
>
> set record="+Sent"
>
>
> José María (Chema) Mateos || https://rinzewind.org

If I put the + as you suggest, mutt wants to save a copy to
/home/username/Mail/Sent but I want it to send a copy to the IMAP
folder which I can see is named "Sent" by pressing c in mutt.

Maybe I should be using something different than "set record"?

Thanks,
David

Re: muttrc for gmx.com emails

[José María Mateos]

On Sat, Aug 06, 2022 at 01:27:05AM -0400, D.J.J. Ring, Jr. wrote:

Those worked, but I still have a problem saving my mail.

This works without an error but it still doesn't save my mail>

set record="Sent"


I don't use `record`, but I think you need either a + or a = sign in 
front of the mailbox name.


set record="+Sent"

Cheers,

--
José María (Chema) Mateos || https://rinzewind.org

Re: muttrc for gmx.com emails

[D.J.J. Ring, Jr.]

Those worked, but I still have a problem saving my mail.

This works without an error but it still doesn't save my mail>

set record="Sent"

That's the name of the folder I can see by pressing c to change folders.

Regards,
David

On Sat, Aug 6, 2022 at 12:59 AM Daniel Tameling
 wrote:
>
> Hi,
>
> > Also I haven't figured out how to save a copy of my sent meil to my
> > gmx sent filder.
>
> I also had this problem when adapting my mutt configuration from gmail to 
> gmx.de.
> (I download the mail with mbsync instead of using imap in mutt, but this 
> should still apply)
> I had to add this to my configuration:
>
> set copy="yes"
> set record="+Gesendet"
>
> You just need to find out, what your sent folder is called and use that in 
> record.
>
> btw: at least the German gmx uses a flat folder structure. So I don't need 
> the [GMX]/ you have in your config.
>
> > I can receive gmx.com mail, I can send gmx.com mail, but when starting
> > mutt, I have to change folders to INBOX.
>
> Did you try
>
> set spoolfile=+INBOX
>
> --
> Best,
> Daniel

Re: muttrc for gmx.com emails

[Daniel Tameling]

Hi,

> Also I haven't figured out how to save a copy of my sent meil to my
> gmx sent filder.

I also had this problem when adapting my mutt configuration from gmail to 
gmx.de.
(I download the mail with mbsync instead of using imap in mutt, but this should 
still apply)
I had to add this to my configuration:

set copy="yes"
set record="+Gesendet"

You just need to find out, what your sent folder is called and use that in 
record.

btw: at least the German gmx uses a flat folder structure. So I don't need the 
[GMX]/ you have in your config. 

> I can receive gmx.com mail, I can send gmx.com mail, but when starting
> mutt, I have to change folders to INBOX.

Did you try

set spoolfile=+INBOX

-- 
Best,
Daniel

muttrc for gmx.com emails

[D.J.J. Ring, Jr.]

Hello,

Some of the less talented visually impaired users were wondering if
anyone has come up with a muttrc file that works with a tmpdir inside
~/.mutt?

I attach what I've come up with so far.

I can receive gmx.com mail, I can send gmx.com mail, but when starting
mutt, I have to change folders to INBOX.

Also I haven't figured out how to save a copy of my sent meil to my
gmx sent filder.

Below my signature is the pasted file, it still is dirty from having
other entries left over from gmail, but these have been commented out
with an # at the beginning of the line.

The file is also attached.

Regards,

David Ring

 === muttrc =

### ~/.mutt/muttrc

## Change the following lines to match your GMX account details
## For a bit more information and password encryption instructions go
to the Mutt set-up article
## If you must use pop change imap to pop, change port numbers, etc.
set imap_user = "usern...@gmx.com"
set imap_pass = "MYGMXEMAILPASSWORD"
set smtp_url = "smtp://usern...@gmx.com:mygmxemailpassw...@mail.gmx.com:587/"
set ssl_force_tls   = yes
set ssl_starttls= yes
set smtp_pass = "MYGMXEMAILPASSWORD"
set from = "usern...@gmx.com"
set realname = "MY REAL NAME"
## Comment the next line or change to no to put sig below quoted message(s)
set sig_on_top = yes
set signature="~/.mutt/sig"

# Change the following line if you prefer a different editor.
set editor = "nano"
# This line changes the spelling checker to aspell from less modern ispell
# set ispell="aspell -e -c"

## Basic config, you can leave this as is in most cases
# Not sure if timeout and keepalive value tweaking will help
intermittent connection issues
# (time values are in seconds)
set wait_key = no
set folder = "imaps://imap.gmx.com:993"
set spoolfile = "+GMX"
set imap_check_subscribed
set hostname = gmx.com
set mail_check = 150
set beep_new
set connect_timeout = 25
set timeout = 300
# Keep IMAP connection alive by polling intermittently
set imap_keepalive = 180
# Allow Mutt to open new imap connection automatically
unset imap_passive
set postponed = "+[GMX]/Drafts"
# set postpone=ask-yes
#set record = "+[gmx]/Sent Mail"
set header_cache=~/.mutt/cache/headers
set message_cachedir=~/.mutt/cache/bodies

## You may need to create your tmpdir in some situations.
set tmpdir = ~/.mutt/tmpdir
set certificate_file=~/.mutt/certificates
set alias_file=~/.mutt/aliases
set move = no
set honor_followup_to = ask-yes

## Date Format ##
set date_format="%d %b %R"

## Index Sorting ##
#set index_format="%4C %Z %{%b %d %t} %-15.15L (%4l) %s"
set index_format="%4C %Z %{%b %d %H:%M} %-15.15L (%?l?%4l&%4c?) %s"

## Automatically includes quote of the original msg in replies
# set include

## If you want to be asked whether to include quoted message(s)
 set include=ask-yes

## Asks whether to forward non plain text mime types attached as they
came or to convert to inline plain text
set mime_forward = ask-no
set sort = 'threads'
set sort_aux = 'reverse-last-date-received'

## The next two are set oposite of default if uncommented. *(needs more study)
#set strict_threads = yes
#set sort_re = no
set auto_tag = yes

## Reminds you of missing subject or empty body with msg
sent as default
set abort_nosubject = ask-no
set abort_unmodified = ask-no
ignore "Authentication-Results:"
ignore "DomainKey-Signature:"
ignore "DKIM-Signature:"
hdr_order Date From To Cc Bcc
set attribution = "\n  %n wrote:\n%d\n"

## Character or string to appear at the start of quoted lines in replys
set indent_string = "> "
set forward_format = "[FWD: %a] %s"
set mailcap_path= ~/.mutt/mailcap
#auto_view text/html
#set implicit_autoview = yes

##  Uncomment below to read plain text instead of html when both formats exist.
#alternative_order text/plain text/html *
set folder_format = "%2C %f %8s %d %t %F %-8.8u %N %d"

## Scrolls one line at a time, i.e. smoothly scrolls, instead of only
moving up or down by whole pages, screen-fulls if you will
set menu_scroll = yes

## Read and write progress messages update frequency: The value is a
number of messages.
set read_inc = 20
set write_inc = 10

## Some useful extra key bindings
## Improve tab completion: complete address aliases with tab...
bind attach view-mailcap
#bind editor  complete# default Mutt setting
# bind editor ^T complete-query
# unset query_command   # default Mutt setting
bind editor  noop

## Optimize copy and save to show mailbox list without prompting
## Use numbers to jump directly to a mailbox, i.e. skip arrowing
macro index,pager C "?" "copy a
message to a mailbox"
macro index,pager s "?" "move a
message to a mailbox"

##This configuration provides enc

Is there any access to header values in muttrc file?

[Chris Green]

Is there any way to 'see' header values from send-hook?

I want to be able to manipulate the To: address in an external program
so I want to do something like:-

send-hook 'barges.org/discussion-forum' 'source myscript.sh $to|'

I.e. I want the To: address fed into myscript.sh.


-- 
Chris Green

Can one access aliases (the alias 'name' that is) in muttrc file?

[Chris Green]

Is there any way to get at the alias 'name' in muttrc?

I'm trying to use send-hook (or send2-hook, or anything really) in
muttrc to change actions/configuration based on the alias which has
been expanded to the destination address.

I have a number of different aliases which expand to the same
destination and I want to do different things according to which alias
was used to send the E-Mail.

I.e. I have aliases (generated dynamically, but that doesn't matter
really) as follows:-

alias dbablife fo...@barges.org
alias dbabarges fo...@barges.org
alias dbabrexit fo...@barges.org
alias dbaeur fo...@barges.org
alias dbagbi fo...@barges.org
alias dbaeutravel fo...@barges.org
alias dbaforum fo...@barges.org

I want to to be able to change things in the message according to the
alias that was used.  I can't add anything extra to the
fo...@barges.org because that's used to match some header information
in received messages.

-- 
Chris Green

Re: muttrc file for aol.com email?

[D.J.J. Ring, Jr.]

I probably should have made note of where I heard it, but I don't go
looking for trouble like in places like reddit, so it likely was a good
source, but I didn't bookmark it, instead, I came here to get one of my
other accounts working with mutt. Maybe they were wrong, I'm not panicking,
I'm just trying to get a backup plan.  There's lots of us who because of
vision problems need text only keyboard driven email.

If we could only get a text browser that would everywhere, life would be
great.

Best wishes,
David

On Mon, Dec 20, 2021, 22:45 John Hawkinson  wrote:

> On Mon, Dec 20, 2021 at 4:33 AM D.J.J. Ring, Jr.  wrote:
> > I just heard gmail was going to become not compatible with mutt. How
> dare they?
>
> This is a prett ystrong claim, and it is going to cause a lot of
> consternation and panic, whether it turns out to be true or mistaken.
>
> Can you please share some more information so we can figure out how to
> address it and how concerned to be? Is there supporting information?
> Is it a rumor? If rumor, what's the provenance? Heard from a
> friend-of-a-friend-of-a-friend? From a reliable source you can
> explain, etc?
>
> Thank you.
>
> --
> jh...@alum.mit.edu
> John Hawkinson
>

Re: muttrc file for aol.com email?

[John Hawkinson]

On Mon, Dec 20, 2021 at 4:33 AM D.J.J. Ring, Jr.  wrote:
> I just heard gmail was going to become not compatible with mutt. How dare 
> they?

This is a prett ystrong claim, and it is going to cause a lot of
consternation and panic, whether it turns out to be true or mistaken.

Can you please share some more information so we can figure out how to
address it and how concerned to be? Is there supporting information?
Is it a rumor? If rumor, what's the provenance? Heard from a
friend-of-a-friend-of-a-friend? From a reliable source you can
explain, etc?

Thank you.

--
jh...@alum.mit.edu
John Hawkinson

Re: muttrc file for aol.com email?

[Greg Donoghue via Mutt-users]

On Mon, Dec 20, 2021 at 04:32:41AM -0500, D.J.J. Ring, Jr. wrote:
>That's the information I needed. I would have never guessed at
>"export.imap.aol.com[1]".
>Also does mutt need an "app password"?
>I just heard gmail was going to become not compatible with mutt. How
>dare they?
>Thanks,
>David

I needed the *app password* to get mine working.

I did not need 'export'.

 set spoolfile =  "imaps://imap.aol.com:993/INBOX"
 set folder = "imaps://imap.aol.com:993"

-- 
Greg Donoghue
gregdonog...@aim.com

Re: muttrc file for aol.com email?

[D.J.J. Ring, Jr.]

That's the information I needed. I would have never guessed at "
export.imap.aol.com".

Also does mutt need an "app password"?

I just heard gmail was going to become not compatible with mutt. How dare
they?

Thanks,
David

On Mon, Dec 20, 2021, 04:25 Greg Donoghue via Mutt-users <
mutt-users@mutt.org> wrote:

> On Sun, Dec 19, 2021 at 07:54:47PM -0500, D.J.J. Ring, Jr. wrote:
> >Does anyone have a muttrc file that works for aol.com[1]?
> >I'm anticipating the big changes with gmail that will break mutt.
> >Best to all,
> >David
> >
> Incoming Mail (IMAP) Server
> • Server - export.imap.aol.com
> • Port - 993
> • Requires SSL - Yes
>
> Outgoing Mail (SMTP) Server
> • Server - smtp.aol.com
> • Port - 465
> • Requires SSL - Yes
> • Requires authentication - Yes
>
> Your login info
>
> If you're using an older email app, *generate an app password* and use
> that for your account password.
>
> https://help.aol.com/articles/Create-and-manage-app-password
>
> • Email address - Your full email address (n...@domain.com)
> • Password - Your account's password
> • Requires authentication - Yes
>
> Hope this will get you started.
> --
> Greg Donoghue
> gregdonog...@aim.com
>

Re: muttrc file for aol.com email?

[Greg Donoghue via Mutt-users]

On Sun, Dec 19, 2021 at 07:54:47PM -0500, D.J.J. Ring, Jr. wrote:
>Does anyone have a muttrc file that works for aol.com[1]?
>I'm anticipating the big changes with gmail that will break mutt.
>Best to all,
>David
> 
Incoming Mail (IMAP) Server
• Server - export.imap.aol.com
• Port - 993
• Requires SSL - Yes

Outgoing Mail (SMTP) Server
• Server - smtp.aol.com
• Port - 465
• Requires SSL - Yes
• Requires authentication - Yes

Your login info

If you're using an older email app, *generate an app password* and use 
that for your account password.

https://help.aol.com/articles/Create-and-manage-app-password

• Email address - Your full email address (n...@domain.com)
• Password - Your account's password
• Requires authentication - Yes

Hope this will get you started.
-- 
Greg Donoghue
gregdonog...@aim.com

Re: muttrc file for aol.com email?

[Hokan]

On Sun, Dec 19, 2021 at 07:54:47PM -0500, D.J.J. Ring, Jr. wrote:
> 
> I'm anticipating the big changes with gmail that will break mutt.

Wot?

You mean the optional "allowlisted IMAP clients"?  Do you expect your
GSuite admins will restrict clients and not include Mutt?

-- 
Hokan
Bicyclist
Sysadmin


signature.asc
Description: PGP signature

muttrc file for aol.com email?

[D.J.J. Ring, Jr.]

Does anyone have a muttrc file that works for aol.com?

I'm anticipating the big changes with gmail that will break mutt.

Best to all,

David

Re: Location of sample muttrc and mailcap files, and correct names of Gmail folders

[boB Stepp]

On 21/02/12 06:50PM, David J. J. Ring, Jr. wrote:


Also and this seems to be the initial cause of my calamity, what is the correct
names of the imap folders in gmail?   Some of my muttrc files have GMail others 
have Gmail with only the first letter capitalized.


I just got through doing a major overhaul of my Gmail.  Gmail's system labels
are as follows:

[Gmail]
[Gmail]/All Mail
[Gmail]/Drafts
[Gmail]/Sent Mail
[Gmail]/Spam
[Gmail]/Starred
[Gmail]/Trash

And of course +INBOX refers to [Gmail]/Inbox.

There are other reserved labels in Gmail such as Snoozed, Important, Chats,
etc., but if those are of interest you can "Google" for them.  ~(:>))

The one gotcha from my perspective is that Gmail uses "labels" *not* "folders"
to structure its mail.  So any particular email may have multiple labels.  If
your intention is to map labels to folders this may cause you grief if you are
not careful.

HTH!

--
Wishing you only the best,

boB Stepp

Re: Location of sample muttrc and mailcap files, and correct names of Gmail folders

[David Lowry-Duda]

Hello - 

> Where are sample files for muttrc located?  Where are sample mailcap 
> located?

On my machine, sample muttrc files are located in 
/usr/share/doc/mutt/examples. There are a couple of muttrc files and a 
sample mailcap file there.

If you have the source, then there are samples of both in the contrib 
directory, and a longer sample muttrc in the doc directory.

> Also and this seems to be the initial cause of my calamity, what is 
> the correct names of the imap folders in gmail?   Some of my muttrc 
> files have GMail others have Gmail with only the first letter 
> capitalized.

I believe they are of the form "+[Gmail]/Trash", for example. But I 
think you might get by with just setting the spoolfile to be "+INBOX".

Good luck!

-- 
David Lowry-Duda  

Location of sample muttrc and mailcap files, and correct names of Gmail folders

[David J. J. Ring, Jr.]

Hello Mutt-Users,

Today for some reason, mutt stopped working, it needed a control-c to interrupt 
then continue, 
I finally got it working, I don't remember how, but probably I had an error
in my muttrc file.

Where are sample files for muttrc located?  Where are sample mailcap located?

Also and this seems to be the initial cause of my calamity, what is the correct
names of the imap folders in gmail?   Some of my muttrc files have GMail others 
have Gmail with only the first letter capitalized.

This was causing a problem because I started having all sorts of extra folders 
appear in my gmail imap account with names like Gmail and GMail, I cannot give 
you specifics because I have finally eliminated them all.

I use settings in my muttrc to retreive my imap because I had tried 
offline-imap or some sort of program
and I lost a bunch of email doing so - or so I think.  So I'm scared of doing 
that again.

Best wishes to all,

David Ring



signature.asc
Description: PGP signature

Re: Syntax for creating Muttrc.

[Sam Kuper]

On Thu, Oct 01, 2020 at 10:01:56PM -0700, Will Yardley wrote:
> On Thu, Oct 01, 2020 at 09:58:17PM -0700, M.R.P. zensky wrote:
>> Can someone tell me the syntax for creating a Muttrc file on linux? I
>> have installed it on linux and am trying to understand how to
>> configure it.
> 
> man 5 muttrc

This.

If anything in there is confusing, then fall back to the over-arching
Mutt manual: http://www.mutt.org/doc/manual/ .

If anything in *there* is confusing, then fall back to the supplementary
documentation written or sanctioned by Mutt developers/maintainers,
which includes an FAQ: https://gitlab.com/muttmua/mutt/-/wikis/home .


> and / or looking at the sample [Muttrc] that should ship with Mutt
> could be a start.

Direct link:

https://gitlab.com/muttmua/mutt/-/raw/master/contrib/sample.muttrc-starter


> There's also some info at:
> https://wiki.archlinux.org/index.php/Mutt#Configuration
> 
> Or search online to find example configs to steal^Wborrow from.

Good starting points:

https://gitlab.com/muttmua/mutt/-/wikis/ConfigList

https://www.fefe.de/muttfaq/faq.html#patient


-- 
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?

()  ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\  file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.

Re: Syntax for creating Muttrc.

[Jude DaShiell]

is fleacollar.sh part of the distribution yet?  That bash script can do a
pretty good job configuring a .muttrc file and creating necessary
directory structure for mutt to use.


--

Re: Syntax for creating Muttrc.

[Will Yardley]

On Thu, Oct 01, 2020 at 09:58:17PM -0700, M.R.P. zensky wrote:

> Can someone tell me the syntax for creating a Muttrc file on linux? I
> have installed it on linux and am trying to understand how to
> configure it.

man 5 muttrc and / or looking at the sample one that should ship with
Mutt could be a start.

There's also some info at:
https://wiki.archlinux.org/index.php/Mutt#Configuration

Or search online to find example configs to steal^Wborrow from.

/w

Syntax for creating Muttrc.

[M.R.P. zensky]

Can someone tell me the syntax for creating a Muttrc file on linux? I have 
installed it on linux and am trying to understand how to configure it.

Re: Simple muttrc file for accessing Gmail imap

[Jude DaShiell]

In order to create an app password, google will need your cell phone
number for verification and later security contacts should those become
necessary.

On Sun, 22 Sep 2019, Hokan wrote:

> Date: Sun, 22 Sep 2019 20:46:58
> From: Hokan 
> To: mutt-users@mutt.org
> Subject: Re: Simple muttrc file for accessing Gmail imap
>
> You'll also need to set "less secure password" or create an "app password".
>
> Or set up Oauth, but that'll take a bit of work.
>
>
> On Sun, Sep 22, 2019 at 07:11:10PM -0400, D.J.J. Ring, Jr. wrote:
> > I've been trying to help someone set up mutt for gmail imap using
> > mutt's internal support for IMAP.
> >
> > I have been going nuts.  Something's wrong but I cannot figure out why it 
> > fails.
> >
> > I just remembered that gmail has to have IMAP switched ON by using the
> > gmail settings online.:
> >
> > For the Gmail IMAP settings to work in your email client, IMAP access
> > must be enabled in Gmail online.
> >
> > https://www.lifewire.com/how-to-enable-gmail-via-imap-1170856
> >
> > HOW TO Activate IMAP in Gmail
> >
> > To access a Gmail account in your email program or mobile device via
> > the IMAP protocol, activate IMAP in Gmail.
> >
> > Open Gmail in a web browser.
> >
> > Choose Settings (the gear icon).
> >
> > Select Settings.
> >
> > Select the Forwarding and POP/IMAP tab.
> >
> > In the IMAP access section, select Enable IMAP.
> >
> > Leave the other settings on the default selections.
> >
> > Select Save Changes.
> >
> > That's it.
> >
> > Duh!  It's been so long since I enabled that setting, I forgot it had
> > to be done.
> >
> > Regards,
> >
> > David
> >
> > On Sat, Aug 24, 2019 at 4:06 PM Jude DaShiell  wrote:
> > >
> > > Yes, those macros work and do so silently.  Thanks for the macros and
> > > the idea to bind stuff to the comma key.  I hadn't thought of that one
> > > before.
> > >
> > > On Sat, 24 Aug 2019, Mark Frank wrote:
> > >
> > > > Date: Sat, 24 Aug 2019 14:00:27
> > > > From: Mark Frank 
> > > > To: mutt-users@mutt.org
> > > > Subject: Re: Simple muttrc file for accessing Gmail imap
> > > >
> > > > On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  
> > > > wrote:
> > > >
> > > > > mutt is set up to download pop3 but has no keyboard shortcut to 
> > > > > download
> > > > > imap or didn't the last time I went through its documentation.
> > > > >
> > > > >
> > > > I've had this in my muttrc for years.  Don't  if if any of these values 
> > > > are
> > > > optimum as I don't use mutt much anymore but it does work.
> > > >
> > > >
> > > > $ grep imap ./.mutt/muttrc | egrep -v ^#
> > > > set spoolfile=imaps://imap.gmail.com/INBOX
> > > > set folder=imaps://imap.gmail.com/
> > > > set imap_keepalive = 900
> > > > set imap_user='m...@markanderika.com'
> > > > set imap_pass=x
> > > > set imap_keepalive=300
> > > > unset imap_passive
> > > > set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
> > > > macro index ,g  "force retrieval of mail from IMAP 
> > > > server"
> > > > macro pager ,g  "force retrieval of mail from IMAP 
> > > > server"
> > > >
> > >
> > > --
> > >
>
>

-- 

Re: Simple muttrc file for accessing Gmail imap

[Hokan]

You'll also need to set "less secure password" or create an "app password".

Or set up Oauth, but that'll take a bit of work.


On Sun, Sep 22, 2019 at 07:11:10PM -0400, D.J.J. Ring, Jr. wrote:
> I've been trying to help someone set up mutt for gmail imap using
> mutt's internal support for IMAP.
> 
> I have been going nuts.  Something's wrong but I cannot figure out why it 
> fails.
> 
> I just remembered that gmail has to have IMAP switched ON by using the
> gmail settings online.:
> 
> For the Gmail IMAP settings to work in your email client, IMAP access
> must be enabled in Gmail online.
> 
> https://www.lifewire.com/how-to-enable-gmail-via-imap-1170856
> 
> HOW TO Activate IMAP in Gmail
> 
> To access a Gmail account in your email program or mobile device via
> the IMAP protocol, activate IMAP in Gmail.
> 
> Open Gmail in a web browser.
> 
> Choose Settings (the gear icon).
> 
> Select Settings.
> 
> Select the Forwarding and POP/IMAP tab.
> 
> In the IMAP access section, select Enable IMAP.
> 
> Leave the other settings on the default selections.
> 
> Select Save Changes.
> 
> That's it.
> 
> Duh!  It's been so long since I enabled that setting, I forgot it had
> to be done.
> 
> Regards,
> 
> David
> 
> On Sat, Aug 24, 2019 at 4:06 PM Jude DaShiell  wrote:
> >
> > Yes, those macros work and do so silently.  Thanks for the macros and
> > the idea to bind stuff to the comma key.  I hadn't thought of that one
> > before.
> >
> > On Sat, 24 Aug 2019, Mark Frank wrote:
> >
> > > Date: Sat, 24 Aug 2019 14:00:27
> > > From: Mark Frank 
> > > To: mutt-users@mutt.org
> > > Subject: Re: Simple muttrc file for accessing Gmail imap
> > >
> > > On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  wrote:
> > >
> > > > mutt is set up to download pop3 but has no keyboard shortcut to download
> > > > imap or didn't the last time I went through its documentation.
> > > >
> > > >
> > > I've had this in my muttrc for years.  Don't  if if any of these values 
> > > are
> > > optimum as I don't use mutt much anymore but it does work.
> > >
> > >
> > > $ grep imap ./.mutt/muttrc | egrep -v ^#
> > > set spoolfile=imaps://imap.gmail.com/INBOX
> > > set folder=imaps://imap.gmail.com/
> > > set imap_keepalive = 900
> > > set imap_user='m...@markanderika.com'
> > > set imap_pass=x
> > > set imap_keepalive=300
> > > unset imap_passive
> > > set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
> > > macro index ,g  "force retrieval of mail from IMAP 
> > > server"
> > > macro pager ,g  "force retrieval of mail from IMAP 
> > > server"
> > >
> >
> > --
> >

-- 
Hokan
Bicyclist
Sysadmin

Re: Simple muttrc file for accessing Gmail imap

[D.J.J. Ring, Jr.]

I've been trying to help someone set up mutt for gmail imap using
mutt's internal support for IMAP.

I have been going nuts.  Something's wrong but I cannot figure out why it fails.

I just remembered that gmail has to have IMAP switched ON by using the
gmail settings online.:

For the Gmail IMAP settings to work in your email client, IMAP access
must be enabled in Gmail online.

https://www.lifewire.com/how-to-enable-gmail-via-imap-1170856

HOW TO Activate IMAP in Gmail

To access a Gmail account in your email program or mobile device via
the IMAP protocol, activate IMAP in Gmail.

Open Gmail in a web browser.

Choose Settings (the gear icon).

Select Settings.

Select the Forwarding and POP/IMAP tab.

In the IMAP access section, select Enable IMAP.

Leave the other settings on the default selections.

Select Save Changes.

That's it.

Duh!  It's been so long since I enabled that setting, I forgot it had
to be done.

Regards,

David

On Sat, Aug 24, 2019 at 4:06 PM Jude DaShiell  wrote:
>
> Yes, those macros work and do so silently.  Thanks for the macros and
> the idea to bind stuff to the comma key.  I hadn't thought of that one
> before.
>
> On Sat, 24 Aug 2019, Mark Frank wrote:
>
> > Date: Sat, 24 Aug 2019 14:00:27
> > From: Mark Frank 
> > To: mutt-users@mutt.org
> > Subject: Re: Simple muttrc file for accessing Gmail imap
> >
> > On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  wrote:
> >
> > > mutt is set up to download pop3 but has no keyboard shortcut to download
> > > imap or didn't the last time I went through its documentation.
> > >
> > >
> > I've had this in my muttrc for years.  Don't  if if any of these values are
> > optimum as I don't use mutt much anymore but it does work.
> >
> >
> > $ grep imap ./.mutt/muttrc | egrep -v ^#
> > set spoolfile=imaps://imap.gmail.com/INBOX
> > set folder=imaps://imap.gmail.com/
> > set imap_keepalive = 900
> > set imap_user='m...@markanderika.com'
> > set imap_pass=x
> > set imap_keepalive=300
> > unset imap_passive
> > set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
> > macro index ,g  "force retrieval of mail from IMAP server"
> > macro pager ,g  "force retrieval of mail from IMAP server"
> >
>
> --
>

Re: Simple muttrc file for accessing Gmail imap

[Jude DaShiell]

Yes, those macros work and do so silently.  Thanks for the macros and
the idea to bind stuff to the comma key.  I hadn't thought of that one
before.

On Sat, 24 Aug 2019, Mark Frank wrote:

> Date: Sat, 24 Aug 2019 14:00:27
> From: Mark Frank 
> To: mutt-users@mutt.org
> Subject: Re: Simple muttrc file for accessing Gmail imap
>
> On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  wrote:
>
> > mutt is set up to download pop3 but has no keyboard shortcut to download
> > imap or didn't the last time I went through its documentation.
> >
> >
> I've had this in my muttrc for years.  Don't  if if any of these values are
> optimum as I don't use mutt much anymore but it does work.
>
>
> $ grep imap ./.mutt/muttrc | egrep -v ^#
> set spoolfile=imaps://imap.gmail.com/INBOX
> set folder=imaps://imap.gmail.com/
> set imap_keepalive = 900
> set imap_user='m...@markanderika.com'
> set imap_pass=x
> set imap_keepalive=300
> unset imap_passive
> set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
> macro index ,g  "force retrieval of mail from IMAP server"
> macro pager ,g  "force retrieval of mail from IMAP server"
>

-- 

Re: Simple muttrc file for accessing Gmail imap

[Mark Frank]

Yes.  Just tested and confirmed as I don't use mutt as much as I used to do.

On Sat, Aug 24, 2019 at 2:25 PM Jude DaShiell  wrote:

> Interesting, so you would hit ,g to download imap email?
>
> On Sat, 24 Aug 2019, Mark Frank wrote:
> > macro index ,g  "force retrieval of mail from IMAP
> server"
> > macro pager ,g  "force retrieval of mail from IMAP
> server"
> >
>
> --
>
>

Re: Simple muttrc file for accessing Gmail imap

[Jude DaShiell]

Interesting, so you would hit ,g to download imap email?

On Sat, 24 Aug 2019, Mark Frank wrote:

> Date: Sat, 24 Aug 2019 14:00:27
> From: Mark Frank 
> To: mutt-users@mutt.org
> Subject: Re: Simple muttrc file for accessing Gmail imap
>
> On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  wrote:
>
> > mutt is set up to download pop3 but has no keyboard shortcut to download
> > imap or didn't the last time I went through its documentation.
> >
> >
> I've had this in my muttrc for years.  Don't  if if any of these values are
> optimum as I don't use mutt much anymore but it does work.
>
>
> $ grep imap ./.mutt/muttrc | egrep -v ^#
> set spoolfile=imaps://imap.gmail.com/INBOX
> set folder=imaps://imap.gmail.com/
> set imap_keepalive = 900
> set imap_user='m...@markanderika.com'
> set imap_pass=x
> set imap_keepalive=300
> unset imap_passive
> set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
> macro index ,g  "force retrieval of mail from IMAP server"
> macro pager ,g  "force retrieval of mail from IMAP server"
>

-- 

Re: Simple muttrc file for accessing Gmail imap

[Mark Frank]

On Sat, Aug 24, 2019 at 1:21 PM Jude DaShiell  wrote:

> mutt is set up to download pop3 but has no keyboard shortcut to download
> imap or didn't the last time I went through its documentation.
>
>
I've had this in my muttrc for years.  Don't  if if any of these values are
optimum as I don't use mutt much anymore but it does work.


$ grep imap ./.mutt/muttrc | egrep -v ^#
set spoolfile=imaps://imap.gmail.com/INBOX
set folder=imaps://imap.gmail.com/
set imap_keepalive = 900
set imap_user='m...@markanderika.com'
set imap_pass=x
set imap_keepalive=300
unset imap_passive
set postponed=imaps://stag.mark-and-erika.com/INBOX.postponed
macro index ,g  "force retrieval of mail from IMAP server"
macro pager ,g  "force retrieval of mail from IMAP server"

Re: Simple muttrc file for accessing Gmail imap

[Jude DaShiell]

mutt is set up to download pop3 but has no keyboard shortcut to download
imap or didn't the last time I went through its documentation.

On Sat, 24 Aug 2019, D.J.J. Ring, Jr. wrote:

> Date: Sat, 24 Aug 2019 11:41:42
> From: "D.J.J. Ring, Jr." 
> To: Jude DaShiell 
> Cc: mutt-users@mutt.org
> Subject: Re: Simple muttrc file for accessing Gmail imap
>
> Hello Jude,
>
> It's possible to access gmail and download messages by adding imap
> locations and NOT use a mail transport program.  Everything is set up
> within the muttrc file.
>
> Burt Henry of the Vinux Wiki.
>
> Mutt vs. Alpine.
> http://wiki.vinuxproject.org/alpine_mutt
>
> Mutt Configuration and Basic Use.
> http://wiki.vinuxproject.org/mutt_configuration_and_basic_use
>
> He manages to do this just in muttrc.
>
> Here's the section of muttrc,
>
> ##Account Specific Settings
> # Change the following six lines to match your Gmail account details
> #And Uncomment and edit if YOU DO NOT WANT to USE ENCRYPTED PASSWD.
> #And comment out the top section that does the PW encryption.
> set imap_user = "gmail_han...@gmail.com"
> #set imap_pass = "my_PW"
> set smtp_url = "smtp://gmail_han...@smtp.gmail.com:587/"
> #set smtp_pass = "my_PW"
> set from = "gmail_han...@gmail.com"
> set realname = "My Name"
>
> # Change the following line to a different editor you prefer.
> set editor = "nano"
>
> ## GMail Config
> #(most of this should work with other IMAP accounts)
> ## Basic config, you can leave this as is in most cases
> # Not sure if timeout and keepalive value tweaking will help
> intermittent connection issues
> # (time values are in seconds)
> set wait_key = no
> set folder = "imaps://imap.gmail.com:993"
> set spoolfile = "+INBOX"
> set imap_check_subscribed
> set hostname = gmail.com
> set mail_check = 180
> set timeout = 300
> # Allow Mutt to open new imap connection automatically.
> unset imap_passive
> # Keep IMAP connection alive by polling intermittently
> set imap_keepalive = 210
> set postponed = "+[GMail]/Drafts"
> set record = "+[GMail]/Sent Mail"
> set header_cache=~/.mutt/cache/headers
> set message_cachedir=~/.mutt/cache/bodies
> set certificate_file=~/.mutt/certificates
> set alias_file=~/.mutt/aliases
> set move = no
> set include
> set sort = 'threads'
> set sort_aux = 'reverse-last-date-received'
> set auto_tag = yes
> ## Reminds you of missing subject or empty body with msg
> sent as default
> set abort_nosubject = ask-no
> set abort_unmodified = ask-no
> ignore "Authentication-Results:"
> ignore "DomainKey-Signature:"
> ignore "DKIM-Signature:"
> hdr_order Date From To Cc
> alternative_order text/plain text/html *
> auto_view text/html
>
> This is from page:  http://wiki.vinuxproject.org/muttrc
>
> Unfortunately, there are errors in his delightfully easy gpg configuration,
> and sometimes he has googlemail instead of gmail and googlemail no longer
> works for me in this muttrc.
>
> There is also a more elaborate muttrc file with more features, but maybe
> the same errors, I'm going through it step by step and writing down the
> errors.
>
> Since I have access to the Vinux Wiki I will upload the corrections as soon
> as I make sure they are correct.
>
> Best wishes,
>
> David Ring
>
> On Sat, Aug 24, 2019, 10:14 Jude DaShiell  wrote:
>
> > I think I can help there, only thing is mine has the mutt blind-friendly
> > options in it.
> >
> > On Sat, 24 Aug 2019, D.J.J. Ring, Jr. wrote:
> >
> >
>

-- 

Re: Simple muttrc file for accessing Gmail imap

[D.J.J. Ring, Jr.]

Hello Jude,

It's possible to access gmail and download messages by adding imap
locations and NOT use a mail transport program.  Everything is set up
within the muttrc file.

Burt Henry of the Vinux Wiki.

Mutt vs. Alpine.
http://wiki.vinuxproject.org/alpine_mutt

Mutt Configuration and Basic Use.
http://wiki.vinuxproject.org/mutt_configuration_and_basic_use

He manages to do this just in muttrc.

Here's the section of muttrc,

##Account Specific Settings
# Change the following six lines to match your Gmail account details
#And Uncomment and edit if YOU DO NOT WANT to USE ENCRYPTED PASSWD.
#And comment out the top section that does the PW encryption.
set imap_user = "gmail_han...@gmail.com"
#set imap_pass = "my_PW"
set smtp_url = "smtp://gmail_han...@smtp.gmail.com:587/"
#set smtp_pass = "my_PW"
set from = "gmail_han...@gmail.com"
set realname = "My Name"

# Change the following line to a different editor you prefer.
set editor = "nano"

## GMail Config
#(most of this should work with other IMAP accounts)
## Basic config, you can leave this as is in most cases
# Not sure if timeout and keepalive value tweaking will help
intermittent connection issues
# (time values are in seconds)
set wait_key = no
set folder = "imaps://imap.gmail.com:993"
set spoolfile = "+INBOX"
set imap_check_subscribed
set hostname = gmail.com
set mail_check = 180
set timeout = 300
# Allow Mutt to open new imap connection automatically.
unset imap_passive
# Keep IMAP connection alive by polling intermittently
set imap_keepalive = 210
set postponed = "+[GMail]/Drafts"
set record = "+[GMail]/Sent Mail"
set header_cache=~/.mutt/cache/headers
set message_cachedir=~/.mutt/cache/bodies
set certificate_file=~/.mutt/certificates
set alias_file=~/.mutt/aliases
set move = no
set include
set sort = 'threads'
set sort_aux = 'reverse-last-date-received'
set auto_tag = yes
## Reminds you of missing subject or empty body with msg
sent as default
set abort_nosubject = ask-no
set abort_unmodified = ask-no
ignore "Authentication-Results:"
ignore "DomainKey-Signature:"
ignore "DKIM-Signature:"
hdr_order Date From To Cc
alternative_order text/plain text/html *
auto_view text/html

This is from page:  http://wiki.vinuxproject.org/muttrc

Unfortunately, there are errors in his delightfully easy gpg configuration,
and sometimes he has googlemail instead of gmail and googlemail no longer
works for me in this muttrc.

There is also a more elaborate muttrc file with more features, but maybe
the same errors, I'm going through it step by step and writing down the
errors.

Since I have access to the Vinux Wiki I will upload the corrections as soon
as I make sure they are correct.

Best wishes,

David Ring

On Sat, Aug 24, 2019, 10:14 Jude DaShiell  wrote:

> I think I can help there, only thing is mine has the mutt blind-friendly
> options in it.
>
> On Sat, 24 Aug 2019, D.J.J. Ring, Jr. wrote:
>
>

Re: Simple muttrc file for accessing Gmail imap

[Jude DaShiell]

I think I can help there, only thing is mine has the mutt blind-friendly
options in it.

On Sat, 24 Aug 2019, D.J.J. Ring, Jr. wrote:

> Date: Sat, 24 Aug 2019 10:09:48
> From: "D.J.J. Ring, Jr." 
> To: mutt-users@mutt.org
> Subject: Simple muttrc file for accessing Gmail imap
>
> For some blind and visually impaired users graphical user interfaces are as
> frustrating as a game of blindfolded archery.
>
> Does anyone have a simple good example of a muttrc file that can access
> gmail imap email by just changing "username" to your real user name and
> "password" to your real password?
>
> Thanks,
>
> David
>

-- 

Simple muttrc file for accessing Gmail imap

[D.J.J. Ring, Jr.]

For some blind and visually impaired users graphical user interfaces are as
frustrating as a game of blindfolded archery.

Does anyone have a simple good example of a muttrc file that can access
gmail imap email by just changing "username" to your real user name and
"password" to your real password?

Thanks,

David

Re: providing imap_pass but not from ~/.muttrc

[Cameron Simpson]

On 14Jun2019 05:48, Jude DaShiell  wrote:

Can mutt read gnome-key-ring?  If so, you maybe could use secret-tool
with the right parameters once.


Well, it can read the output of a shell command, so something could be 
arranged. However, I believe Mattias wants to use credentials from a 
local source and get them to a mutt run on a remote machine.


Can the gnome-key-ring socket be usefully forwarded over the ssh connect 
so that the remote mutt can access it? You can forward UNIX domain 
sockets over an ssh connection, the trick is what needs to be said on 
the far end to get the remote secret-tool to access the forwarded 
socket. An environment variable presumably.


Cheers,
Cameron Simpson 

Re: providing imap_pass but not from ~/.muttrc

[Jude DaShiell]

Can mutt read gnome-key-ring?  If so, you maybe could use secret-tool
with the right parameters once.

On Thu, 13 Jun 2019, Matthias Apitz wrote:

> Date: Thu, 13 Jun 2019 14:56:33
> From: Matthias Apitz 
> To: mutt-users@mutt.org
> Subject: providing imap_pass but not from ~/.muttrc
>
>
> I often use SSH to connect to my rented VM space of my ISP (which gets me to a
> Linux server) and I do use mutt from there to check my mails or even to
> answer, esp. when I do not have my FreeBSD netbook with full Internet and all
> mails up.
>
> I do not want to set 'imap_pass=...' and such values in the ~/.muttrc on
> this VM. Is there any other way to provide such credentials without to
> key them in on start of mutt, for example based on an environment
> variable which I could route to the VM through the SSH session like:
>
> $ ssh -At www.unixarea.de imap_pass=abc bash --login
> Thu Jun 13 20:44:51 CEST 2019
> ...
> sh4-5:~$ env | grep imap
> imap_pass=abc
>
> Any other ideas? The SSH access is RSA based, i.e. without any password,
> and the private key comes from my OpenPGP card. Best solution would be to
> use this key as well for the IMAP authentication somehow.
>
> Thanks
>
>   matthias
>
>

-- 

Re: providing imap_pass but not from ~/.muttrc

[Matthias Apitz]

El día Thursday, June 13, 2019 a las 03:19:26PM -0400, Ben Boeckel escribió:

> > $ ssh -At www.unixarea.de imap_pass=abc bash --login
> > Thu Jun 13 20:44:51 CEST 2019
> > ...
> > sh4-5:~$ env | grep imap
> > imap_pass=abc
> 
> I don't think there's any mechanism in mutt. You might be able to have
> `mutt -F <(genmuttrc)` dump it out. It may also be worth just doing `set
> imap_pass=...` inside mutt once it has started.

I think the best generic approach would be to be able to set in .muttrc
something like

set imap_pass=" 
> However, what's your threat model that having it in the file is not OK
> but the environment is OK? `/proc/foo/environ` is just as readable on
> Linux as muttrc is likely to be.

Correct, but you need a bit more knowledge to read it from /proc/PID/...
as just grepping/stealing the users home dir.

> How are you getting your sendmail password over in order to send email?
> Or is it trusted because it's coming from the ISP's VM?

It's handed over by mutt to /usr/sbin/sendmail ... on the VM locally.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!

Re: providing imap_pass but not from ~/.muttrc

[Cameron Simpson]

On 13Jun2019 17:10, Larry Rosenman  wrote:

On 06/13/2019 4:52 pm, Cameron Simpson wrote:

On 13Jun2019 14:26, Larry Rosenman  wrote:

I do the following trick:
source "gpg -q --textmode -d ~/.neomutt/passwords.gpg  |"

where the passwords.gpg file sets my_ vars for all my
passwords.


Doesn't that require interaction on each mutt startup? I appreciate
that this has the password nicely encrypted when idle and doesn't
display them on the command line or in environment variables.


[snip]

I have gpg-agent running so the key is available.  I have some 
switch-identity stuff in the rest of my

(neo)mutt rc files to switch between the identities.


Ah, I wondered. My own gpg-agent timeout is short enough that I'd be 
prompted all the time :-(


Cheers,
Cameron Simpson 

Re: providing imap_pass but not from ~/.muttrc

[Larry Rosenman]

On 06/13/2019 4:52 pm, Cameron Simpson wrote:

On 13Jun2019 14:26, Larry Rosenman  wrote:

I do the following trick:

source "gpg -q --textmode -d ~/.neomutt/passwords.gpg  |"

where the passwords.gpg file sets my_ vars for all my
passwords.


Doesn't that require interaction on each mutt startup? I appreciate
that this has the password nicely encrypted when idle and doesn't
display them on the command line or in environment variables.


[snip]

I have gpg-agent running so the key is available.  I have some 
switch-identity stuff in the rest of my

(neo)mutt rc files to switch between the identities.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

Re: providing imap_pass but not from ~/.muttrc

[Cameron Simpson]

On 13Jun2019 14:26, Larry Rosenman  wrote:

I do the following trick:

source "gpg -q --textmode -d ~/.neomutt/passwords.gpg  |"

where the passwords.gpg file sets my_ vars for all my
passwords.


Doesn't that require interaction on each mutt startup? I appreciate that 
this has the password nicely encrypted when idle and doesn't display 
them on the command line or in environment variables.


I've got various mail credentials in my .fetchmailrc (I now use getmail, 
but whatever), so I've got scripts to fetch them from it. Should port it 
to the getmail config some time.


So, the muttrc config line which presages accessing my phone IMAP 
account:


 source 'cs-mutt-imap-settings cs-iphone-cc'

cs-mutt-imap-settings is this script:

 #!/bin/sh
 #
 # Read clause form .fetchmailrc, recite mutt IMAP settings.
 #   - Cameron Simpson  26sep2015
 #

 set -ue

 clause=$1
 shift

 fetchmailclause "$clause" \
 | awk '$1 == "user" { user=$2 }
$1 == "pass" { pass=$2 }
$1 == "via"  { via=$2 }
END  { print "set imap_user='\''" user "'\''"
   print "set imap_pass='\''" pass "'\''"
   print "set my_imap_host='\''" via "'\''"
 }
   '

and fetchmailclause is this script:

 #!/bin/sh
 #
 # Pull out a single clause from a .fetchmailrc file.
 # The parsing's a little simplistic but it works fairly well.
 #- Cameron Simpson  09sep2003
 #

 rc=$HOME/.fetchmailrc
 start=skip# vs poll

 cmd=$0
 usage="Usage: $cmd [-f fetchmailrc] [clause]"

 badopts=

 [ "x$1" = x-f ] && { rc=$2; shift; shift; }

 [ $# = 0 ] && exec awk '$1 == "spoll" || $1 == "skip" { print $2 }' "$rc"

 clause=$1; shift
 [ $# = 0 ] || { echo "$cmd: extra arguments after clause: $*" >&2; 
 badopts=1; }


 [ $badopts ] && { echo "$usage" >&2; exit 2; }

 exec sed -ne '
 y// /
 s/$/ /
 '"/^ *skip  *$clause /b start
 /^ *poll  *$clause /b start
 d
 :start
 n
 y// /
 s/   */ /g
 s/^ //
 s/ $//
 /^#/b start
 /^$/b start
 /^skip /d
 /^poll /d
 p
 b start" "$rc"

So if the OP already has the credentials sitting around elsewhere they 
could automate getting them.


This approach does have the downside that credentials are still in files 
in the clear though.


Cheers,
Cameron Simpson 

Re: providing imap_pass but not from ~/.muttrc

[Larry Rosenman]

On 06/13/2019 2:19 pm, Ben Boeckel wrote:

On Thu, Jun 13, 2019 at 20:56:33 +0200, Matthias Apitz wrote:
I often use SSH to connect to my rented VM space of my ISP (which gets 
me to a
Linux server) and I do use mutt from there to check my mails or even 
to
answer, esp. when I do not have my FreeBSD netbook with full Internet 
and all

mails up.

I do not want to set 'imap_pass=...' and such values in the ~/.muttrc 
on

this VM. Is there any other way to provide such credentials without to
key them in on start of mutt, for example based on an environment
variable which I could route to the VM through the SSH session like:

$ ssh -At www.unixarea.de imap_pass=abc bash --login
Thu Jun 13 20:44:51 CEST 2019
...
sh4-5:~$ env | grep imap
imap_pass=abc


I don't think there's any mechanism in mutt. You might be able to have
`mutt -F <(genmuttrc)` dump it out. It may also be worth just doing 
`set

imap_pass=...` inside mutt once it has started.

However, what's your threat model that having it in the file is not OK
but the environment is OK? `/proc/foo/environ` is just as readable on
Linux as muttrc is likely to be.

How are you getting your sendmail password over in order to send email?
Or is it trusted because it's coming from the ISP's VM?

--Ben



I do the following trick:

source "gpg -q --textmode -d ~/.neomutt/passwords.gpg  |"

where the passwords.gpg file sets my_ vars for all my
passwords.

Just an idea.

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

Re: providing imap_pass but not from ~/.muttrc

[Ben Boeckel]

On Thu, Jun 13, 2019 at 20:56:33 +0200, Matthias Apitz wrote:
> I often use SSH to connect to my rented VM space of my ISP (which gets me to a
> Linux server) and I do use mutt from there to check my mails or even to
> answer, esp. when I do not have my FreeBSD netbook with full Internet and all
> mails up.
> 
> I do not want to set 'imap_pass=...' and such values in the ~/.muttrc on
> this VM. Is there any other way to provide such credentials without to
> key them in on start of mutt, for example based on an environment
> variable which I could route to the VM through the SSH session like:
> 
> $ ssh -At www.unixarea.de imap_pass=abc bash --login
> Thu Jun 13 20:44:51 CEST 2019
> ...
> sh4-5:~$ env | grep imap
> imap_pass=abc

I don't think there's any mechanism in mutt. You might be able to have
`mutt -F <(genmuttrc)` dump it out. It may also be worth just doing `set
imap_pass=...` inside mutt once it has started.

However, what's your threat model that having it in the file is not OK
but the environment is OK? `/proc/foo/environ` is just as readable on
Linux as muttrc is likely to be.

How are you getting your sendmail password over in order to send email?
Or is it trusted because it's coming from the ISP's VM?

--Ben

providing imap_pass but not from ~/.muttrc

[Matthias Apitz]

I often use SSH to connect to my rented VM space of my ISP (which gets me to a
Linux server) and I do use mutt from there to check my mails or even to
answer, esp. when I do not have my FreeBSD netbook with full Internet and all
mails up.

I do not want to set 'imap_pass=...' and such values in the ~/.muttrc on
this VM. Is there any other way to provide such credentials without to
key them in on start of mutt, for example based on an environment
variable which I could route to the VM through the SSH session like:

$ ssh -At www.unixarea.de imap_pass=abc bash --login
Thu Jun 13 20:44:51 CEST 2019
...
sh4-5:~$ env | grep imap
imap_pass=abc

Any other ideas? The SSH access is RSA based, i.e. without any password,
and the private key comes from my OpenPGP card. Best solution would be to
use this key as well for the IMAP authentication somehow.

Thanks

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!


signature.asc
Description: PGP signature

Re: muttrc for different mutt versions

[Todd Zullinger]

Claus Assmann wrote:
> On Thu, Sep 06, 2018, Kai Weber wrote:
> 
>> How can I have the same muttrc on both machines without running into
>> errors during mutt start?
> 
> I split the rc file into
> 1) a common part
> 2) parts specific to the mutt version
> and
> - source the common part (1) in the specific version (2)
> - use a wrapper which invokes mutt with the specific rc file (2)

Mutt also looks for muttrc-$VERSION, so you can avoid the
need for a wrapper.  If you start mutt-1.10.1 and have a
config file at ~/.mutt/muttrc-1.10.1, it will be sourced.

You can use $XDG_CONFIG_HOME/mutt/muttrc-$VERSION or
~/.muttrc-$VERSION as well, of course.

Source: http://mutt.org/doc/manual/#configuration-files

-- 
Todd
~~
Happiness is like peeing on yourself. Everyone can see it, but only
you can feel its warmth



signature.asc
Description: PGP signature

Re: muttrc for different mutt versions

[Claus Assmann]

On Thu, Sep 06, 2018, Kai Weber wrote:

> How can I have the same muttrc on both machines without running into
> errors during mutt start?

I split the rc file into
1) a common part
2) parts specific to the mutt version
and
- source the common part (1) in the specific version (2)
- use a wrapper which invokes mutt with the specific rc file (2)

muttrc for different mutt versions

[Kai Weber]

At home I use Debian unstable with mutt 1.10.x, at work I am bound to
Debian 9 and mutt 1.7.2. I know, I could compile and install mutt by
myself but let's say I can not:

How can I have the same muttrc on both machines without running into
errors during mutt start?

Error in /home/kai/.config/mutt/muttrc, line 16: mime_type_query_command: 
unknown variable
Error in /home/kai/.config/mutt/muttrc, line 76: abort_noattach_regexp: unknown 
variable
source: errors in /home/kai/.config/mutt/muttrc

Any suggestions?

Kai

Re: source .muttrc after changes in script?

[Cameron Simpson]

On 03Aug2018 14:42, Orm Finnendahl  
wrote:

I wrote a shell script to specify an fcc for the sender of an email
and insert it into .muttrc and bound it to ".f".

Is there a way to automatize sourcing the .muttrc after the insertion?


Please, just "automate" :-(

I don't think so. You could half way do it by making macros for several common 
mutt keystrokes to test for a changed muttrc and resource things before doing 
the primary action, but that feels cumbersome and fragile.


On the other hand, doing that for a choice specific set, such as just before 
composing a new message, is less cumbersome, less fragile, and far less 
impactful to perfomance.



On a related issue:

When sourcing the .muttrc (using ": source ~/.muttrc") the mail
entries get resorted. Is there a way to inhibit this sorting?


Likely your .muttrc sets the sorting criteria, and that resorted the index.

If you separate your .muttrc into a few files:

 - fixed settings (eg your attributed etc)
 - default initial settings (eg your sorting)
 - modifiable settings (eg list of mail aliases etc which might be updated)

and make your main .muttrc source all 3 then you could just not source your 
muttrc, instead sourcing only the relevant file such as that last "modifiable 
settings" file. Then your sorting should not change.


Cheers,
Cameron Simpson 

source .muttrc after changes in script?

[Orm Finnendahl]

Hi,

 I wrote a shell script to specify an fcc for the sender of an email
and insert it into .muttrc and bound it to ".f".

Is there a way to automatize sourcing the .muttrc after the insertion?

On a related issue:

When sourcing the .muttrc (using ": source ~/.muttrc") the mail
entries get resorted. Is there a way to inhibit this sorting?

--
Orm

Re: Need some help with send-hook and folder-hook, their order in muttrc

[Jason]

On Tue, Nov 07, 2017 at 10:17:04AM +, Chris Green wrote:
> I want messages sent from one particular folder to have a different
> From: address.
> 
> Currently the only settings I have in my muttrc that affect the From:
> address are:-
> 
> send-hook .  'my_hdr From: Chris Green <ch...@isbd.co.uk>'
> ...
> ...
> send-hook ~l 'my_hdr From: Chris Green <c...@isbd.net>'
> 
> 
> I use the c...@isbd.net address for all my mailing lists.
> 
> 
> I'd like to make it so that when I'm in a particular folder (which
> will probably be called 'cl') my From: address will also be
> c...@isbd.net. 
> 
> So I need to add something like:-
> 
> folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'
> 
> However I'm a little unclear what else I need, do I need something
> like:-
> 
> folder-hook . 'my_hdr From: Chris Green <ch...@isbd.co.uk>'
> 
> and does it go before or after the specific 'cl one?  Plus, do these
> two settings make the send-hook setting of my From: address redundant?
> I still need the 'send hook ~l' one of course.
> 

Couldn't you just do something like this:

folder-hook . 'set from=ch...@isbd.co.uk; set realname="Chris Green"'
folder-hook /path/to/cl 'set from=c...@isbd.net; set realname="Chris Green"'

The first line sets the default and the second line sets it for the cl
folder. Although I'm not sure how this interacts with your send-hook
lines; maybe you'd need to remove the 'send-hook . ' line.

-- 
Jason

Re: Need some help with send-hook and folder-hook, their order in muttrc

[Chris Green]

On Tue, Nov 07, 2017 at 09:32:09PM +, David Woodfall wrote:
> > On Tue, Nov 07, 2017 at 08:49:06AM -0800, Ian Zimmerman wrote:
> > > On 2017-11-07 10:17, Chris Green wrote:
> > > 
> > > > I'd like to make it so that when I'm in a particular folder (which
> > > > will probably be called 'cl') my From: address will also be
> > > > c...@isbd.net.
> > > >
> > > > So I need to add something like:-
> > > >
> > > > folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'
> > > >
> > > > However I'm a little unclear what else I need,
> > > 
> > > If you use my_hdr in folder hooks at all, you probably need something
> > > like this line, from my own .muttrc:
> > > 
> > > folder-hook . "unmy_hdr to from reply-to bcc newsgroups x-loosely-listed"
> > > 
> > > >From my experience, you'll never be able to keep track of them
> > > individually and add the return-to-default hook for each header 
> > > separately.
> > > 
> > OK, it seems to get rather messy.
> > 
> > I think it may be easier to have a macro which
> > 
> >Changes my_hdr
> >Sends the message
> >Changes my_hdr back
> > 
> > -- 
> > Chris Green
> 
> What I do is have a hooks file which runs other hooks files depending
> on the folder:
> 
Ah, now that's clever, it might well do exactly what I need in a way
that I can understand, thanks.


> My .mutt/hooks:
> 
> folder-hook 'imaps://domain/.*' source ~/.mutt/default
> folder-hook =lists/* source ~/.mutt/listhook
> 
> My .mutt/default
> 
> my_hdr From: David Woodfall <d...@somedomain.net>
> set sort=threads
> 
> My .mutt/listhook:
> 
> set collapse-all
> set sort=threads
> my_hdr From: David Woodfall <d...@dawoodfall.net>
> 
Thanks for that, it looks very close to the sort of thing I want to do.

-- 
Chris Green

Re: Need some help with send-hook and folder-hook, their order in muttrc

[David Woodfall]

On Tue, Nov 07, 2017 at 08:49:06AM -0800, Ian Zimmerman wrote:

On 2017-11-07 10:17, Chris Green wrote:

> I'd like to make it so that when I'm in a particular folder (which
> will probably be called 'cl') my From: address will also be
> c...@isbd.net.
>
> So I need to add something like:-
>
> folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'
>
> However I'm a little unclear what else I need,

If you use my_hdr in folder hooks at all, you probably need something
like this line, from my own .muttrc:

folder-hook . "unmy_hdr to from reply-to bcc newsgroups x-loosely-listed"

>From my experience, you'll never be able to keep track of them
individually and add the return-to-default hook for each header separately.


OK, it seems to get rather messy.

I think it may be easier to have a macro which

   Changes my_hdr
   Sends the message
   Changes my_hdr back

--
Chris Green


What I do is have a hooks file which runs other hooks files depending
on the folder:

My .mutt/hooks:

folder-hook 'imaps://domain/.*' source ~/.mutt/default
folder-hook =lists/* source ~/.mutt/listhook

My .mutt/default

my_hdr From: David Woodfall <d...@somedomain.net>
set sort=threads

My .mutt/listhook:

set collapse-all
set sort=threads
my_hdr From: David Woodfall <d...@dawoodfall.net>

The default file will set the header back after it has been changed in
the lists folder.

Re: Need some help with send-hook and folder-hook, their order in muttrc

[Chris Green]

On Tue, Nov 07, 2017 at 08:49:06AM -0800, Ian Zimmerman wrote:
> On 2017-11-07 10:17, Chris Green wrote:
> 
> > I'd like to make it so that when I'm in a particular folder (which
> > will probably be called 'cl') my From: address will also be
> > c...@isbd.net. 
> > 
> > So I need to add something like:-
> > 
> > folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'
> > 
> > However I'm a little unclear what else I need, 
> 
> If you use my_hdr in folder hooks at all, you probably need something
> like this line, from my own .muttrc:
> 
> folder-hook . "unmy_hdr to from reply-to bcc newsgroups x-loosely-listed"
> 
> >From my experience, you'll never be able to keep track of them
> individually and add the return-to-default hook for each header separately.
> 
OK, it seems to get rather messy.

I think it may be easier to have a macro which

Changes my_hdr
Sends the message
Changes my_hdr back

-- 
Chris Green

Re: Need some help with send-hook and folder-hook, their order in muttrc

[Ian Zimmerman]

On 2017-11-07 10:17, Chris Green wrote:

> I'd like to make it so that when I'm in a particular folder (which
> will probably be called 'cl') my From: address will also be
> c...@isbd.net. 
> 
> So I need to add something like:-
> 
> folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'
> 
> However I'm a little unclear what else I need, 

If you use my_hdr in folder hooks at all, you probably need something
like this line, from my own .muttrc:

folder-hook . "unmy_hdr to from reply-to bcc newsgroups x-loosely-listed"

>From my experience, you'll never be able to keep track of them
individually and add the return-to-default hook for each header separately.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Need some help with send-hook and folder-hook, their order in muttrc

[Chris Green]

I want messages sent from one particular folder to have a different
From: address.

Currently the only settings I have in my muttrc that affect the From:
address are:-

send-hook .  'my_hdr From: Chris Green <ch...@isbd.co.uk>'
...
...
send-hook ~l 'my_hdr From: Chris Green <c...@isbd.net>'


I use the c...@isbd.net address for all my mailing lists.


I'd like to make it so that when I'm in a particular folder (which
will probably be called 'cl') my From: address will also be
c...@isbd.net. 

So I need to add something like:-

folder-hook cl 'my_hdr From: Chris Green <c...@isbd.net>'

However I'm a little unclear what else I need, do I need something
like:-

folder-hook . 'my_hdr From: Chris Green <ch...@isbd.co.uk>'

and does it go before or after the specific 'cl one?  Plus, do these
two settings make the send-hook setting of my From: address redundant?
I still need the 'send hook ~l' one of course.

-- 
Chris Green

Re: My typical .muttrc frustrations

[Erik Christiansen]

On 22.04.17 14:33, Charles E Campbell wrote:
> Hello, Erik:
> 
> I tried both mail and mailx.  Both fail silently when I attempt to send an
> email off my machine (didn't try mailx, but mail will send email to accounts
> on the same machine), although I suppose its possible they're still
> re-trying somewhere in the background and won't get a failure email for a
> few days.

Charles, I've just sent an email to myself via the ISP (the "Received:"
header lines show it went via 3 of their servers), thus confirming that
I don't have such an issue. (I'll freely admit that much of my mailx
usage is to send myself a reminder after I've shut down mutt, and can't
be bothered with entering the ISP password for fetchmail, and waiting
for things to come up.)

> That's why I had been using mutt until recently.  I have two
> potential smtp(s) targets, but neither works with mutt.  For example, both
> smtp targets fail with:
> 
> SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-SHA)
> digest-md5 authentication failed, trying next method
> external authentication failed, trying next method
> anonymous authentication failed, trying next method
> SASL authentication failed
> Could not send the message.

And that doesn't happen when mutt is used interactively, AIUI.
The question seems to be: What does it do in that mode, to bring up the
SSL connection, that neither mutt nor mail do in batch mode?

> Regards and thank you for looking into this,
> Chip Campbell

No worries. Unfortunately, I haven't set up any SSL for mail, so can't
shed the light of experience on the gremlins you're smoking out.

Erik

Re: My typical .muttrc frustrations

[Charles E Campbell]

Erik Christiansen wrote:

On 17.04.17 22:34, Charles E Campbell wrote:

Here's the result:

...

Could not send the message.

Well, it's never occurred to me to pause to figure out how to use mutt
to send email on the command line, because the MUA I used before mutt
was traditional unix "mail"¹, and it is infinitely easier to just
apt-get that. A "man mail" shows that it's:

bsd-mailx - simple mail user agent

that I'm using ATM. As /usr/bin/bsd-mailx is only 92 kB in size, it
doesn't add much ballast to mutt 1.8.0 at 2.46 MB.

Mind you, it may just be that running an MTA here (postfix these days)
is what avoids your problems. That was easy to set up after the first
effort, given that I keep a few notes to avoid excessive brow furrowing
next time round.

¹ It was what we had on HP-UX and Solaris boxes back in the 1980s, and
   it still works the same.


Hello, Erik:

I tried both mail and mailx.  Both fail silently when I attempt to send 
an email off my machine (didn't try mailx, but mail will send email to 
accounts on the same machine), although I suppose its possible they're 
still re-trying somewhere in the background and won't get a failure 
email for a few days.  That's why I had been using mutt until recently.  
I have two potential smtp(s) targets, but neither works with mutt.  For 
example, both smtp targets fail with:


SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-SHA)
digest-md5 authentication failed, trying next method
external authentication failed, trying next method
anonymous authentication failed, trying next method
SASL authentication failed
Could not send the message.

Regards and thank you for looking into this,
Chip Campbell

Re: My typical .muttrc frustrations

[Erik Christiansen]

On 17.04.17 22:34, Charles E Campbell wrote:
> Here's the result:
...
> Could not send the message.

Well, it's never occurred to me to pause to figure out how to use mutt
to send email on the command line, because the MUA I used before mutt
was traditional unix "mail"¹, and it is infinitely easier to just
apt-get that. A "man mail" shows that it's:

bsd-mailx - simple mail user agent

that I'm using ATM. As /usr/bin/bsd-mailx is only 92 kB in size, it
doesn't add much ballast to mutt 1.8.0 at 2.46 MB.

Mind you, it may just be that running an MTA here (postfix these days)
is what avoids your problems. That was easy to set up after the first
effort, given that I keep a few notes to avoid excessive brow furrowing
next time round.

¹ It was what we had on HP-UX and Solaris boxes back in the 1980s, and
  it still works the same.

Erik

Re: My typical .muttrc frustrations

[Charles E Campbell]

lilydjwg wrote:

On Sun, Apr 16, 2017 at 06:48:34PM -0400, Charles E Campbell wrote:

Hello:

It was tricky, but I got my .muttrc working so that I could send stuff out
via the command line.

Until about two weeks ago, where mutt suddenly stopped sending out email and
started complaining instead.

To shorten the story: this is what I use with Seamonkey.  Works fine.

Description   : astronaut
Server Name   : outgoing.verizon.net
Port  : 465
Connection Security   : SSL/TLS
Authentication Method : Normal password
User Name : astronaut

Of course, there is a password involved and its stored in Seamonkey's
passwords file.

Now, on to .muttrc:

[...]

You can see my some of my attempts at getting mutt to talk via smtp and
messing around with smtp authenticators.  None of them work.

Would someone please help?

Try this one?

set smtp_url="smtps://astron...@verizon.net@outgoing.verizon.net:465"


Here's the result:

cec/ fsp#06 djinni? tstmutt.cfb

SSL connection using TLSv1/SSLv3 (ECDHE-RSA-AES256-GCM-SHA384)
external authentication failed, trying next method
anonymous authentication failed, trying next method
plain authentication failed, trying next method
Connection to outgoing.verizon.net closed
digest-md5 authentication failed, trying next method
No authenticators available
Could not send the message.

That's better than what I had been getting: (after a long pause)

Connection to outgoing.verizon.net closed
SMTP session failed: read error
Could not send the message.

Thank you,
Chip Campbell

My typical .muttrc frustrations

[Charles E Campbell]

Hello:

It was tricky, but I got my .muttrc working so that I could send stuff 
out via the command line.


Until about two weeks ago, where mutt suddenly stopped sending out email 
and started complaining instead.


To shorten the story: this is what I use with Seamonkey.  Works fine.

Description   : astronaut
Server Name   : outgoing.verizon.net
Port  : 465
Connection Security   : SSL/TLS
Authentication Method : Normal password
User Name : astronaut

Of course, there is a password involved and its stored in Seamonkey's 
passwords file.


Now, on to .muttrc:

#set smtp_url="smtp://smtp.verizon.net:465"
#set smtp_url="smtps://astron...@smtp.verizon.net:465"
#set smtp_url="smtps://astron...@outgoing.verizon.net:465"
#set smtp_url="smtp://astron...@outgoing.verizon.net:465"
#set smtp_url="smtp://outgoing.verizon.net:465"
set smtp_url="smtp://outgoing.verizon.net:465/"
set smtp_pass="ELIDED"
set from="astron...@verizon.net"
set realname="C Campbell"
set editor="gvim"
set move=no
set 
smtp_authenticators="external:anonymous:plain:otp:skey:digest-md5:scram:ntlm:gssapi:browserid-aes128:eap-aes128"

ignore "Authentication-Results:"
ignore "DomainKey-Signature:"
ignore "DKIM-Signature:"
hdr_order Date From To Cc
alternative_order text/plain text/html *
set header_cache=~/.mutt/cache/headers
set message_cachedir=~/.mutt/cache/bodies
set certificate_file=~/.mutt/certificates
set smart_wrap=yes
set sort='threads'
set sort_aux='last-date-received'
# vim: ft=muttrc

You can see my some of my attempts at getting mutt to talk via smtp and 
messing around with smtp authenticators.  None of them work.


Would someone please help?

Thank you,
Chip Campbell

Re: Muttrc example needed POP3/SMTP

[Erik Christiansen]

On 04.02.17 17:04, sunrise wrote:
> 
> Are there any suggestions for which MTA would be most suitable for
> this purpose (sending queued messages on a system that is not online
> when composing messages)?

They would all handle that, straight out of the box. Mail spooling is a
basic MTA function. (I remember looking at great piles of backed up mail
on a company-wide mailserver which used sendmail and uucp over dial-up,
back in the early 1990s, when the internet in Australia had only spread
to universities and companies.)

I have ADSL, but may not remember to turn on the modem before composing
some emails. Postfix will spool them, and automatically send them after
the ADSL link comes up. The others will too.

Maybe look up the manual on the preferred MTA candidate, and check for
an easy to understand command to flush the queue, in case you ever need
to manually free a logjam for some reason, and you want to get e.g. a
resume out fast.

Erik

Re: Muttrc example needed POP3/SMTP

[sunrise]

Thank you for all your replies and suggestions - they were greatly appreciated.

I am using dial-up email and would like to setup a cron job to 1) Dial in to 
the server,
2) Retrieve any messages (probably via getmail4 or similar) and 3) Send any 
queued
messages. So I'm looking into using msmtpq (a script for use with msmtp) with 
mutt.

Are there any suggestions for which MTA would be most suitable for this purpose 
(sending
queued messages on a system that is not online when composing messages)?

Thanks.



On Fri, 3 Feb 2017 21:31:33 +1100
Erik Christiansen  wrote:

>On 03.02.17 09:47, Chris Green wrote:
>> ... and if you're on a distribution where Postfix is the standard
>> that's also pretty easy to set up.  I personally prefer Postfix from
>> the ease of configuration point of view.
>
>+1
>
>(It also has a Sendmail compatibility interface, so that we old folks
>could move over painlessly. But now my muscle memory is Postfix oriented.)
>
>> I use Postfix and both send and receive mail using SMTP as my desktop
>> machine is on all the time.  Thus I have no need for POP3/IMAP mail
>> collection.
>
>As my machine is shut down each night, I use fetchmail to bring mail in
>via POP3. It has served me well for several decades now.
>
>Erik

Re: Muttrc example needed POP3/SMTP

[sunrise]

Thanks for your input; I will definitely be looking at the possibility of
using offlineimap. I am on a dial up connection - does offlineimap handle 
dropped
connections well?

Thanks again.


On Fri, 3 Feb 2017 21:57:21 + (UTC)
Arkadiusz Drabczyk <arkadi...@drabczyk.org> wrote:

>On 2017-02-03, sunrise <sunr...@emypeople.net> wrote:
>> I would like to start using mutt but am somewhat intimidated by all the 
>> possible
>> options in the muttrc config file. Would someone be willing to provide me 
>> with a basic
>> muttrc I could use to get started?
>>
>> Here is what I'm looking for:
>>
>> * POP3 (one provider) for retrieving messages
>
>I'd just like to add that these days you should give IMAP a try - I
>find better than POP3 because it automatically synchronizes
>everything.  It's easy to use with mutt as well.
>
>For example, I use offlineimap as the IMAP client on my Slackware box
>and K9Mail e-mail client on my phone.  When I mark a message as read
>on my phone it's automatically marked as read when downloaded with
>offlineimap in mutt, when I send a message on either device it's
>automatically shown in Sent folder on both devices, and when I move a
>a message to a given folder or delete a message it's automatically
>synchronized on both devices.  It's very convenient, especially if get
>a lot of mail.

Re: Muttrc example needed POP3/SMTP

[Arkadiusz Drabczyk]

On 2017-02-03, sunrise <sunr...@emypeople.net> wrote:
> I would like to start using mutt but am somewhat intimidated by all the 
> possible options
> in the muttrc config file. Would someone be willing to provide me with a 
> basic muttrc I
> could use to get started?
>
> Here is what I'm looking for:
>
> * POP3 (one provider) for retrieving messages

I'd just like to add that these days you should give IMAP a try - I
find better than POP3 because it automatically synchronizes
everything.  It's easy to use with mutt as well.

For example, I use offlineimap as the IMAP client on my Slackware box
and K9Mail e-mail client on my phone.  When I mark a message as read
on my phone it's automatically marked as read when downloaded with
offlineimap in mutt, when I send a message on either device it's
automatically shown in Sent folder on both devices, and when I move a
a message to a given folder or delete a message it's automatically
synchronized on both devices.  It's very convenient, especially if get
a lot of mail.
-- 
Arkadiusz Drabczyk <arkadi...@drabczyk.org>

Re: Muttrc example needed POP3/SMTP

[Erik Christiansen]

On 03.02.17 09:47, Chris Green wrote:
> ... and if you're on a distribution where Postfix is the standard
> that's also pretty easy to set up.  I personally prefer Postfix from
> the ease of configuration point of view.

+1

(It also has a Sendmail compatibility interface, so that we old folks
could move over painlessly. But now my muscle memory is Postfix oriented.)

> I use Postfix and both send and receive mail using SMTP as my desktop
> machine is on all the time.  Thus I have no need for POP3/IMAP mail
> collection.

As my machine is shut down each night, I use fetchmail to bring mail in
via POP3. It has served me well for several decades now.

Erik

Re: Muttrc example needed POP3/SMTP

[Chris Green]

On Fri, Feb 03, 2017 at 12:11:10AM -0600, rlhar...@oplink.net wrote:
> On Thu, February 2, 2017 10:37 pm, sunrise wrote:
> > I already had getmail set up but didn't have msmtp installed.
> 
> If exim4 is installed and configured, there is no need for msmtp, unless you
> need the profile feature of msmtp which gives you the ability to send
> messages through any of a number of smarthosts.
> 
> Some may argue that exim4 is overkill for most users, but the package is
> mainstream, proven, and very capable; and, with the script provided by the
> Debian maintainer, configuration of exim4 is simple and quick.
> 
... and if you're on a distribution where Postfix is the standard
that's also pretty easy to set up.  I personally prefer Postfix from
the ease of configuration point of view.

I use Postfix and both send and receive mail using SMTP as my desktop
machine is on all the time.  Thus I have no need for POP3/IMAP mail
collection.

-- 
Chris Green

Re: Muttrc example needed POP3/SMTP

[rlharris]

On Thu, February 2, 2017 10:37 pm, sunrise wrote:
> I already had getmail set up but didn't have msmtp installed.

If exim4 is installed and configured, there is no need for msmtp, unless you
need the profile feature of msmtp which gives you the ability to send
messages through any of a number of smarthosts.

Some may argue that exim4 is overkill for most users, but the package is
mainstream, proven, and very capable; and, with the script provided by the
Debian maintainer, configuration of exim4 is simple and quick.

RH

Re: Muttrc example needed POP3/SMTP

[rlharris]

On Thu, February 2, 2017 10:37 pm, sunrise wrote:
> Thanks a lot for both replies; I feel I am now several steps closer to
> getting a working system. I already had getmail set up but didn't have
> msmtp installed.

The Mail Transfer Agent (on Debian, typically Exim4) handles outgoing
messages on the local machine; these messages are sent to the mail server
of your Internet Service Provider (ISP), which acts as a "smarthost".

If you configure Exim4 (and you should, using the configuration dialogue
provided by the Debian maintainer), you specify the URL of the smarthost
(such as "mail.myisp.net"), the address which is to appear on outgoing
messages ("myn...@myisp.net"), and the password which the smarthost
requires for authentication.  For this, see the command "dpkg-reconfigure
exim4-config" and the files "/etc/email-addresses" and
"/etc/exim4/password-client".



> One question I still have is: What are the advantages of using getmail
> and msmtp versus using mutt's built in POP3 and SMTP capabilities?

The author and maintainer of getmail has taken great pains to ensure that
getmail4 works reliably even if a POP3 server is "broken" (and that often
is the case).  With a properly-configured getmail, you pretty much are
assured of never losing a message.  In salvaging messages from a POP3
server, I personally have used getmail4 to download hundreds of thousands
of messages in a single marathon session running in excess of a day.

And, as I previously mentioned, you can use the combination of getmail4
and maildrop to sort incoming messages in any manner and to any degree you
wish, triggering periodic fetches with a cron job, even if no mutt session
is running.  And then, when you do start mutt, you can view any of the
sort categories independently of the others. Thus, if you are pressed for
time, you can look only at messages of important categories, without the
necessity of wading message-by-message through stuff which is not urgent.

Also, if you do not have 24/7 access to the Internet, delegating
downloading (and sorting, if desired) allows you to go on-line, get your
messages while you browse or do other on-line work, then go offline and
read the messages with mutt.

But those who are accustomed to the Window$ way of doing things may prefer
a monolithic mail client which can fetch directly from a POP3 server and
send directly to a smarthost.

RH

Re: Muttrc example needed POP3/SMTP

[dale]

On 2/2/17 9:44 PM, sunrise wrote:

I would like to start using mutt but am somewhat intimidated by all the 
possible options
in the muttrc config file. Would someone be willing to provide me with a basic 
muttrc I
could use to get started?

Here is what I'm looking for:

* POP3 (one provider) for retrieving messages
* SMTP for sending
* Mail stored in maildir format in $HOME

Using Mutt 1.5.21

Thanks!




I think there is an example .muttrc in /etc/mutt

--
dale | http://www.dalekelly.org

Re: Muttrc example needed POP3/SMTP

[sunrise]

On Fri, 3 Feb 2017 04:15:23 +0100
Francesco Ariis <fa...@ariis.it> wrote:

>On Thu, Feb 02, 2017 at 08:44:34PM -0600, sunrise wrote:
>> I would like to start using mutt but am somewhat intimidated by all the 
>> possible
>> options in the muttrc config file. Would someone be willing to provide me 
>> with a basic
>> muttrc I could use to get started?
>
>This is what I have:
>
>set mbox_type=Maildir
>set folder="~/mail"
>set mask="!^\\.[^.]"
>
>mailboxes "+inbox" # ~/mail/inbox
>
>set record="+sent" # ~/mail/sent
>set postponed="+drafts" # etc.
>set trash="+trash"
>
>set realname="Plato"
>
>set envelope_from=yes
>set sendmail="msmtp -C /home/f/cfg/msmtp/msmtpall"
># msmtp is small, efficient and easy to configure
>
>macro generic \e0 'bash -ic "k echo Checking mail...; getmail -g
>~/cfg/getmail -r getmailconf; echo over"'
># alt-0 to download messages
>
>
>Mutt is a client, so you will have to configure msmtp and getmail yourself
>(they are easy enough). If you need more help fire again in the mailing
>list and please consider updating the wiki with your use case when
>you succeed.


Thanks a lot for both replies; I feel I am now several steps closer to getting 
a working
system. I already had getmail set up but didn't have msmtp installed.

One question I still have is: What are the advantages of using getmail and 
msmtp versus
using mutt's built in POP3 and SMTP capabilities?

Thank you for your time.

Re: Muttrc example needed POP3/SMTP

[Francesco Ariis]

On Thu, Feb 02, 2017 at 08:44:34PM -0600, sunrise wrote:
> I would like to start using mutt but am somewhat intimidated by all the 
> possible options
> in the muttrc config file. Would someone be willing to provide me with a 
> basic muttrc I
> could use to get started?

This is what I have:

set mbox_type=Maildir
set folder="~/mail"
set mask="!^\\.[^.]"

mailboxes "+inbox" # ~/mail/inbox

set record="+sent" # ~/mail/sent
set postponed="+drafts" # etc.
set trash="+trash"

set realname="Plato"

set envelope_from=yes
set sendmail="msmtp -C /home/f/cfg/msmtp/msmtpall"
# msmtp is small, efficient and easy to configure

macro generic \e0 'bash -ic "k echo Checking mail...; getmail -g 
~/cfg/getmail -r getmailconf; echo over"'
# alt-0 to download messages


Mutt is a client, so you will have to configure msmtp and getmail yourself
(they are easy enough). If you need more help fire again in the mailing
list and please consider updating the wiki with your use case when
you succeed.

Re: Muttrc example needed POP3/SMTP

[rlharris]

On Thu, February 2, 2017 8:44 pm, sunrise wrote:
> I would like to start using mutt but am somewhat intimidated by all the
> possible options in the muttrc config file. Would someone be willing to
> provide me with a basic muttrc I could use to get started?

That's why they make search engines; you can find dozens of muttrc files,
and any number of muttrc tutorials.

You might consider using getmail4 for POP3?  getmail4 is reliable and easy
to configure, and by using getmail4 you simplify the configuration of
muttrc.

Later you can add maildrop to sort into categories messages retrieved by
getmail4 -- it is a nice combination.

RH

Muttrc example needed POP3/SMTP

[sunrise]

I would like to start using mutt but am somewhat intimidated by all the 
possible options
in the muttrc config file. Would someone be willing to provide me with a basic 
muttrc I
could use to get started?

Here is what I'm looking for:

* POP3 (one provider) for retrieving messages
* SMTP for sending
* Mail stored in maildir format in $HOME

Using Mutt 1.5.21

Thanks!

pass different "gpg --encrypt-to" when using different .muttrc ?

[Guy Gold]

Hi list,
I have this simple issue which has proven to be not-so-simple :)

I have "encrypt-to" set in ~/.gnupg/gpg.conf, which enables me to
decrypt my own sent email. 

However, I also have a .muttrc for gmail, and I'd like to
"encrypt-to" my sent gmail with a different key than the one
specified in ~/.gnupg/gpg.conf

I've read there should be a patch enabling:
"pgp_encrypt_self"  - but, this is not legal in my muttrc. 

Is there any way to pass a different "encrypt-to" to gpg
according to the .muttrc I'm running ?

(I've tried using gpg.rc - but then too, 
ened up with the same issue- one default key used.) 

Thank you. 

-- 
Guy Gold
Cambridge, Massachusetts

Re: How to debug muttrc? (for signature)

[Patrick Shanahan]

* Peter Terpstra <peter.terpst...@gmail.com> [08-15-16 17:11]:
> 
> In a reply you need this one set:
> set sig_on_top
> 
> Then it will be placed above the quoted text.
> 
> Mutt will find it if this works too:
> cd ~ && cat ~/.signature
> 
> Kindly,
> 
> Peter
> 
>  ~ pENG yU <pengyu...@gmail.com> [2016-08-14 10:40:24 -0500]:
> 
> > hI, i HAVE THE FOLLOWING LINE IN MY MUTTRC. bUT NO SIGNATURE IS
> > GENERATED IN THE EMAIL (i ONLY TESTED MUTT ON THE COMMAND LINE).
> > 
> > SET signature="~/.signature"
> > 
> > Does anybody know how to debug muttrc to understand why no signature
> > is included in the generated emails?
> > 
> > -- 
> > Regards,
> > Peng

Why would one set "sig_on_top", you reply as you read so context is
preserved, "don't you"?

really!  :(
-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535@ http://linuxcounter.net

Re: How to debug muttrc? (for signature)

[Peter Terpstra]

In a reply you need this one set:
set sig_on_top 


Then it will be placed above the quoted text.

Mutt will find it if this works too:
cd ~ && cat ~/.signature

Kindly,

Peter

 ~ pENG yU <pengyu...@gmail.com> [2016-08-14 10:40:24 -0500]:


hI, i HAVE THE FOLLOWING LINE IN MY MUTTRC. bUT NO SIGNATURE IS
GENERATED IN THE EMAIL (i ONLY TESTED MUTT ON THE COMMAND LINE).

SET signature="~/.signature"

Does anybody know how to debug muttrc to understand why no signature
is included in the generated emails?

--
Regards,
Peng

How to debug muttrc? (for signature)

[Peng Yu]

Hi, I have the following line in my muttrc. But no signature is
generated in the email (I only tested mutt on the command line).

set signature="~/.signature"

Does anybody know how to debug muttrc to understand why no signature
is included in the generated emails?

-- 
Regards,
Peng

Re: How to debug muttrc? (for signature)

[Peng Yu]

BTW, I use the follow command to send the email.

mutt -s 'my subject' pengyu...@gmail.com <<< my_body

On Sun, Aug 14, 2016 at 10:40 AM, Peng Yu <pengyu...@gmail.com> wrote:
> Hi, I have the following line in my muttrc. But no signature is
> generated in the email (I only tested mutt on the command line).
>
> set signature="~/.signature"
>
> Does anybody know how to debug muttrc to understand why no signature
> is included in the generated emails?
>
> --
> Regards,
> Peng



-- 
Regards,
Peng

Re: no MUTTRC environment variable?

[Xu Wang]

On Mon, Jul 4, 2016 at 12:35 AM,  <c...@zip.com.au> wrote:
> On 03Jul2016 00:50, Xu Wang <xuwang...@gmail.com> wrote:
>>
>> Thank you very much for the replies, Will and Cameron.
>>
>> Yes, these workarounds work fine for my personal setup. However, I am
>> working on scripts that I would like to release for other users to
>> use. I do not want to require other users to refactor their .muttrcs
>> just to use the scripts. Creating user-friendsly scripts is what
>> motivates me.
>
>
> And fair enough too. I suspect then that you must explicitly invoke mutt as
> needed. This:
>
>  mutt -F /dev/null -e 'source muttrc1' -e 'source muttrc2' ...
>
> is probably the cleanest way to invoke mutt without reliance on the user's
> .muttrc, and to source whatever config you intend. You can add the "-n"
> option to also bypass and system muttrc file.
>
> Does this help?
>
> Cheers,
> Cameron Simpson <c...@zip.com.au>

Thank you Cameron. I will think about this option and test it. I
highly appreciate your time and thoughts.

Kind regards,

Xu

Re: no MUTTRC environment variable?

[cs]

On 03Jul2016 00:50, Xu Wang <xuwang...@gmail.com> wrote:

Thank you very much for the replies, Will and Cameron.

Yes, these workarounds work fine for my personal setup. However, I am
working on scripts that I would like to release for other users to
use. I do not want to require other users to refactor their .muttrcs
just to use the scripts. Creating user-friendsly scripts is what
motivates me.


And fair enough too. I suspect then that you must explicitly invoke mutt as 
needed. This:


 mutt -F /dev/null -e 'source muttrc1' -e 'source muttrc2' ...

is probably the cleanest way to invoke mutt without reliance on the user's 
.muttrc, and to source whatever config you intend. You can add the "-n" option 
to also bypass and system muttrc file.


Does this help?

Cheers,
Cameron Simpson <c...@zip.com.au>

Re: [SPAM?] Re: [SPAM?] Re: no MUTTRC environment variable?

[Xu Wang]

On Sat, Jul 2, 2016 at 8:44 PM, Will Yardley
<mutt-us...@veggiechinese.net> wrote:
> On Sat, Jul 02, 2016 at 08:13:55PM -0400, Xu Wang wrote:
>> On Thu, Jun 30, 2016 at 9:10 PM, Will Yardley
>> <mutt-us...@veggiechinese.net> wrote:
>> > On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote:
>
>> >> I have read the environment variables section in 'man mutt' and there
>> >> does not seem to be a MUTTRC environment variable. One can set using
>> >> -F option but sometime environment variable is nice.
>> >
>> > What kind of uses did you have in mind?
>> >
>> > You can use environment variables in config files, so you can always
>> > work around this for most of the use cases I can think of by having
>> >
>> > source ~/.muttrc-$FOO
>> > in ~/.muttrc, and then define $FOO.
>
>> For me it is not ideal because when I execute
>> source ~/.muttrc-$FOO
>> then the rest of the .muttrc is still processed. I would like to
>> process only ~/.muttrc-$FOO.
>> I hope that has sense.
>
> I get what you're saying. But if I'm understanding what you're trying to
> do, you should be able to have .muttrc *only* contain:
>
> source ~/.muttrc-$FOO
>
> that is, it would be a meta-muttrc. You can still source other files
> from .muttrc-$FOO.
>
> w
>

Thank you very much for the replies, Will and Cameron.

Yes, these workarounds work fine for my personal setup. However, I am
working on scripts that I would like to release for other users to
use. I do not want to require other users to refactor their .muttrcs
just to use the scripts. Creating user-friendsly scripts is what
motivates me.

Kind regards,

Xu

Re: [SPAM?] Re: no MUTTRC environment variable?

[Xu Wang]

On Sun, Jul 3, 2016 at 12:43 AM, Jon LaBadie <mut...@jgcomp.com> wrote:
>> > On Thu, Jun 30, 2016 at 08:02:38PM -0400, Xu Wang wrote:
>> >>
>> >> I have read the environment variables section in 'man mutt' and there
>> >> does not seem to be a MUTTRC environment variable. One can set using
>> >> -F option but sometime environment variable is nice.
>> >>
>> >> Can someone confirm this is correct? Is there a reason for this?
>> >
>
> How about implementing your own with a mutt alias?
>
>
>   alias mutt='mutt ${MUTTRC:+-F ${MUTTRC}}'
>
> If MUTTRC is not set, or is the empty string, this becomes
> just "mutt" and ~/.muttrc will be used as normal.  But if
> MUTTRC is set it becomes "mutt -F ${MUTTRC}" and uses the
> rc file specified in the variable.
>
> Jon
> --
> Jon H. LaBadie j...@jgcomp.com
>  11226 South Shore Rd.  (703) 787-0688 (H)
>  Reston, VA  20190  (703) 935-6720 (C)

Interesting idea, Jon! I will consider this for my personal setup.

Kind regards,

Xu