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

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 

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 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 = 

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
 # 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..
 .^[[37m^[[40m^[[K^[(B^[[m^[[39;49m^[[37m^[[4
 0m
 Looking up 

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

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..

.^[[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...
   

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!  
>