The issue has resolved itself without me taking any action!
Thanks to those who offered advice.
Particular thanks to those who pointed out that I had made the
boneheaded move to post my password base-64 encoded on this list. The password
has been changed.
Andy
On
On Thu, Jun 20, 2024 at 11:42:20AM -0700, Will Yardley wrote:
If by "the docs" you're referring only to the man pages, vs. the Mutt
wiki and other online docs, you're right that they don't explicitly
mention that it can refer to a remote mailbox.
Obviously the manual was not updated when the
On Thu, Jun 20, 2024 at 02:25:41PM -0400, Kurt Hackenberg wrote:
> On Thu, Jun 20, 2024 at 11:18:48AM -0700, Will Yardley wrote:
>
> > ...I agree the docs could make it more clear.
>
> The docs never mention it, not even once.
If by "the docs" you're referring only to the man pages, vs. the
Kurt Hackenberg wrote on Thu, 20 Jun 2024
at 14:25:41 EDT in :
> The docs never mention it, not even once.
You need to read more broadly: "If your spool mailbox is in a non-default place
where Mutt cannot find it, you can specify its location with this variable."
Once you understand "spool
On Thu, Jun 20, 2024 at 11:18:48AM -0700, Will Yardley wrote:
...I agree the docs could make it more clear.
The docs never mention it, not even once.
On Thu, Jun 20, 2024 at 02:14:40PM -0400, Kurt Hackenberg wrote:
> On Thu, Jun 20, 2024 at 10:56:28AM -0700, Will Yardley wrote:
>
> > > The variable spoolfile has nothing to do with IMAP, and does not affect
> > > it.
> >
> > I disagree; from what I can see, the _naming_ of $spoolfile is
On Thu, Jun 20, 2024 at 10:56:28AM -0700, Will Yardley wrote:
The variable spoolfile has nothing to do with IMAP, and does not affect it.
I disagree; from what I can see, the _naming_ of $spoolfile is vestigal
and comes from before mutt supported IMAP, but it _does_ affect mutt's
behavior,
On Thu, Jun 20, 2024 at 01:25:33PM -0400, Kurt Hackenberg wrote:
> On Thu, Jun 20, 2024 at 10:11:36AM -0700, Will Yardley wrote:
>
> > > I believe that's unnecessary, and kind of wrong. That variable
> > > spoolfile is for incoming mail delivered into local files on the
> > > computer where Mutt
On Thu, Jun 20, 2024 at 10:11:36AM -0700, Will Yardley wrote:
I believe that's unnecessary, and kind of wrong. That variable
spoolfile is
for incoming mail delivered into local files on the computer where
Mutt runs
(eg, /var/mail/freduser, or ~freduser/Maildir). IMAP is entirely
different,
On Thu, Jun 20, 2024 at 12:30:13PM -0400, Kurt Hackenberg wrote:
> I believe that's unnecessary, and kind of wrong. That variable spoolfile is
> for incoming mail delivered into local files on the computer where Mutt runs
> (eg, /var/mail/freduser, or ~freduser/Maildir). IMAP is entirely
On Wed, Jun 19, 2024 at 11:43:54PM -0400, Andrew D Arenson wrote:
Today, after working for years, my IMAP connection to Dreamhost has
started hanging when I attempt to send an email, showing a message
like: "Sending message... 0K/0.4K (0%)".
Sure looks like Dreamhost had a problem. (Does it
Thanks! I had seen this notice, but unfortunately, my problems have persisted.I have asked their support to share what went wrong and how they fixed it to see if I can identify how that might have affected mutt's attempt to use their SMTP server.Andyfrom mobileOn Jun 20, 2024 11:35, José María
On Thu, Jun 20, 2024 at 08:08:22AM -0700, Will Yardley wrote:
[snip discussion about OAuth support]
> All that said, while I know active development is pretty much on pause,
> and while it's unclear to me whether XOAUTH2 itself is a standard, I
> think it is (IMO) important that mutt somehow
On Wed, Jun 19, 2024 at 11:43:54PM -0400, Andrew D Arenson wrote:
Today, after working for years, my IMAP connection to Dreamhost has
started hanging when I attempt to send an email, showing a message
like: "Sending message... 0K/0.4K (0%)".
Looks like Dreamhost had problems with their mail
On Thu, Jun 20, 2024 at 07:38:50AM -0700, Will Yardley wrote:
> On Thu, Jun 20, 2024 at 09:06:54AM +0200, Christian Brabandt wrote:
> > On Mi, 19 Jun 2024, Will Yardley wrote:
> >
> > > (I have started to see some Gmail environments also prevent the
> > > creation of app passwords).
> >
> > If I
On 2024-06-20, Christian Brabandt wrote:
> On Mi, 19 Jun 2024, Will Yardley wrote:
>
>> (I have started to see some Gmail environments also prevent the
>> creation of app passwords).
>
> If I recall correctly google is transitioning away from using app
> passwords later this year. A quick google
On Thu, Jun 20, 2024 at 09:06:54AM +0200, Christian Brabandt wrote:
> On Mi, 19 Jun 2024, Will Yardley wrote:
>
> > (I have started to see some Gmail environments also prevent the
> > creation of app passwords).
>
> If I recall correctly google is transitioning away from using app
> passwords
On Mi, 19 Jun 2024, Will Yardley wrote:
> (I have started to see some Gmail environments also prevent the
> creation of app passwords).
If I recall correctly google is transitioning away from using app
passwords later this year. A quick google turned up this doc:
On 2024-06-19 15:31, Will Yardley wrote:
> On Tue, Jun 18, 2024 at 07:25:48AM +0200, Jan Eden via Mutt-users wrote:
> > text/html; w3m -dump -I %{charset} -T text/html -o display_link_number=1
> > %s; copiousoutput;
>
> Aside from the lynx suggestion that someone posted, I think "urlview" is
>
On 2024-06-20 01:20, Andrew D Arenson wrote:
> Just to add -- I have, indeed, tried both port 587 and port 465 -- same
> results.
>
> Point about this being SMTP and not IMAP is noted. Thanks!
Could it be that the SMTP server's certificate changed, so the TLS
connection fails because mutt
20 matches
Mail list logo
