1 |
On Wed, Mar 24, 2021 at 04:31:56AM -0400, Philip wrote in |
2 |
<YFr4/PITvgyTVa3U@××××××××.net>: |
3 |
>210322 Remco Rijnders wrote: |
4 |
>> On Mon, Mar 22, 2021 at 03:22:26AM -0400, Philip wrote in |
5 |
>>> I tried the Mutt 'G' command, which replied : |
6 |
>>> "STLS: Mate, the command must be CAPA USER PASS QUIT ; no encryption". |
7 |
>>> Of course, that wouldn't do, as it has to send out my password. |
8 |
>>> So Fetchmail itself is working, but when Mutt calls it, something goes wrong. |
9 |
>> How does Mutt call Fetchmail ? |
10 |
> |
11 |
>That I'm not sure (smile). |
12 |
|
13 |
I think mutt doesn't call fetchmail. You have fetchmail set up to pull mail from |
14 |
your pop server (this works), and you have mutt set up to also pull mail from |
15 |
your pop server (this no longer works), using mutt's own built in POP support |
16 |
(http://www.mutt.org/doc/manual/#pop) which does not use your fetchmail |
17 |
configuration at all. |
18 |
|
19 |
You thus have two ways set up to access your mail. You might either do away with |
20 |
POP support in your mutt (as the mutt manual says: If you only need to fetch all |
21 |
messages to a local mailbox you should consider using a specialized program, |
22 |
such as fetchmail(1), getmail(1) or similar.), or make sure that mutt accesses |
23 |
the POP server the same way that fetchmail does. |
24 |
|
25 |
>> I think 'G' is not bound by default in Mutt. |
26 |
> |
27 |
>IIRC it is bound by default : at least, it's always worked before. |
28 |
|
29 |
Ah yes, your version of mutt has POP support built in, mine doesn't and as such |
30 |
'G' is not bound on my system, my bad. |
31 |
|
32 |
>> How did you set it up in your .muttrc ? |
33 |
> |
34 |
> set pop_host="pop.<ISP>" |
35 |
> set pop_pass="<password>" |
36 |
> set pop_user="<username>" |
37 |
> set pop_last |
38 |
> |
39 |
>Fetchmail is run as a user cron job. It was last emerged in 2020. |
40 |
>The cron jobs are running as before, but nothing is downloaded. |
41 |
> .muttrc hasn't been changed since 2020. |
42 |
> |
43 |
>It does appear that it is in fact more convenient to use Fetchmail directly. |
44 |
>Instead of having to check several folders for new mail, |
45 |
>I can issue the command (aliased as 'fm') when I decide to check mail |
46 |
>& it actually tells me how many it's downloading, |
47 |
>so if there's nothing, I don't have to do anything else. |
48 |
> |
49 |
>However, it wb helpful to find out what has gone wrong. |
50 |
>It must be some pkg I updated since 210220. |
51 |
|
52 |
Either something changed in your system, or possibly on the ISP side of things. |
53 |
The "Mate, the command must be one of CAPA, USER, PASS or QUIT" error you get is |
54 |
returned by the server you are trying to retrieve your mail from, not mutt, and |
55 |
probably in relation to mutt sending the STLS command to (attempt to) start a |
56 |
secure session. You might want to see what mutt does different from what |
57 |
fetchmail does. Try adding ':995' (for port 995, used for encrypted POP3) to the |
58 |
pop_host setting? |
59 |
|
60 |
Of late, a lot of email providers (notably gmail, MS/outlook, and I think Yahoo |
61 |
too) require OAUTH support to access mail. Maybe this applies to you? See the |
62 |
interwebs for documentation on how to configure this for fetchmail and mutt |
63 |
respectively. |
64 |
|
65 |
I hope this helps you a little further. |
66 |
|
67 |
Kind regards, |
68 |
|
69 |
Remco |