From alpine-info at u.washington.edu Thu Aug 1 09:45:42 2024 From: alpine-info at u.washington.edu (Andrew C Aitchison via Alpine-info) Date: Thu Aug 1 09:45:53 2024 Subject: [Alpine-info] Request for CLIENTID support in Alpine Message-ID: Would it be possible to add CLIENTID support in Alpine ? CLIENTID is defined by a pair of draft RFCs https://datatracker.ietf.org/doc/draft-storey-smtp-client-id/ https://datatracker.ietf.org/doc/draft-yu-imap-client-id/ It allows the mail client to tell the server more about itself and the user, allowing a server to restrict access on a device+user basis; eg to block a spammer who has got hold of your login details, whilst continuing to allowing you to send and receive emails from your phone. CLIENTID is supported by Thunderbird, emClient, and BlueMail clients and at least MagicMail "the Top Selling Carrier Grade Email platform for the ISP, Telco, and Cable industry in North America". This is a 2FA method that does not require a third party, so is simpler to implement than OAUTH. I am currently attempting to write CLIENTID support for Exim. Thanks, -- Andrew C. Aitchison Kendal, UK andrew@aitchison.me.uk From alpine-info at u.washington.edu Sun Aug 4 18:05:20 2024 From: alpine-info at u.washington.edu (David Morris via Alpine-info) Date: Sun Aug 4 18:05:25 2024 Subject: [Alpine-info] Can't compile V2.25 or 2.26 on Rocky 9.2 Message-ID: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> FYI Rocky is a linux distribution based on RH Enterprise Linux. Centos used to fill that role, but RedHat turned Centos into an advanced release sandbox... What I see running configure: ... checking for setupterm in -ltinfo... no checking for setupterm in -lncurses... no checking for setupterm in -lcurses... no checking for tgetent in -ltermlib... no checking for tgetent in -ltermcap... no configure: error: Terminfo/termcap not found (in case it matters, this is from the 2.26 attempt) ncurses-6.2.8 is installed and the infocmp command exists and works. After some digging and comparing my systems, I noticed that ncurses is installed in /usr/lib64/ which suggests the problem is associated with the fact my system is a 64 bit system and hence a minimal /usr/lib/ I tried looking at 'configure' but it has been too many years since I did any shell programming so I made no progress there. I previously tried to add support for the 32 bit programs but I think what I found was incomplete. I'd be happy to test any updates to configure, but have to put this on the back burner for not. Thanks, David From alpine-info at u.washington.edu Tue Aug 6 14:18:29 2024 From: alpine-info at u.washington.edu (David Morris via Alpine-info) Date: Tue Aug 6 14:18:34 2024 Subject: [Alpine-info] New version welcome message has a bad URL Message-ID: The welcome message still references X10HOST From alpine-info at u.washington.edu Tue Aug 6 14:24:43 2024 From: alpine-info at u.washington.edu (David Morris via Alpine-info) Date: Tue Aug 6 14:24:48 2024 Subject: [Alpine-info] Can't compile V2.25 or 2.26 on Rocky 9.2 In-Reply-To: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> References: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> Message-ID: <5fabd721-d878-e73d-d464-91aa53911122@xpasc.com> Update: I solved my operational issue with running Alpine on the new system I'm provisioning. I built a 32-bit executable on my RHEL 5.3 system and then copied all the 32-bit dependancies to my new Rocky 9.2 system. It worked. Would still like to have a 64 bit executable for the future as I had to disable SSL because I don't have the required openssl version. On Sun, 4 Aug 2024, David Morris wrote: > > FYI Rocky is a linux distribution based on RH Enterprise Linux. Centos > used to fill that role, but RedHat turned Centos into an advanced release > sandbox... > > What I see running configure: > ... > checking for setupterm in -ltinfo... no > checking for setupterm in -lncurses... no > checking for setupterm in -lcurses... no > checking for tgetent in -ltermlib... no > checking for tgetent in -ltermcap... no > configure: error: Terminfo/termcap not found > (in case it matters, this is from the 2.26 attempt) > > ncurses-6.2.8 is installed and the infocmp command exists and works. > > After some digging and comparing my systems, I noticed that ncurses is > installed in /usr/lib64/ which suggests the problem is associated with the > fact my system is a 64 bit system and hence a minimal /usr/lib/ > > I tried looking at 'configure' but it has been too many years since I did > any shell programming so I made no progress there. I previously tried to > add support for the 32 bit programs but I think what I found was > incomplete. > > I'd be happy to test any updates to configure, but have to put this on the > back burner for not. > > Thanks, > David > > From alpine-info at u.washington.edu Wed Aug 7 04:01:39 2024 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Wed Aug 7 04:01:45 2024 Subject: [Alpine-info] Can't compile V2.25 or 2.26 on Rocky 9.2 In-Reply-To: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> References: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> Message-ID: <4bc311f8-38bb-6de9-4069-d9ab8aa30d69@telefonica.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2024-08-04 at 18:05 -0700, David Morris via Alpine-info wrote: > FYI Rocky is a linux distribution based on RH Enterprise Linux. Centos > used to fill that role, but RedHat turned Centos into an advanced release > sandbox... > > What I see running configure: > ... > checking for setupterm in -ltinfo... no > checking for setupterm in -lncurses... no > checking for setupterm in -lcurses... no > checking for tgetent in -ltermlib... no > checking for tgetent in -ltermcap... no > configure: error: Terminfo/termcap not found > (in case it matters, this is from the 2.26 attempt) > > ncurses-6.2.8 is installed and the infocmp command exists and works. I'm not familiar with RH nor Rocky; I use openSUSE, so I could be confused/mistaken. Here, if I see that error, it would be because I have not instaled termcap-devel. For compilation, I need to install the -devel version of each library. (apparently I can have Telcontar:~ # opi termcap-devel Searching repos for: termcap-devel 1. mingw32-termcap-devel 2. mingw64-termcap-devel Pick a number (0 to quit): ) - -- Cheers, Carlos E. R. (from openSUSE 15.5 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZrNUExwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV1CIAoIYteFkAFoIWZT0n/ZFC NgJYE8B0AJ9KhkWrjHhlKiyJbfKraJHeWHn9fQ== =qjxB -----END PGP SIGNATURE----- From alpine-info at u.washington.edu Wed Aug 7 06:34:16 2024 From: alpine-info at u.washington.edu (Andrew C Aitchison via Alpine-info) Date: Wed Aug 7 06:34:35 2024 Subject: [Alpine-info] Can't compile V2.25 or 2.26 on Rocky 9.2 In-Reply-To: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> References: <9c7edaee-5fcc-813b-33aa-63612e13d6be@xpasc.com> Message-ID: On Sun, 4 Aug 2024, David Morris via Alpine-info wrote: > FYI Rocky is a linux distribution based on RH Enterprise Linux. Centos > used to fill that role, but RedHat turned Centos into an advanced release > sandbox... > > What I see running configure: > ... > checking for setupterm in -ltinfo... no > checking for setupterm in -lncurses... no > checking for setupterm in -lcurses... no > checking for tgetent in -ltermlib... no > checking for tgetent in -ltermcap... no > configure: error: Terminfo/termcap not found > (in case it matters, this is from the 2.26 attempt) Do you have EPEL ? It seems to be still on 2.25, but you could take the source rpm https://dl.fedoraproject.org/pub/epel/9/Everything/source/tree/Packages/a/alpine-2.25-2.el9.src.rpm add the 2.26 tarball, upsdte alpine.spec to use v2.26 and run rpmbuild -ba alpine.spec > ncurses-6.2.8 is installed and the infocmp command exists and works. > > After some digging and comparing my systems, I noticed that ncurses is > installed in /usr/lib64/ which suggests the problem is associated with the > fact my system is a 64 bit system and hence a minimal /usr/lib/ > > I tried looking at 'configure' but it has been too many years since I did > any shell programming so I made no progress there. I previously tried to > add support for the 32 bit programs but I think what I found was > incomplete. > > I'd be happy to test any updates to configure, but have to put this on the > back burner for not. > > Thanks, > David -- Andrew C. Aitchison Kendal, UK andrew@aitchison.me.uk From alpine-info at u.washington.edu Sat Aug 10 12:01:06 2024 From: alpine-info at u.washington.edu (Karen Lewellen via Alpine-info) Date: Sat Aug 10 12:01:11 2024 Subject: [Alpine-info] things that might cause Alpine to close an Inbox? Message-ID: Hi folks, I do not really encounter this issue anywhere but with the Alpine configurations at dreamhost. Even here the problem varies. still, curious what common factors might cause Alpine to close an inbox, say in less than a minute? Wondering if there are settings i can check. Thanks, Karen From alpine-info at u.washington.edu Sat Aug 10 16:04:46 2024 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Sat Aug 10 16:04:51 2024 Subject: [Alpine-info] things that might cause Alpine to close an Inbox? In-Reply-To: References: Message-ID: Hi Karen: I just looked but cannot find what I was going to suggest, but I seem to remember a setting to disable inactivity. When this used to happen if I followed an url which lead me to a long download, over an hour. Anyway I must have fixed it as I've had an inbox in a similar state for `several hours. Chime From alpine-info at u.washington.edu Sat Aug 10 18:02:40 2024 From: alpine-info at u.washington.edu (Karen Lewellen via Alpine-info) Date: Sat Aug 10 18:02:44 2024 Subject: [Alpine-info] things that might cause Alpine to close an Inbox? In-Reply-To: References: Message-ID: Hi chime, What makes this really odd is the inbox closes, while I am writing an email for example. Inactivity is one thing, but while I am typing? Thanks for looking, Kare On Sat, 10 Aug 2024, Chime Hart wrote: > Hi Karen: I just looked but cannot find what I was going to suggest, but I > seem to remember a setting to disable inactivity. When this used to happen if > I followed an url which lead me to a long download, over an hour. Anyway I > must have fixed it as I've had an inbox in a similar state for `several > hours. > Chime > > > From alpine-info at u.washington.edu Sun Aug 11 05:44:51 2024 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Sun Aug 11 05:44:58 2024 Subject: [Alpine-info] things that might cause Alpine to close an Inbox? In-Reply-To: References: Message-ID: <6d1561a0-f50b-4b80-9a35-ec3cced41747@telefonica.net> On 2024-08-11 03:02, Karen Lewellen via Alpine-info wrote: > Hi chime, > What makes this really odd is the inbox closes, while I am writing an > email for example. > Inactivity is one thing, but while I am typing? > Thanks for looking, > Kare Bad server. I have that problem with one account of my ISP. The other accounts at that ISP work fine, except this one. For years. Alpine can not stand that problem and closes the folder. Other MUAs, like Thunderbird, silently reopen and the user doesn't even notice. On the other hand, I get corrupted indexes with TB now and then. -- Cheers / Saludos, Carlos E. R. (from 15.5 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-info at u.washington.edu Sun Aug 11 08:10:25 2024 From: alpine-info at u.washington.edu (Eduardo Chappa via Alpine-info) Date: Sun Aug 11 08:10:38 2024 Subject: [Alpine-info] things that might cause Alpine to close an Inbox? In-Reply-To: References: Message-ID: <76611ad4-2e65-1455-201e-540bcd849cd7@yandex.com> On Sat, 10 Aug 2024, Karen Lewellen via Alpine-info wrote: > Hi folks, > I do not really encounter this issue anywhere but with the Alpine > configurations at dreamhost. > Even here the problem varies. still, curious what common factors might > cause Alpine to close an inbox, say in less than a minute? > Wondering if there are settings i can check. > Thanks, > Karen Dear Karen, press M S C and set Mail Check Interval = 15 I hope this helps. -- Eduardo From alpine-info at u.washington.edu Thu Aug 22 13:58:30 2024 From: alpine-info at u.washington.edu (Doug Luce via Alpine-info) Date: Thu Aug 22 13:58:35 2024 Subject: [Alpine-info] Automatically expunging? Message-ID: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> Seems my Alpine (2.26, 4/9/2024) client has started automatically sending an EXPUNGE command after I mark a message deleted (in the INBOX). This wasn't always the case and I'm not sure when it started but my guess is in the last month or two. I can't seem to find a setting that controls this and a quick perusal of the source doesn't clue me in. Anyone know what I may have done to myself? Thanks, Doug From alpine-info at u.washington.edu Thu Aug 22 14:13:00 2024 From: alpine-info at u.washington.edu (David Lang via Alpine-info) Date: Thu Aug 22 14:13:05 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> Message-ID: <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > Seems my Alpine (2.26, 4/9/2024) client has started automatically sending an > EXPUNGE command after I mark a message deleted (in the INBOX). This wasn't > always the case and I'm not sure when it started but my guess is in the last > month or two. > > I can't seem to find a setting that controls this and a quick perusal of the > source doesn't clue me in. Anyone know what I may have done to myself? under settings -> config look for: [X] Expunge Only Manually [X] Expunge Without Confirming David Lang From alpine-info at u.washington.edu Thu Aug 22 14:24:16 2024 From: alpine-info at u.washington.edu (Doug Luce via Alpine-info) Date: Thu Aug 22 14:24:25 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> Message-ID: <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> Those were some of the first settings I messed with. Setting both (or either) doesn't seem to make any difference -- 'd' results in an EXPUNGE in all cases. Doug On Thu, 22 Aug 2024, David Lang wrote: > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > >> Seems my Alpine (2.26, 4/9/2024) client has started automatically sending >> an EXPUNGE command after I mark a message deleted (in the INBOX). This >> wasn't always the case and I'm not sure when it started but my guess is in >> the last month or two. >> >> I can't seem to find a setting that controls this and a quick perusal of >> the source doesn't clue me in. Anyone know what I may have done to myself? > > under settings -> config look for: > > [X] Expunge Only Manually > [X] Expunge Without Confirming > > David Lang > From alpine-info at u.washington.edu Thu Aug 22 16:01:47 2024 From: alpine-info at u.washington.edu (David Morris via Alpine-info) Date: Thu Aug 22 16:01:53 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> Message-ID: On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > Those were some of the first settings I messed with. Setting both (or > either) doesn't seem to make any difference -- 'd' results in an EXPUNGE in > all cases. > > Doug > > > On Thu, 22 Aug 2024, David Lang wrote: > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > Seems my Alpine (2.26, 4/9/2024) client has started automatically > > > sending an EXPUNGE command after I mark a message deleted (in the > > > INBOX). This wasn't always the case and I'm not sure when it started but > > > my guess is in the last month or two. > > > > > > I can't seem to find a setting that controls this and a quick perusal of > > > the source doesn't clue me in. Anyone know what I may have done to > > > myself? > > > > under settings -> config look for: > > > > [X] Expunge Only Manually > > [X] Expunge Without Confirming > > > > David Lang > > > > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > ---------- > > This email has been scanned for spam and viruses by Proofpoint Essentials. > Visit the following link to report this email as spam: > https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5faae2f2d91cc8ab0a54f33a290e37b01e4b2c8d5c4d5b56917864b4b8d8ca3c543dad47e03f6e1c1d6551e94bb52585e3c45cefd3e84bf1476513694596e94ee151f131c9b5cdd75d844122ca6aa37d2e427f01808f4216f4908b7b6e80cba8d5e4b0d785fe51cf0309bf57d3f614c14659ec37ab7de8d28c11d7a7779a8af0e0d5c77e17c51b8a25 > From alpine-info at u.washington.edu Thu Aug 22 16:07:29 2024 From: alpine-info at u.washington.edu (David Morris via Alpine-info) Date: Thu Aug 22 16:07:34 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> Message-ID: Sorry about the previous content free reply ... I'm running 2.26. My mail server and mail files are all on my local system where I run Alpine. I have not of the Expunge settings SET and expunge continues to work the way it always has ... it expunges when I use the eXpunge command, not when I mark deleted. If you are using a remote mail server, perhaps the provider changed something. If you, like me, are using a local server, we continue to have a mystery. On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > Those were some of the first settings I messed with. Setting both (or > either) doesn't seem to make any difference -- 'd' results in an EXPUNGE in > all cases. > > Doug > > > On Thu, 22 Aug 2024, David Lang wrote: > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > Seems my Alpine (2.26, 4/9/2024) client has started automatically > > > sending an EXPUNGE command after I mark a message deleted (in the > > > INBOX). This wasn't always the case and I'm not sure when it started but > > > my guess is in the last month or two. > > > > > > I can't seem to find a setting that controls this and a quick perusal of > > > the source doesn't clue me in. Anyone know what I may have done to > > > myself? > > > > under settings -> config look for: > > > > [X] Expunge Only Manually > > [X] Expunge Without Confirming > > > > David Lang > > > > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > ---------- > > This email has been scanned for spam and viruses by Proofpoint Essentials. > Visit the following link to report this email as spam: > https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5faae2f2d91cc8ab0a54f33a290e37b01e4b2c8d5c4d5b56917864b4b8d8ca3c543dad47e03f6e1c1d6551e94bb52585e3c45cefd3e84bf1476513694596e94ee151f131c9b5cdd75d844122ca6aa37d2e427f01808f4216f4908b7b6e80cba8d5e4b0d785fe51cf0309bf57d3f614c14659ec37ab7de8d28c11d7a7779a8af0e0d5c77e17c51b8a25 > From alpine-info at u.washington.edu Thu Aug 22 17:42:19 2024 From: alpine-info at u.washington.edu (Damion Yates via Alpine-info) Date: Thu Aug 22 17:42:35 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> Message-ID: +1 on checking the IMAP server, this is a common setting for some because the iPhone doesn't handle non-auto expunging on delete and it's the most common IMAP client. In GMail this is something you can enable/disable along with a variety of other settings, like only showing the latest 1,000 or doing "archive" rather than delete permanently. - Damion On Fri, Aug 23, 2024 at 12:11?AM David Morris via Alpine-info < alpine-info@u.washington.edu> wrote: > > Sorry about the previous content free reply ... > > I'm running 2.26. My mail server and mail files are all on my local system > where I run Alpine. I have not of the Expunge settings SET and expunge > continues to work the way it always has ... it expunges when I use the > eXpunge command, not when I mark deleted. > > If you are using a remote mail server, perhaps the provider changed > something. If you, like me, are using a local server, we continue to have > a mystery. > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > Those were some of the first settings I messed with. Setting both (or > > either) doesn't seem to make any difference -- 'd' results in an EXPUNGE > in > > all cases. > > > > Doug > > > > > > On Thu, 22 Aug 2024, David Lang wrote: > > > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > > > Seems my Alpine (2.26, 4/9/2024) client has started automatically > > > > sending an EXPUNGE command after I mark a message deleted (in the > > > > INBOX). This wasn't always the case and I'm not sure when it started > but > > > > my guess is in the last month or two. > > > > > > > > I can't seem to find a setting that controls this and a quick > perusal of > > > > the source doesn't clue me in. Anyone know what I may have done to > > > > myself? > > > > > > under settings -> config look for: > > > > > > [X] Expunge Only Manually > > > [X] Expunge Without Confirming > > > > > > David Lang > > > > > > > _______________________________________________ > > Alpine-info mailing list > > Alpine-info@u.washington.edu > > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > > > ---------- > > > > This email has been scanned for spam and viruses by Proofpoint > Essentials. > > Visit the following link to report this email as spam: > > > https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5faae2f2d91cc8ab0a54f33a290e37b01e4b2c8d5c4d5b56917864b4b8d8ca3c543dad47e03f6e1c1d6551e94bb52585e3c45cefd3e84bf1476513694596e94ee151f131c9b5cdd75d844122ca6aa37d2e427f01808f4216f4908b7b6e80cba8d5e4b0d785fe51cf0309bf57d3f614c14659ec37ab7de8d28c11d7a7779a8af0e0d5c77e17c51b8a25 > > > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > -- Damion Yates - damion.yates@gmail.com London, England -------------- next part -------------- An HTML attachment was scrubbed... URL: From alpine-info at u.washington.edu Thu Aug 22 22:45:19 2024 From: alpine-info at u.washington.edu (Doug Luce via Alpine-info) Date: Thu Aug 22 22:46:09 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> Message-ID: <447cb603-3e17-c537-1ef6-b0d0c0bdb71f@alpine.con.com> The remote IMAP server is my personal Dovecot instance which isn't configured to expunge on delete. I've updated neither binary nor config in a year or two. It appears to be the client doing this, at least that's my interpretation of this debug output: - delete message - DELETE: msg 65 imap_cmd(INBOX, STORE, 0x1) IMAP DEBUG 22:13:39 8/22: 01000061 STORE 65 +Flags (\DELETED) IMAP DEBUG 22:13:39 8/22: * 65 FETCH (FLAGS (\Deleted Old)) IMAP DEBUG 22:13:39 8/22: 01000061 OK Store completed (0.076 + 0.000 + 0.075 secs). ... Mail_Ping(INBOX): lastping=1 er=34 [forced] [current] 22:14:05.627864 imap_cmd(INBOX, NOOP, 0x0) IMAP DEBUG 22:14:05 8/22: 010000bf NOOP IMAP DEBUG 22:14:05 8/22: * 65 EXPUNGE mm_expunged({imap.server:993/imap/nostarttls/ssl/user="doug"}INBOX,65) mm_expunged: rawno=65 msgno=65 nmsgs=114644 max_msgno=114644 flagged_exld=0 IMAP DEBUG 22:14:05 8/22: 010000bf OK NOOP completed (0.003 + 0.000 + 0.002 secs). Ping complete: 22:14:05.644670 Logging on the server also shows the EXPUNGE coming from the client. It's happening on mailbox ping (like when I press ^L). The source shows `EXPUNGEATPING` and `expok` as potential (internal) triggers but it's not clear what specifically allows this to happen. Doug On Fri, 23 Aug 2024, Damion Yates via Alpine-info wrote: > +1 on checking the IMAP server, this is a common setting for some because the iPhone doesn't handle non-auto expunging on delete and it's the most common IMAP client. > In GMail this is something you can enable/disable along with a variety of other settings, like only showing the latest 1,000 or doing "archive" rather?than delete > permanently. > > ?- Damion > > On Fri, Aug 23, 2024 at 12:11?AM David Morris via Alpine-info wrote: > > Sorry about the previous content free reply ... > > I'm running 2.26. My mail server and mail files are all on my local system > where I run Alpine. I have not of the Expunge settings SET and expunge > continues to work the way it always has ... it expunges when I use the > eXpunge command, not when I mark deleted. > > If you are using a remote mail server, perhaps the provider changed > something. If you, like me, are using a local server, we continue to have > a mystery. > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > Those were some of the first settings I messed with. Setting both (or > > either) doesn't seem to make any difference -- 'd' results in an EXPUNGE in > > all cases. > > > > Doug > > > > > > On Thu, 22 Aug 2024, David Lang wrote: > > > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > > > Seems my Alpine (2.26, 4/9/2024) client has started automatically > > > > sending an EXPUNGE command after I mark a message deleted (in the > > > > INBOX). This wasn't always the case and I'm not sure when it started but > > > > my guess is in the last month or two. > > > > > > > > I can't seem to find a setting that controls this and a quick perusal of > > > > the source doesn't clue me in. Anyone know what I may have done to > > > > myself? > > > > > > under settings -> config look for: > > > > > >? ? ? [X]? Expunge Only Manually > > >? ? ? [X]? Expunge Without Confirming > > > > > > David Lang > > > > > > > _______________________________________________ > > Alpine-info mailing list > > Alpine-info@u.washington.edu > > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > > > ---------- > > > > This email has been scanned for spam and viruses by Proofpoint Essentials. > > Visit the following link to report this email as spam: > >https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5faae2f2d91cc8ab0a54f33a290e37b01 > e4b2c8d5c4d5b56917864b4b8d8ca3c543dad47e03f6e1c1d6551e94bb52585e3c45cefd3e84bf1476513694596e94ee151f131c9b5cdd75d844122ca6aa37d2e427f01808f4216f4908b7b6e80cba8d5e4b0d78 > 5fe51cf0309bf57d3f614c14659ec37ab7de8d28c11d7a7779a8af0e0d5c77e17c51b8a25 > > > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > > > -- > Damion Yates - damion.yates@gmail.com > London, England > > From alpine-info at u.washington.edu Fri Aug 23 05:31:26 2024 From: alpine-info at u.washington.edu (Damion Yates via Alpine-info) Date: Fri Aug 23 05:31:42 2024 Subject: [Alpine-info] Automatically expunging? In-Reply-To: <447cb603-3e17-c537-1ef6-b0d0c0bdb71f@alpine.con.com> References: <07874da2-bfa1-93e1-65f1-aa1090c2e49a@alpine.con.com> <07701430-32ns-34p3-54s0-4142n44o87ns@ynat.uz> <31c3cb28-6b58-5142-a997-9b2e46344fcc@alpine.con.com> <447cb603-3e17-c537-1ef6-b0d0c0bdb71f@alpine.con.com> Message-ID: Oh fair enough, that's quite odd. I would inspect your .pinerc by hand with alpine not running. Then you should make sure it's definitely the only one being loaded by alpine at startup, no system default is being picked up. I'm unsure which debug options will help with that, but perhaps `strace -o ~/log /usr/bin/alpine` and read through that, grep for open and see if you can see it reading in another pinerc with expunge settings turned on. Best wishes, - Damion On Fri, Aug 23, 2024 at 6:46?AM Doug Luce wrote: > The remote IMAP server is my personal Dovecot instance which isn't > configured to expunge on delete. I've updated neither binary nor > config in a year or two. > > It appears to be the client doing this, at least that's my > interpretation of this debug output: > > - delete message - > DELETE: msg 65 > imap_cmd(INBOX, STORE, 0x1) > IMAP DEBUG 22:13:39 8/22: 01000061 STORE 65 +Flags (\DELETED) > IMAP DEBUG 22:13:39 8/22: * 65 FETCH (FLAGS (\Deleted Old)) > IMAP DEBUG 22:13:39 8/22: 01000061 OK Store completed (0.076 + 0.000 > + 0.075 secs). > ... > Mail_Ping(INBOX): lastping=1 er=34 [forced] [current] 22:14:05.627864 > imap_cmd(INBOX, NOOP, 0x0) > IMAP DEBUG 22:14:05 8/22: 010000bf NOOP > IMAP DEBUG 22:14:05 8/22: * 65 EXPUNGE > mm_expunged({imap.server:993/imap/nostarttls/ssl/user="doug"}INBOX,65) > mm_expunged: rawno=65 msgno=65 nmsgs=114644 max_msgno=114644 > flagged_exld=0 > IMAP DEBUG 22:14:05 8/22: 010000bf OK NOOP completed (0.003 + 0.000 + > 0.002 secs). > Ping complete: 22:14:05.644670 > > Logging on the server also shows the EXPUNGE coming from the client. > > It's happening on mailbox ping (like when I press ^L). The source > shows `EXPUNGEATPING` and `expok` as potential (internal) triggers but > it's not clear what specifically allows this to happen. > > Doug > > > On Fri, 23 Aug 2024, Damion Yates via Alpine-info wrote: > > > +1 on checking the IMAP server, this is a common setting for some > because the iPhone doesn't handle non-auto expunging on delete and it's the > most common IMAP client. > > In GMail this is something you can enable/disable along with a variety > of other settings, like only showing the latest 1,000 or doing "archive" > rather than delete > > permanently. > > > > - Damion > > > > On Fri, Aug 23, 2024 at 12:11?AM David Morris via Alpine-info < > alpine-info@u.washington.edu> wrote: > > > > Sorry about the previous content free reply ... > > > > I'm running 2.26. My mail server and mail files are all on my > local system > > where I run Alpine. I have not of the Expunge settings SET and > expunge > > continues to work the way it always has ... it expunges when I use > the > > eXpunge command, not when I mark deleted. > > > > If you are using a remote mail server, perhaps the provider changed > > something. If you, like me, are using a local server, we continue > to have > > a mystery. > > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > Those were some of the first settings I messed with. Setting > both (or > > > either) doesn't seem to make any difference -- 'd' results in an > EXPUNGE in > > > all cases. > > > > > > Doug > > > > > > > > > On Thu, 22 Aug 2024, David Lang wrote: > > > > > > > On Thu, 22 Aug 2024, Doug Luce via Alpine-info wrote: > > > > > > > > > Seems my Alpine (2.26, 4/9/2024) client has started > automatically > > > > > sending an EXPUNGE command after I mark a message deleted > (in the > > > > > INBOX). This wasn't always the case and I'm not sure when it > started but > > > > > my guess is in the last month or two. > > > > > > > > > > I can't seem to find a setting that controls this and a > quick perusal of > > > > > the source doesn't clue me in. Anyone know what I may have > done to > > > > > myself? > > > > > > > > under settings -> config look for: > > > > > > > > [X] Expunge Only Manually > > > > [X] Expunge Without Confirming > > > > > > > > David Lang > > > > > > > > > > _______________________________________________ > > > Alpine-info mailing list > > > Alpine-info@u.washington.edu > > > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > > > > > ---------- > > > > > > This email has been scanned for spam and viruses by Proofpoint > Essentials. > > > Visit the following link to report this email as spam: > > > > https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5faae2f2d91cc8ab0a54f33a290e37b01 > > > e4b2c8d5c4d5b56917864b4b8d8ca3c543dad47e03f6e1c1d6551e94bb52585e3c45cefd3e84bf1476513694596e94ee151f131c9b5cdd75d844122ca6aa37d2e427f01808f4216f4908b7b6e80cba8d5e4b0d78 > > > 5fe51cf0309bf57d3f614c14659ec37ab7de8d28c11d7a7779a8af0e0d5c77e17c51b8a25 > > > > > _______________________________________________ > > Alpine-info mailing list > > Alpine-info@u.washington.edu > > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > > > > > > > > -- > > Damion Yates - damion.yates@gmail.com > > London, England > > > > > -- Damion Yates - damion.yates@gmail.com London, England -------------- next part -------------- An HTML attachment was scrubbed... URL: From alpine-info at u.washington.edu Sat Aug 31 04:40:13 2024 From: alpine-info at u.washington.edu (Bret Busby via Alpine-info) Date: Sat Aug 31 04:40:18 2024 Subject: [Alpine-info] Where do removed messages go Message-ID: Hello. I am running alpine 2.25 on Linux Mint Mate 21.3 . I have just exited alpine, a few minutes ago, and it displayed a message stating that, for the folder that I was exiting, a number of messages were saved, and, 1 message was removed. I do not know why it removed whichever message it removed. Has that message been vaporised, or, is it somewhere that it can be retrieved? In that particular folder, the messages are of very great importance to me, involving decades of work, and, indiscriminate removal of messages, especially without requiring verification of the desire to remove a message, is very harmful. So, I want to know where the message is now, if it still exists, so that I can find it, see what it is, and, restore it. Thank you in anticipation. .. Bret Busby Armadale West Australia (UTC+0800) .............. From alpine-info at u.washington.edu Sat Aug 31 08:14:48 2024 From: alpine-info at u.washington.edu (Eduardo Chappa via Alpine-info) Date: Sat Aug 31 08:15:00 2024 Subject: [Alpine-info] Where do removed messages go In-Reply-To: References: Message-ID: On Sat, 31 Aug 2024, Bret Busby via Alpine-info wrote: > Hello. > > I am running alpine 2.25 on Linux Mint Mate 21.3 . > > I have just exited alpine, a few minutes ago, and it displayed a message > stating that, for the folder that I was exiting, a number of messages > were saved, and, 1 message was removed. > > I do not know why it removed whichever message it removed. Dear Bret, I am sorry this happened. I am not aware of any circumstances under which Alpine would remove messages, except filtering. I imagine you do not have debug information that could be analyzed. Alpine does not save deleted messages to any specific folder, so whichever message was deleted is not recoverable. The only thing I can suggest is to create a filter in that folder that is active on deleted messages and saves them to another folder. Please let me know if you need any assistance from me. -- Eduardo From alpine-info at u.washington.edu Sat Aug 31 08:48:35 2024 From: alpine-info at u.washington.edu (Iosif Fettich via Alpine-info) Date: Sat Aug 31 08:48:41 2024 Subject: [Alpine-info] Where do removed messages go In-Reply-To: References: Message-ID: <32ce460e-8311-9f09-e565-9f24bf09001f@netsoft.ro> Hi Bret, >> I do not know why it removed whichever message it removed. Not forget the obvious: if you have some backups of that folder somewhere, maybe you're in luck and can find that particular message in one of those backups....? Good luck to you. Iosif Fettich