From robin.listas at telefonica.net Mon Aug 7 12:25:16 2023 From: robin.listas at telefonica.net (Carlos E. R.) Date: Fri Mar 22 14:17:33 2024 Subject: [Alpine-info] Sudenly, a rule doesn't work. In-Reply-To: <74b74e9a-56aa-62a8-f89b-1ad7b9886d88@telefonica.net> References: <6b6ff193-e7ff-527c-489e-828b3262550d@telefonica.net> <74b74e9a-56aa-62a8-f89b-1ad7b9886d88@telefonica.net> Message-ID: On 2023-06-25 13:38, Carlos E. R. wrote: > On Sunday, 2023-06-25 at 11:45 +0100, Dennis Davis wrote: >> On Fri, 23 Jun 2023, Carlos E. R. wrote: > > ... > >>> And suddenly, today it fails: >>> >>> >>> [full text search not supported] >>> >>> >>> >>> Is there something I can do? >>> >>> It is a gmx.es account. > >> Long shot: if this is an IMAP account, the following option on the >> INBOX/Folder specification might help: > > Yes, it is IMAP. > >> Loser >> This option makes sense only for IMAP servers that do not >> perform a SEARCH command correctly. If your filtering rules fail >> to filter some messages, that should have been filtered, then >> this option will make Alpine download all data necessary data >> to perform that search. There is a performance penalty when >> using this option. Downloading the data to perform the search >> will take longer than requesting the IMAP server to perform the >> filtering, but the filtering will be done correctly. > > AH! > > Trying now. > > incoming-folders=... > "imap Gmx L" {imap.gmx.com/tls/user=myname@gmx.es/loser}INBOX, > > > Yes, the filter runs significantly slower, but it runs. Opening the > folder seems as fast as always. ... So now I have a second instance of alpine, with a different config file. The main one has: > incoming-folders="... > "imap Gmx L" {imap.gmx.com/tls/user=me@gmx.es}INBOX, and the alternate one, started via: alpine -p /home/cer/.pinerc-gmx has: > ... > "imap F Gmx L" {imap.gmx.com/tls/user=me@gmx.es/loser}INBOX, This has been working since this post, but today it fails again. [full text search not supported] I restart this alpine, and it works again. :-? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar) -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 209 bytes Desc: OpenPGP digital signature URL: From alpine.chappa at yandex.com Tue Aug 8 07:08:47 2023 From: alpine.chappa at yandex.com (Eduardo Chappa) Date: Fri Mar 22 14:17:33 2024 Subject: [Alpine-info] Sudenly, a rule doesn't work. In-Reply-To: References: <6b6ff193-e7ff-527c-489e-828b3262550d@telefonica.net> <74b74e9a-56aa-62a8-f89b-1ad7b9886d88@telefonica.net> Message-ID: <31436bd1-e3f7-22e7-fcc0-0f0b4b445c68@yandex.com> On Mon, 7 Aug 2023, Carlos E. R. wrote: >> "imap F Gmx L" {imap.gmx.com/tls/user=me@gmx.es/loser}INBOX, > > > This has been working since this post, but today it fails again. > > [full text search not supported] Go through your .pinerc file and make sure that every connection to imap.gmx.com says "/loser" in it. What I think might be happening is that you have two configurations for GMX, one with /loser and one without it. Sometimes you use the one with /loser first, and sometimes you use the one without it. When you use the one without it first, the time you are going to open the one with it, Alpine reuses your connection and does not register the /loser part because of it. Does this explain your issue? -- Eduardo From robin.listas at telefonica.net Tue Aug 8 10:47:37 2023 From: robin.listas at telefonica.net (Carlos E. R.) Date: Fri Mar 22 14:17:33 2024 Subject: [Alpine-info] Sudenly, a rule doesn't work. In-Reply-To: <31436bd1-e3f7-22e7-fcc0-0f0b4b445c68@yandex.com> References: <6b6ff193-e7ff-527c-489e-828b3262550d@telefonica.net> <74b74e9a-56aa-62a8-f89b-1ad7b9886d88@telefonica.net> <31436bd1-e3f7-22e7-fcc0-0f0b4b445c68@yandex.com> Message-ID: <6e17c1da-95c5-67a1-9ea7-ad358eb4c763@telefonica.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2023-08-08 a las 08:08 -0600, Eduardo Chappa escribi?: > On Mon, 7 Aug 2023, Carlos E. R. wrote: > >>> "imap F Gmx L" {imap.gmx.com/tls/user=me@gmx.es/loser}INBOX, >> >> >> This has been working since this post, but today it fails again. >> >> [full text search not supported] > > Go through your .pinerc file and make sure that every connection to > imap.gmx.com says "/loser" in it. What I think might be happening is that you > have two configurations for GMX, one with /loser and one without it. > Sometimes you use the one with /loser first, and sometimes you use the one > without it. When you use the one without it first, the time you are going to > open the one with it, Alpine reuses your connection and does not register the > /loser part because of it. Does this explain your issue? That is correct, there are two folders defined, one the "input" and another one where I move to the messages that hit the rule. I just edited the second. Wow. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZNJ/uhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVFmAAnRRZdSxv3GKHAAJYV0dM J9q6mkaiAJ4m58oIVLTWtNfo21sDXzt4DpLvBw== =1CD0 -----END PGP SIGNATURE----- From g at gft.nu Thu Aug 17 06:01:17 2023 From: g at gft.nu (George Thuronyi) Date: Fri Mar 22 14:17:33 2024 Subject: [Alpine-info] Opening attachments Message-ID: Greetings, When I open attachments in Alpine (Windows), the files open in the native program with a temporary name like, "img-PDF-22495.pdf" or "img-VND.O-68299." Is there any way to retain the file name when opening? (Saving the attachment first does retain the original file name.) Thanks! George Thuronyi (Pine/Alpine user since the 1990s) -------------- next part -------------- An HTML attachment was scrubbed... URL: