Re: Unexplained mutt error

2022-02-25 Thread Jon LaBadie

On Fri, Feb 25, 2022 at 06:25:01PM -0600, Ranjan Maitra wrote:

On Fri Feb25'22 04:31:32PM, Jon LaBadie wrote:

From: Jon LaBadie 
Date: Fri, 25 Feb 2022 16:31:32 -0500
To: mutt-users@mutt.org
Subject: Re: Unexplained mutt error

On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra wrote:
>
> My apologies, I guess I was not at all clear in my question. I want a
> hook which if I press "r" would give me a query about if I want to
> answer to the list or reply to the sender.
>

Doesn't the "reply_to" setting allow you to do that already.



It does? I have:

set reply_to=yes

I had no idea about this and I looked it up. So I guess I should put
this as a hook inside my list folders. I will try that, thanks!



Have you overlooked the "Type:" for reply_to?  It is type "quadoption".

So instead of just settings yes and no, I think there are 2 additional
settings, "ask-yes" and "ask-no".  Again, I think the "-yes" and "-no"
are the defaults when you just press Enter as your answer.

Jon

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



Re: Unexplained mutt error

2022-02-25 Thread Ranjan Maitra
On Fri Feb25'22 04:31:32PM, Jon LaBadie wrote:
> From: Jon LaBadie 
> Date: Fri, 25 Feb 2022 16:31:32 -0500
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra wrote:
> >
> > My apologies, I guess I was not at all clear in my question. I want a
> > hook which if I press "r" would give me a query about if I want to
> > answer to the list or reply to the sender.
> >
>
> Doesn't the "reply_to" setting allow you to do that already.
>

It does? I have:

set reply_to=yes

I had no idea about this and I looked it up. So I guess I should put this as a 
hook inside my list folders. I will try that, thanks!

Ranjan


Re: Unexplained mutt error

2022-02-25 Thread Jon LaBadie

On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra wrote:


My apologies, I guess I was not at all clear in my question. I want a
hook which if I press "r" would give me a query about if I want to
answer to the list or reply to the sender.



Doesn't the "reply_to" setting allow you to do that already.

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



Re: Unexplained mutt error

2022-02-25 Thread Ranjan Maitra
On Fri Feb25'22 01:29:14PM, Kurt Hackenberg wrote:
> From: Kurt Hackenberg 
> Date: Fri, 25 Feb 2022 13:29:14 -0500
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> On 2022/02/25 10:53, Ranjan Maitra wrote:
>
> > Regardless, actually I think that all I would be happy with would be a 
> > query or something that alerts me to the fact that I am potentially writing 
> > to an individual address (or a list) (for when I am  on a list, but not in 
> > general, because then I start to blindly accept because most email is not 
> > to a list).
>
> It's possible to configure Mutt so that its index tells you that a message
> came from a list. The default index format includes %L, so all you'd have to
> do is use "subscribe" to tell Mutt what lists you're subscribed to. Or
> there's $auto_subscribe, to do that automatically for lists that announce
> themselves.
>
> With the index telling you the message came from a list, then you would know
> to reply with 'L'.
>
> You could try this to see if you like it by just adding this to your
> .muttrc:
> set auto_subscribe=yes
>
> This section of the manual describes what Mutt can do with mailing lists:
> <http://mutt.org/doc/manual/#using-lists>


My apologies, I guess I was not at all clear in my question. I want a hook 
which if I press "r" would give me a query about if I want to answer to the 
list or reply to the sender.

Thanks,
Ranjan


Re: Unexplained mutt error

2022-02-25 Thread Kurt Hackenberg

On 2022/02/25 10:53, Ranjan Maitra wrote:


Regardless, actually I think that all I would be happy with would be a query or 
something that alerts me to the fact that I am potentially writing to an 
individual address (or a list) (for when I am  on a list, but not in general, 
because then I start to blindly accept because most email is not to a list).


It's possible to configure Mutt so that its index tells you that a 
message came from a list. The default index format includes %L, so all 
you'd have to do is use "subscribe" to tell Mutt what lists you're 
subscribed to. Or there's $auto_subscribe, to do that automatically for 
lists that announce themselves.


With the index telling you the message came from a list, then you would 
know to reply with 'L'.


You could try this to see if you like it by just adding this to your 
.muttrc:

set auto_subscribe=yes

This section of the manual describes what Mutt can do with mailing lists:



Re: Unexplained mutt error

2022-02-25 Thread Patrick Shanahan
* Ranjan Maitra  [02-25-22 10:54]:
> On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote:
> > From: Charles Cazabon 
> > Date: Fri, 25 Feb 2022 07:00:05 -0600
> > To: mutt-users@mutt.org
> > Subject: Re: Unexplained mutt error
> >
> > Kurt Hackenberg  wrote:
> > > On 2022/02/22 18:10, Ranjan Maitra wrote:
> > >
> > > > As an aside, for others: is there, in .muttrc a way to set things such
> > > > that hitting "r" would automatically switch to reply list ("L") for
> > > > specific folders?
> > [...]
> > > It's possible to change key bindings, so maybe you could do that on the 
> > > fly,
> > > conditionally, for certain folders...or maybe you could write some tricky
> > > macro...but I think probably those are both bad ideas. I think you'd do
> > > better to just always use 'L' to reply to a list.
> >
> > That's the right solution, but I've also seen people configure their MDA to
> > add a Reply-To: header to incoming list messages that don't have them.  
> > Just a
> > thought.
> >
> 
> I see: I use fetchmail and then procmail for fetching email. So, would this 
> be done through fetchmail or procmail?
> 

If you *must* add a header, procmail would be the app.

> Regardless, actually I think that all I would be happy with would be a query 
> or something that alerts me to the fact that I am potentially writing to an 
> individual address (or a list) (for when I am  on a list, but not in general, 
> because then I start to blindly accept because most email is not to a list).
> 
> Any thoughts on if this is possible?

man muttrc

specifically look at 
  lists  [  ... ]
  
and "subscribe"
  
-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet oftc
What sort of day was it?  A day like all days, filled with 
those events that alter and illuminate our times... 


Re: Unexplained mutt error

2022-02-25 Thread Charles Cazabon
Ranjan Maitra  wrote:
> On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote:
> >
> > That's the right solution, but I've also seen people configure their MDA
> > to add a Reply-To: header to incoming list messages that don't have them.
> 
> I see: I use fetchmail and then procmail for fetching email. So, would this
> be done through fetchmail or procmail?

Here procmail is your MDA.  I know it can do such things, but don't ask me
how.

> Regardless, actually I think that all I would be happy with would be a query
> or something that alerts me to the fact that I am potentially writing to an
> individual address (or a list) (for when I am  on a list, but not in
> general, because then I start to blindly accept because most email is not to
> a list).
> 
> Any thoughts on if this is possible?

There's a number of ways.  If your list mail is in separate folders, you can
use a folder hook to just disable the (r) function, or to remap it to
list-reply.

Charles
-- 
---
Charles Cazabon
GPL'ed software available at:   http://pyropus.ca/software/
---


Re: Unexplained mutt error

2022-02-25 Thread Ranjan Maitra
On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote:
> From: Charles Cazabon 
> Date: Fri, 25 Feb 2022 07:00:05 -0600
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> Kurt Hackenberg  wrote:
> > On 2022/02/22 18:10, Ranjan Maitra wrote:
> >
> > > As an aside, for others: is there, in .muttrc a way to set things such
> > > that hitting "r" would automatically switch to reply list ("L") for
> > > specific folders?
> [...]
> > It's possible to change key bindings, so maybe you could do that on the fly,
> > conditionally, for certain folders...or maybe you could write some tricky
> > macro...but I think probably those are both bad ideas. I think you'd do
> > better to just always use 'L' to reply to a list.
>
> That's the right solution, but I've also seen people configure their MDA to
> add a Reply-To: header to incoming list messages that don't have them.  Just a
> thought.
>

I see: I use fetchmail and then procmail for fetching email. So, would this be 
done through fetchmail or procmail?

Regardless, actually I think that all I would be happy with would be a query or 
something that alerts me to the fact that I am potentially writing to an 
individual address (or a list) (for when I am  on a list, but not in general, 
because then I start to blindly accept because most email is not to a list).

Any thoughts on if this is possible?

Many thanks and best wishes,
Ranjan




Re: Unexplained mutt error

2022-02-25 Thread Charles Cazabon
Kurt Hackenberg  wrote:
> On 2022/02/22 18:10, Ranjan Maitra wrote:
> 
> > As an aside, for others: is there, in .muttrc a way to set things such
> > that hitting "r" would automatically switch to reply list ("L") for
> > specific folders?
[...]
> It's possible to change key bindings, so maybe you could do that on the fly,
> conditionally, for certain folders...or maybe you could write some tricky
> macro...but I think probably those are both bad ideas. I think you'd do
> better to just always use 'L' to reply to a list.

That's the right solution, but I've also seen people configure their MDA to
add a Reply-To: header to incoming list messages that don't have them.  Just a
thought.

Charles
-- 
---
Charles Cazabon
GPL'ed software available at:   http://pyropus.ca/software/
---


Re: Unexplained mutt error

2022-02-24 Thread Kurt Hackenberg

On 2022/02/22 18:10, Ranjan Maitra wrote:


As an aside, for others: is there, in .muttrc a way to set things such that hitting "r" 
would automatically switch to reply list ("L") for specific folders?

I have seen that for some list mail, "r" responds to list, and for others, to 
the sender.


Some mailing lists add a Reply-To: header with the list address; that 
would make 'r' send to the list address instead of to the original 
sender. Opinions are mixed on whether it's a good idea for lists to do 
that. You could check whether that header exists in your list messages 
where you see that behavior.


It's possible to change key bindings, so maybe you could do that on the 
fly, conditionally, for certain folders...or maybe you could write some 
tricky macro...but I think probably those are both bad ideas. I think 
you'd do better to just always use 'L' to reply to a list.


This section of the manual describes what Mutt can do with mailing lists:



Re: Unexplained mutt error

2022-02-22 Thread Ranjan Maitra
I think the OPs problem is with sending, not accessing email.

Ranjan

On Wed Feb23'22 02:29:12AM, Sam Kuper wrote:
> From: Sam Kuper 
> Date: Wed, 23 Feb 2022 02:29:12 +
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> On Tue, Feb 22, 2022 at 04:40:06PM -0600, Ion wrote:
> > Thanks to all of you for trying to solve my problem. But I have been
> > trying to setup mutt for nine days now.  I have followed all your
> > advice and instructions to the best of my ability, to no avail.  [...]
> > Much as I want to use a CLI client, Thunderbird, Claws, and Evolution
> > were able to connect me within 15 minutes ...
>
> Have you tried using Getmail (or Fetchmail, or mbsync, or OfflineIMAP,
> etc - i.e. an MRA (mail retrieval agent)) to get a copy of your mail
> from your Fastmail server to a local Mbox or Maildir?
>
> If you can get that working, then you can just point Mutt at the
> resulting Mbox or Maildir on your local drive, and read your mail that
> way:
>
> mutt -R -f /path/to/local/mbox/or/maildir
>
> I.e. rely only on Mutt's MUA functionality, not its MRA functionality.
>
> You might even be able to point Mutt at wherever Thunderbird keeps your
> local mailstore, depending on how you have Thunderbird configured.  I.e.
> let Thunderbird act as your MRA and use Mutt as your MUA:
>
> mutt -R -f /path/to/local/Thunderbird/mail/store
>
> Don't give up!
>
> --
> 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: Unexplained mutt error

2022-02-22 Thread Sam Kuper
On Tue, Feb 22, 2022 at 04:40:06PM -0600, Ion wrote:
> Thanks to all of you for trying to solve my problem. But I have been
> trying to setup mutt for nine days now.  I have followed all your
> advice and instructions to the best of my ability, to no avail.  [...]
> Much as I want to use a CLI client, Thunderbird, Claws, and Evolution
> were able to connect me within 15 minutes ...

Have you tried using Getmail (or Fetchmail, or mbsync, or OfflineIMAP,
etc - i.e. an MRA (mail retrieval agent)) to get a copy of your mail
from your Fastmail server to a local Mbox or Maildir?

If you can get that working, then you can just point Mutt at the
resulting Mbox or Maildir on your local drive, and read your mail that
way:

mutt -R -f /path/to/local/mbox/or/maildir

I.e. rely only on Mutt's MUA functionality, not its MRA functionality.

You might even be able to point Mutt at wherever Thunderbird keeps your
local mailstore, depending on how you have Thunderbird configured.  I.e.
let Thunderbird act as your MRA and use Mutt as your MUA:

mutt -R -f /path/to/local/Thunderbird/mail/store

Don't give up!

-- 
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: Unexplained mutt error

2022-02-22 Thread Ranjan Maitra


Can't type, sorry. No apostrophe at the end.

> This got mangled.

set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"; set ssl_force_tls 
= yes; set ssl_starttls = yes

or

 set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"
 set ssl_force_tls = yes
 set ssl_starttls = yes

Hope this works for you,
Ranjan


Re: Unexplained mutt error

2022-02-22 Thread Ranjan Maitra
My apologies:


> For me, the magic was the equivalent of what for you would be:
>
> set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465" set 
> ssl_force_tls = yes set ssl_starttls = yes'

This got mangled.

set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"; set ssl_force_tls 
= yes; set ssl_starttls = yes'

or

 set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"
 set ssl_force_tls = yes
 set ssl_starttls = yes'

btw, if your password has special characters, you may need to have the escape 
character sequence in place. Example: "\$" for "$".


Ranjan



>

> Of course, getting the password, etc right.
>
> As an aside, for others: is there, in .muttrc a way to set things such that 
> hitting "r" would automatically switch to reply list ("L") for specific 
> folders?
>
> I have seen that for some list mail, "r" responds to list, and for others, to 
> the sender.
>
> Many thanks and best wishes,
> Ranjan
>
>
>
>
> On Tue Feb22'22 04:40:06PM, Ion wrote:
> > From: Ion 
> > Date: Tue, 22 Feb 2022 16:40:06 -0600
> > To: mutt-users@mutt.org
> > Subject: Re: Unexplained mutt error
> >
> > Thanks to all of you for trying to solve my problem. But I have been
> > trying to setup mutt for nine days now. I have followed all your advice
> > and instructions to the best of my ability, to no avail. My E-mail
> > providers don't seem to know that CLI clients exist. They keep asking me
> > to take a snapshot of the preferences menu. Much as I want to use a CLI
> > client, Thunderbird, Claws, and Evolution were able to connect me within
> > 15 minutes so I will go back to Thunderbird. And truthfully it's
> > Fastmail that's the problem as other accounts work as expected.
> >
> > Thanks again.
> >
> > On 22/02/2022 16:15, Kevin J. McCarthy wrote:
> > > On Tue, Feb 22, 2022 at 02:34:05PM -0600, Ranjan Maitra wrote:
> > > > On Tue Feb22'22 02:06:57PM, Ion wrote:
> > > > > As instructed I changed it to...
> > > > >
> > > > > set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"
> > > > >
> > > > > and also tried
> > > > >
> > > > > set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"
> > > > >
> > > >
> > > > set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"
> > >
> > > Thanks Ranjan - that's right.  Remember port 465 uses smtps://
> > >
> > > > > both produced "Invalid SMTP URL: smtp.fastmail.com:465"
> > >
> > > Check your muttrc to make sure you don't have the value specified
> > > twice or something.  That error message prints out the full value of
> > > $smtp_url, so somehow Mutt has the value minus the
> > > 'smtps://ionm...@eml.cc@' prefix stored in $smtp_url.
> > >
> > > You can also check the value at runtime by typing ':set ?smtp_url' and
> > > hitting return.
> > >


Re: Unexplained mutt error

2022-02-22 Thread Ranjan Maitra
Sorry for not recalling this from your earlier e-mail, but what exactly were 
the claws-mail settings?

Did you make sure about smtps? In my limited experience, though mail providers 
talk about smtp and 587 port, many of them only work with smtps and 465.

I moved from sylpheed to mutt, and the helpful people here and looking around 
got me going eventually.

For me, the magic was the equivalent of what for you would be:

set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465" set ssl_force_tls 
= yes set ssl_starttls = yes'

Of course, getting the password, etc right.

As an aside, for others: is there, in .muttrc a way to set things such that 
hitting "r" would automatically switch to reply list ("L") for specific folders?

I have seen that for some list mail, "r" responds to list, and for others, to 
the sender.

Many thanks and best wishes,
Ranjan




On Tue Feb22'22 04:40:06PM, Ion wrote:
> From: Ion 
> Date: Tue, 22 Feb 2022 16:40:06 -0600
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> Thanks to all of you for trying to solve my problem. But I have been
> trying to setup mutt for nine days now. I have followed all your advice
> and instructions to the best of my ability, to no avail. My E-mail
> providers don't seem to know that CLI clients exist. They keep asking me
> to take a snapshot of the preferences menu. Much as I want to use a CLI
> client, Thunderbird, Claws, and Evolution were able to connect me within
> 15 minutes so I will go back to Thunderbird. And truthfully it's
> Fastmail that's the problem as other accounts work as expected.
>
> Thanks again.
>
> On 22/02/2022 16:15, Kevin J. McCarthy wrote:
> > On Tue, Feb 22, 2022 at 02:34:05PM -0600, Ranjan Maitra wrote:
> > > On Tue Feb22'22 02:06:57PM, Ion wrote:
> > > > As instructed I changed it to...
> > > >
> > > > set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"
> > > >
> > > > and also tried
> > > >
> > > > set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"
> > > >
> > >
> > > set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"
> >
> > Thanks Ranjan - that's right.  Remember port 465 uses smtps://
> >
> > > > both produced "Invalid SMTP URL: smtp.fastmail.com:465"
> >
> > Check your muttrc to make sure you don't have the value specified
> > twice or something.  That error message prints out the full value of
> > $smtp_url, so somehow Mutt has the value minus the
> > 'smtps://ionm...@eml.cc@' prefix stored in $smtp_url.
> >
> > You can also check the value at runtime by typing ':set ?smtp_url' and
> > hitting return.
> >


Re: Unexplained mutt error

2022-02-22 Thread Ion

Thanks to all of you for trying to solve my problem. But I have been
trying to setup mutt for nine days now. I have followed all your advice
and instructions to the best of my ability, to no avail. My E-mail
providers don't seem to know that CLI clients exist. They keep asking me
to take a snapshot of the preferences menu. Much as I want to use a CLI
client, Thunderbird, Claws, and Evolution were able to connect me within
15 minutes so I will go back to Thunderbird. And truthfully it's
Fastmail that's the problem as other accounts work as expected.

Thanks again.

On 22/02/2022 16:15, Kevin J. McCarthy wrote:

On Tue, Feb 22, 2022 at 02:34:05PM -0600, Ranjan Maitra wrote:

On Tue Feb22'22 02:06:57PM, Ion wrote:

As instructed I changed it to...

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"

and also tried

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"



set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"


Thanks Ranjan - that's right.  Remember port 465 uses smtps://


both produced "Invalid SMTP URL: smtp.fastmail.com:465"


Check your muttrc to make sure you don't have the value specified
twice or something.  That error message prints out the full value of
$smtp_url, so somehow Mutt has the value minus the
'smtps://ionm...@eml.cc@' prefix stored in $smtp_url.

You can also check the value at runtime by typing ':set ?smtp_url' and
hitting return.



Re: Unexplained mutt error

2022-02-22 Thread Kevin J. McCarthy

On Tue, Feb 22, 2022 at 02:34:05PM -0600, Ranjan Maitra wrote:

On Tue Feb22'22 02:06:57PM, Ion wrote:

As instructed I changed it to...

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"

and also tried

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"



set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"


Thanks Ranjan - that's right.  Remember port 465 uses smtps://


both produced "Invalid SMTP URL: smtp.fastmail.com:465"


Check your muttrc to make sure you don't have the value specified twice 
or something.  That error message prints out the full value of 
$smtp_url, so somehow Mutt has the value minus the 
'smtps://ionm...@eml.cc@' prefix stored in $smtp_url.


You can also check the value at runtime by typing ':set ?smtp_url' and 
hitting return.


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


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-22 Thread Ranjan Maitra
On Tue Feb22'22 02:06:57PM, Ion wrote:
> From: Ion 
> Date: Tue, 22 Feb 2022 14:06:57 -0600
> To: mutt-users@mutt.org
> Subject: Re: Unexplained mutt error
>
> On 21/02/2022 21:53, Kevin J. McCarthy wrote:
>
> > On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:
> > > I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set
> > > smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed:
> > > 530 5.7.1 Authentication required".
> >
> > You'll need to add your username to the $smtp_url, so something like
> >   set smtp_url = "smtp://ionm...@eml.cc@smtp.fastmail.com:587"
> >
> As instructed I changed it to...
>
> set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"
>
> and also tried
>
> set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"
>

set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"



> both produced "Invalid SMTP URL: smtp.fastmail.com:465"
>
>


Re: Unexplained mutt error

2022-02-22 Thread Ion

On 21/02/2022 21:53, Kevin J. McCarthy wrote:


On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set
smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed:
530 5.7.1 Authentication required".


You'll need to add your username to the $smtp_url, so something like
  set smtp_url = "smtp://ionm...@eml.cc@smtp.fastmail.com:587"


As instructed I changed it to...

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:587"

and also tried

set smtp_url ="smtp://ionm...@eml.cc@smtp.fastmail.com:465"

both produced "Invalid SMTP URL: smtp.fastmail.com:465"




Re: Unexplained mutt error

2022-02-22 Thread Ion

I have already done that.

On 22/02/2022 08:42, José María Mateos wrote:

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

I used the same password as IMAP as the Fastmail help page tells me
"Your app-specific password. You cannot use your regular Fastmail
password." So does the "set ssl_force_tls =yes" not cover
authentication?


You need to create a password to use with IMAP / SMTP, it's not your
regular password:
https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords

Cheers,



Re: Unexplained mutt error

2022-02-22 Thread José María Mateos

On Tue, Feb 22, 2022 at 09:42:46AM -0500, José María Mateos wrote:

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

I used the same password as IMAP as the Fastmail help page tells me
"Your app-specific password. You cannot use your regular Fastmail
password." So does the "set ssl_force_tls =yes" not cover authentication?


You need to create a password to use with IMAP / SMTP, it's not your 
regular password: 
https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords


Given that you're using Fastmail, this is my SMTP config:

# SMTP SETTINGS
# Use port 565 for SMTP instead of 465 so we can mask the IP when sending.
set smtp_url = 'smtps://ch...@rinzewind.org@smtp.fastmail.com:565/'
# Source the password from file
# This file is in the following format:
# set smtp_pass = "pass"
# set imap_pass = $smtp_pass
source ~/.creds/mutt.pass

Cheers,

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


Re: Unexplained mutt error

2022-02-22 Thread José María Mateos

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

I used the same password as IMAP as the Fastmail help page tells me
"Your app-specific password. You cannot use your regular Fastmail
password." So does the "set ssl_force_tls =yes" not cover authentication?


You need to create a password to use with IMAP / SMTP, it's not your 
regular password: https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords


Cheers,

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


Re: Unexplained mutt error

2022-02-21 Thread Kevin J. McCarthy

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set
smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed:
530 5.7.1 Authentication required".


You'll need to add your username to the $smtp_url, so something like
  set smtp_url = "smtp://ionm...@eml.cc@smtp.fastmail.com:587"

I used the same password as IMAP as the Fastmail help page tells me 
"Your app-specific password.  You cannot use your regular Fastmail 
password."


Yes that's right.


So does the "set ssl_force_tls =yes" not cover authentication?


No that just makes sure encryption is used for 'smtp://' URLs.

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


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-21 Thread Ion

I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set
smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed:
530 5.7.1 Authentication required".

I used the same password as IMAP as the Fastmail help page tells me
"Your app-specific password. You cannot use your regular Fastmail
password." So does the "set ssl_force_tls =yes" not cover authentication?

On 21/02/2022 16:40, Kevin J. McCarthy wrote:

On Mon, Feb 21, 2022 at 02:46:11PM -0600, Ion wrote:

set smtp_url ="smtp://smtp.fastmail.com:465"



But the response was...

"SMTP session failed: read error"


The prefix 'smtps://' should be used with port 465:
  set smtp_url ="smtps://smtp.fastmail.com:465"

Alternatively you can use 'smtp://' with port 587 to use STARTTLS:
  set smtp_url ="smtp://smtp.fastmail.com:587"


set timeout=15
set mail_check=1


You didn't ask, but as an aside, $mail_check of 1 is a bit too
aggressive for IMAP.   suggests
  set mail_check=90
  set timeout=15
which I think is a fairly balanced approach.



Re: Unexplained mutt error

2022-02-21 Thread Kevin J. McCarthy

On Mon, Feb 21, 2022 at 02:46:11PM -0600, Ion wrote:

set smtp_url ="smtp://smtp.fastmail.com:465"



But the response was...

"SMTP session failed: read error"


The prefix 'smtps://' should be used with port 465:
  set smtp_url ="smtps://smtp.fastmail.com:465"

Alternatively you can use 'smtp://' with port 587 to use STARTTLS:
  set smtp_url ="smtp://smtp.fastmail.com:587"


set timeout=15
set mail_check=1


You didn't ask, but as an aside, $mail_check of 1 is a bit too 
aggressive for IMAP.   suggests

  set mail_check=90
  set timeout=15
which I think is a fairly balanced approach.

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


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-21 Thread Ion

Since my previous attempts failed I decided to go the default route
using Fastmail IMAP and SMTP as advised on their web help page. I set my
.muttrc file as follows, hoping it would be easier to resolve the problem.

set imap_user=ionm...@eml.cc
set imap_pass="my fastmail password"
set realname    ="Ion"
set from = "ionm...@eml.cc"
set folder=imaps://imap.fastmail.com:993
set smtp_url ="smtp://smtp.fastmail.com:465"
set smtp_pass = "my fastmail password"
set ssl_force_tls =yes
set header_cache = ~/.cache/mutt
set spoolfile = "+INBOX"
set record ="+Sent Items"
set postponed="+Drafts"
set trash = "+Trash"
set editor ="nano"
set timeout=15
set mail_check=1
set check_new=yes
auto_view text/html

But the response was...

"SMTP session failed: read error"



Re: Unexplained mutt error

2022-02-20 Thread Robert F. Crochelt
On Sun, Feb 20, 2022 at 03:37:45PM -0500, Kurt Hackenberg wrote:
> On Sun, Feb 20, 2022 at 01:10:11PM -0600, Hokan wrote:
> 
> >Replying to the sender seems to be the default behavior for the list.
> 
> Do y'all know about the command 'L' ?
> 
> See the manual:
> 

Thanks for this.
Bob Crochelt


Re: Unexplained mutt error

2022-02-20 Thread Kurt Hackenberg
On Sun, Feb 20, 2022 at 01:10:11PM -0600, Hokan wrote:

>Replying to the sender seems to be the default behavior for the list.

Do y'all know about the command 'L' ?

See the manual:



Re: Unexplained mutt error

2022-02-20 Thread Ion



On 20/02/2022 14:41, Kevin J. McCarthy wrote:

On Sun, Feb 20, 2022 at 01:49:45PM -0600, Ion wrote:

Here are my account settings from Thunderbird. They work.

IMAP server mail.messagingengine.com ionm...@eml.cc 993 SSL/TLS
SMTP server smtp.pobox.com i...@pobox.com 587 STARTTLS

So doesn't that indicate that I have an accessible "Sent" folder?


No, that is only telling Thunderbird how to connect to your IMAP and
SMTP servers.


But here's more. In Thunderbird settings Copies and Folders are all
on Pobox. So perhaps that's the problem.


It's been a long time since I've used Thunderbird.  Maybe someone else
can chime in.

But, yes, it sounds like you are saying Thunderbird is saving copies
to your pobox.com server account, instead of
mail.messagingengine.com.  Do you have IMAP settings configured for
pobox.com too?

No, my IMAP is set to Fastmail



$record can have a full 'imaps://' URL in it, but it seems a bit
strange to be reading from one place and writing to another. Perhaps
you can re-check the correct settings with your provider.


You're right. "Strange" defines the way I do a lot of things.



A quick search found
,
but please check for yourself what is "correct".

Thanks for all the help. I think I'm getting closer to a solution. I
will report back later.


Re: Unexplained mutt error

2022-02-20 Thread Kevin J. McCarthy

On Sun, Feb 20, 2022 at 01:49:45PM -0600, Ion wrote:

Here are my account settings from Thunderbird. They work.

IMAP server mail.messagingengine.com ionm...@eml.cc 993 SSL/TLS
SMTP server smtp.pobox.com i...@pobox.com 587 STARTTLS

So doesn't that indicate that I have an accessible "Sent" folder?


No, that is only telling Thunderbird how to connect to your IMAP and 
SMTP servers.


But here's more. In Thunderbird settings Copies and Folders are all on 
Pobox. So perhaps that's the problem.


It's been a long time since I've used Thunderbird.  Maybe someone else 
can chime in.


But, yes, it sounds like you are saying Thunderbird is saving copies to 
your pobox.com server account, instead of mail.messagingengine.com.  Do 
you have IMAP settings configured for pobox.com too?


$record can have a full 'imaps://' URL in it, but it seems a bit strange 
to be reading from one place and writing to another.  Perhaps you can 
re-check the correct settings with your provider.


A quick search found 
, 
but please check for yourself what is "correct".


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


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-20 Thread Ion

On 20/02/2022 13:28, Kevin J. McCarthy wrote:


On Sun, Feb 20, 2022 at 01:13:56PM -0600, Ion wrote:

On 20/02/2022 12:37, Kevin J. McCarthy wrote:

Are you sure you have a "Sent" folder on your mail.messagingengine.com
account, that you can access and write to?


Here are my account settings from Thunderbird. They work.

IMAP server mail.messagingengine.com ionm...@eml.cc 993 SSL/TLS
SMTP server smtp.pobox.com i...@pobox.com 587 STARTTLS

So doesn't that indicate that I have an accessible "Sent" folder? But
here's more. In Thunderbird settings Copies and Folders are all on
Pobox. So perhaps that's the problem. How would I define those in my
.muttrc?



Well if I don't have access to it why does...

:~> echo "" | mutt -s "subject" -i file.txt ionm...@gmx.us" work when it
uses the same .muttrc file?


Fcc'ing to an IMAP mailbox is not supported in batch mode.  So the
batch mode send is not trying to record the sent message to '+Sent'.


Thank you that explains a lot.

On Fastmail, for instance, the correct setting is:
  set record = "+Sent Items"
but perhaps their 'pobox' users are configured differently.


I changed it to "+Sent Items".  Nothing changed.


Did you check that you have a "Sent" or "Sent Items" folder, that you
can access and write to?  Perhaps you could try another mailbox that
you are sure exists and you can write to?

It may also be useful to run mutt in debug mode, e.g. with '-d 2' as
an argument.  If it's compiled with debug mode, that will generate a
file, ~/.muttdebug0 with commands sent to the SMTP and IMAP servers. 
Perhaps that will give a clue as to where the error is coming from.


Unfortunately DEBUG was not defined during compilation, and I don't
think I am sufficiently advance to compile it.


Re: Unexplained mutt error

2022-02-20 Thread Patrick Shanahan
* Hokan  [02-20-22 14:11]:
> Replying to the sender seems to be the default behavior for the list.
> 
> Perhaps the list owner could set the "Reply-to" header to help with this.
> 
> 
> On Sun, Feb 20, 2022 at 10:37:22AM -0800, Kevin J. McCarthy wrote:
> > Please don't reply to me personally, it's poor etiquette.


there is no *default* behavior after observing netiquette.  setting
"Reply-To:" alters the header and the list software abstains.


-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet oftc
What sort of day was it?  A day like all days, filled with 
those events that alter and illuminate our times... 


Re: Unexplained mutt error

2022-02-20 Thread Kevin J. McCarthy

On Sun, Feb 20, 2022 at 01:13:56PM -0600, Ion wrote:

On 20/02/2022 12:37, Kevin J. McCarthy wrote:

Are you sure you have a "Sent" folder on your mail.messagingengine.com
account, that you can access and write to?


Well if I don't have access to it why does...

:~> echo "" | mutt -s "subject" -i file.txt ionm...@gmx.us" work when it
uses the same .muttrc file?


Fcc'ing to an IMAP mailbox is not supported in batch mode.  So the batch 
mode send is not trying to record the sent message to '+Sent'.



On Fastmail, for instance, the correct setting is:
  set record = "+Sent Items"
but perhaps their 'pobox' users are configured differently.


I changed it to "+Sent Items".  Nothing changed.


Did you check that you have a "Sent" or "Sent Items" folder, that you 
can access and write to?  Perhaps you could try another mailbox that you 
are sure exists and you can write to?


It may also be useful to run mutt in debug mode, e.g. with '-d 2' as an 
argument.  If it's compiled with debug mode, that will generate a file, 
~/.muttdebug0 with commands sent to the SMTP and IMAP servers.  Perhaps 
that will give a clue as to where the error is coming from.


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


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-20 Thread Ion

On 20/02/2022 12:37, Kevin J. McCarthy wrote:


Please don't reply to me personally, it's poor etiquette.  Redirecting
back to the mailing list.

Understood. I apologize.


On Sun, Feb 20, 2022 at 11:55:06AM -0600, Ion wrote:

Thanks for the speedy reply. There was no prompt. So I added "set
confirmcreate = yes" to my .muttrc file and tried gain. No change.
Another observation. Mutt shows my IMAP inbox. It seems the problem lies
with the SMTP request.


I'm not sure why you aren't seeing a "Create xxx?" prompt first.
Still, I hypothesize this is from your 'set record ="+Sent"' setting.


I see no "Create xxx" prompt.



Are you sure you have a "Sent" folder on your mail.messagingengine.com
account, that you can access and write to?


Well if I don't have access to it why does...

:~> echo "" | mutt -s "subject" -i file.txt ionm...@gmx.us" work when it
uses the same .muttrc file?



On Fastmail, for instance, the correct setting is:
  set record = "+Sent Items"
but perhaps their 'pobox' users are configured differently.


I changed it to "+Sent Items".  Nothing changed.



-Kevin


Re: Unexplained mutt error

2022-02-20 Thread Hokan
Replying to the sender seems to be the default behavior for the list.

Perhaps the list owner could set the "Reply-to" header to help with this.


On Sun, Feb 20, 2022 at 10:37:22AM -0800, Kevin J. McCarthy wrote:
> Please don't reply to me personally, it's poor etiquette.

-- 
Hokan
Bicyclist
Sysadmin


Re: Unexplained mutt error

2022-02-20 Thread Kevin J. McCarthy
Please don't reply to me personally, it's poor etiquette.  Redirecting 
back to the mailing list.


On Sun, Feb 20, 2022 at 11:55:06AM -0600, Ion wrote:

Thanks for the speedy reply. There was no prompt. So I added "set
confirmcreate = yes" to my .muttrc file and tried gain. No change.
Another observation. Mutt shows my IMAP inbox. It seems the problem lies
with the SMTP request.


I'm not sure why you aren't seeing a "Create xxx?" prompt first.  Still, 
I hypothesize this is from your 'set record ="+Sent"' setting.


Are you sure you have a "Sent" folder on your mail.messagingengine.com 
account, that you can access and write to?


On Fastmail, for instance, the correct setting is:
  set record = "+Sent Items"
but perhaps their 'pobox' users are configured differently.

-Kevin


signature.asc
Description: PGP signature


Re: Unexplained mutt error

2022-02-20 Thread Kevin J. McCarthy

On Sun, Feb 20, 2022 at 10:56:05AM -0600, Ion wrote:

...while executing mutt and using the menus, with the same addresses
leaves me with...

Code:
CREATE failed: Permission denied


That's an IMAP permission error.  It would usually be preceded by a 
prompt to create a mailbox that doesn't exist yet, unless $confirmcreate 
was turned off in your muttrc.


Did you see any kind of prompt?

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


signature.asc
Description: PGP signature