From alpine-info at u.washington.edu Fri Apr 18 10:07:16 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 10:07:21 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? Message-ID: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> Hi All: In several software synthesizers, while listening to an index of mail, it is processing dates in seemingly a European way. I think the real problems are the capitalized abreviations of months such as Apr. Message numbers above 31 don't have an issue. Some Linux screen-readers don't have an acception dictionary as many DOS-and-windows one do. Its rather confusing hearing "April first 2" I looked in an alpine man-page, only found 1 mention of date. Thanks so much in advance-and-by the way my DecTalk doesn't have an issue. Chime From alpine-info at u.washington.edu Fri Apr 18 11:57:50 2025 From: alpine-info at u.washington.edu (Mats Dufberg via Alpine-info) Date: Fri Apr 18 11:57:58 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> Message-ID: <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> Chime, I am not sure what your issue is, but I think that you do not like the way that Alpine write dates. That is, however, configurable. I have chosen DATEISO for e.g. the listing in the directory and the line that you see below. I prefer the ISO date format. Would that help you? Yours, Mats On 2025-04-18, 10:07 (-0700) Chime Hart via Alpine-info Hi All: In several software synthesizers, while listening to an index of mail, > it is processing dates in seemingly a European way. I think the real problems > are the capitalized abreviations of months such as Apr. Message numbers above > 31 don't have an issue. Some Linux screen-readers don't have an acception > dictionary as many DOS-and-windows one do. Its rather confusing hearing "April > first 2" I looked in an alpine man-page, only found 1 mention of date. Thanks > so much in advance-and-by the way my DecTalk doesn't have an issue. > Chime > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > ------------------------------------------------------ | Mats Dufberg | mats@dufberg.se | | Sp?nga kyrkv?g 618 | +46 8 38 48 59 | | SE-16362 Sp?nga, Sweden | +46 70 258 25 88 | ------------------------------------------------------ From alpine-info at u.washington.edu Fri Apr 18 12:43:41 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 12:43:46 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> Message-ID: <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> Hi Matt: I looked in .pinerc, did not find any other date formats? An only way I can consider to temporarily fix this would be to remove the word "date" from an index order, maybe then it will just read a message number without an abbreviated month-and-date. But if I knew how, I am willing to try your suggestion. Thanks so much in advance Chime From alpine-info at u.washington.edu Fri Apr 18 13:06:23 2025 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Fri Apr 18 13:06:29 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> Message-ID: <19b6d42f-a9ae-495e-9213-0a18c5d7eb34@telefonica.net> On 2025-04-18 21:43, Chime Hart via Alpine-info wrote: > Hi Matt: I looked in .pinerc, did not find any other date formats? An only way > I can consider to temporarily fix this would be to remove the word "date" from > an index order, maybe then it will just read a message number without an > abbreviated month-and-date. But if I knew how, I am willing to try your > suggestion. Thanks so much in advance > Chime In file ".pinerc", I have this: # Specifies the introduction to insert when replying to a message. reply-leadin=El _DATEISO_ a las _TIME24_ _TIMEZONE_, _FROM_ escribi?: empty-header-message= ... # This gives a format for displaying the index. It is made # up of space-delimited tokens telling which fields are displayed and in # which order. See help text index-format=STATUS MSGNO SHORTDATEISO TIME24 FROM(20%) ADDRESSTO(10%) SIZE ATT SUBJECT(75%) There may be more places. And you can create your own line. -- Cheers / Saludos, Carlos E. R. (from 15.6 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 Fri Apr 18 13:32:44 2025 From: alpine-info at u.washington.edu (Andreas Schamanek via Alpine-info) Date: Fri Apr 18 13:32:52 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> Message-ID: <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> Hi Chime, What Carlos referred to in .pinerc you can find in the config menu (keys M + S + C) under "Index Format". When your cursor is highlighting this entry you can go to Help and find how the index format can be changed. There, on the 1st page is then a link to Help on index tokens -> x-alpine-help:h_index_tokens This lists and describes all possible ways to configure time and date. Be warned it's a lot. Practically everything is possible. It might be easier for you to let us know what kind of format you'd prefer, and some helpful souls will look up the tokens. Also, I know, there are people on this list who use screen readers. So, maybe, they can recommend some settings. I have no idea what might work best for screen readers. -- -- Andreas :-) From alpine-info at u.washington.edu Fri Apr 18 13:37:29 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 13:37:34 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <19b6d42f-a9ae-495e-9213-0a18c5d7eb34@telefonica.net> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <19b6d42f-a9ae-495e-9213-0a18c5d7eb34@telefonica.net> Message-ID: Well, thanks Carlos-and-an earlier suggestion: Well, I switched from my DecTalk to software speech. I certainly will remove the time, but its still rather miss-leading. An early section of an index message looks like -> 1 25-03-05 4:12pm but reads as 1 March 25 2005 It is message 1 on March 25 but the date-and-month are in the wrong order. Thanks in advance Chime From alpine-info at u.washington.edu Fri Apr 18 13:55:40 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 13:55:46 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <19b6d42f-a9ae-495e-9213-0a18c5d7eb34@telefonica.net> Message-ID: At least after removing date, now at least it reads the message number correctly. Thanks in advance Chime From alpine-info at u.washington.edu Fri Apr 18 14:35:35 2025 From: alpine-info at u.washington.edu (Mats Dufberg via Alpine-info) Date: Fri Apr 18 14:35:44 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> Message-ID: <08098c88-a77d-252c-df35-179422fc985b@dufberg.se> Chime, I have the following in .pinerc with "DATEISO": reply-leadin=On _DATEISO_, _TIME24_ (_TIMEZONE_) _FROM_ <_ADDRESS_> wrote: index-format=FULLSTATUS MSGNO DATEISO FROMORTO(33%) SIZE SUBJECT(67%) If you use the setup function in Alpine and press "?" you can get some help on the various "tags" you can use. Yours, Mats On 2025-04-18, 12:43 (-0700) Chime Hart wrote: > Hi Matt: I looked in .pinerc, did not find any other date formats? An only way > I can consider to temporarily fix this would be to remove the word "date" from > an index order, maybe then it will just read a message number without an > abbreviated month-and-date. But if I knew how, I am willing to try your > suggestion. Thanks so much in advance > Chime > > ------------------------------------------------------ | Mats Dufberg | mats@dufberg.se | | Sp?nga kyrkv?g 618 | +46 8 38 48 59 | | SE-16362 Sp?nga, Sweden | +46 70 258 25 88 | ------------------------------------------------------ From alpine-info at u.washington.edu Fri Apr 18 16:13:14 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 16:13:19 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> Message-ID: <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> Thanks Andreas: I would prefer the date listed as april 18 2025 As I mentioned off-list to Mats, I took the date out, now it reads alot faster with no confusion. Chime From alpine-info at u.washington.edu Fri Apr 18 17:41:05 2025 From: alpine-info at u.washington.edu (Andreas Schamanek via Alpine-info) Date: Fri Apr 18 17:41:11 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> Message-ID: <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> On Sat, 19 Apr 2025, at 01:13, Chime Hart wrote: > I would prefer the date listed as > april 18 2025 This can be achieved with the tokens MONTHLONG DAY YEAR A similar option with short month names and a comma is LONGDATE. It should result in Apr 18, 2025 BTW, long/full month names _and_ a comma, so for instance April 18, 2025 are not possible AFAICT b/c Alpine always puts a space between the text of individual tokens. -- -- Andreas :-) From alpine-info at u.washington.edu Fri Apr 18 18:48:53 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 18 18:48:59 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> Message-ID: Thanks Andreas, will try your example. I figured if we stayed away from capitalized months it would be less likely to mangle. Chime From alpine-info at u.washington.edu Fri Apr 18 21:03:57 2025 From: alpine-info at u.washington.edu (Karen Lewellen via Alpine-info) Date: Fri Apr 18 21:04:28 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> Message-ID: Hi chime, I am wondering if the mangling is tied to the screen reader software you are using? speaking personally, I am surprised one cannot customize how capitalization's are spoken. I keep mine off, unless editing, but I am using DOS. For the record, at least according to recent google accessibility posts, you cannot customize accessibility settings with some of their tools either..which is frankly nonsensical. Karen On Fri, 18 Apr 2025, Chime Hart via Alpine-info wrote: > Thanks Andreas, will try your example. I figured if we stayed away from > capitalized months it would be less likely to mangle. > Chime > > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman12.u.washington.edu/mailman/listinfo/alpine-info > From alpine-info at u.washington.edu Sat Apr 19 04:15:33 2025 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Sat Apr 19 04:15:39 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> Message-ID: <3d1712ff-464d-41cd-93b9-92a27e3ea4d2@telefonica.net> On 2025-04-19 02:41, Andreas Schamanek via Alpine-info wrote: > > On Sat, 19 Apr 2025, at 01:13, Chime Hart wrote: > >> I would prefer the date listed as >> april 18 2025 > > This can be achieved with the tokens > > ? MONTHLONG DAY YEAR > > A similar option with short month names and a comma is LONGDATE. It > should result in > > ? Apr 18, 2025 Would not the format of LONGDATE depend on the locale? [...] Yes. I just made a quick test. It is "abr 19, 2025" here. -- Cheers / Saludos, Carlos E. R. (from 15.6 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 Sat Apr 19 04:34:41 2025 From: alpine-info at u.washington.edu (Andreas Schamanek via Alpine-info) Date: Sat Apr 19 04:34:46 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <3d1712ff-464d-41cd-93b9-92a27e3ea4d2@telefonica.net> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> <3d1712ff-464d-41cd-93b9-92a27e3ea4d2@telefonica.net> Message-ID: <0b4d6bb4-6e55-1711-6752-5fedb827bb49@fam.tuwien.ac.at> On Sat, 19 Apr 2025, at 03:48, Chime Hart wrote: > Thanks Andreas, will try your example. I figured if we stayed away from > capitalized months it would be less likely to mangle. Sorry that I missed the fact that you wanted non-capitalized months. On Sat, 19 Apr 2025, at 13:15, Carlos E. R. via Alpine-info wrote: > Would not the format of LONGDATE depend on the locale? [...] > Yes. I just made a quick test. It is "abr 19, 2025" here. I was wondering, too. Thanks for testing it. What locale did you use to get non-capitalized months? All the ones available to me use capital letters. For completeness, this also depends on the setting of "Disable Index Locale Dates". -- -- Andreas :-) From alpine-info at u.washington.edu Sat Apr 19 05:17:02 2025 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Sat Apr 19 05:17:10 2025 Subject: [Alpine-info] Any Other Way of Alpine Reading Dates? In-Reply-To: <0b4d6bb4-6e55-1711-6752-5fedb827bb49@fam.tuwien.ac.at> References: <9eee8947-2870-dbdd-b572-33e829c93152@hubert-humphrey.com> <81ac2916-fa4a-0056-9980-9ef19c856210@dufberg.se> <7c19922a-bbe6-6550-78d6-fabe18abfb6a@hubert-humphrey.com> <3ddae373-e6e6-36bb-9de5-ffcb582d65fc@fam.tuwien.ac.at> <2e40624e-95db-9329-6b48-53ae3452c2a5@hubert-humphrey.com> <82c63a2e-36cd-dbdf-5c1c-f3bf7a1794f8@fam.tuwien.ac.at> <3d1712ff-464d-41cd-93b9-92a27e3ea4d2@telefonica.net> <0b4d6bb4-6e55-1711-6752-5fedb827bb49@fam.tuwien.ac.at> Message-ID: On 2025-04-19 13:34, Andreas Schamanek via Alpine-info wrote: > On Sat, 19 Apr 2025, at 03:48, Chime Hart wrote: > >> Thanks Andreas, will try your example. I figured if we stayed away? from >> capitalized months it would be less likely to mangle. > > Sorry that I missed the fact that you wanted non-capitalized months. > > On Sat, 19 Apr 2025, at 13:15, Carlos E. R. via Alpine-info wrote: > >> Would not the format of LONGDATE depend on the locale? [...] >> Yes. I just made a quick test. It is "abr 19, 2025" here. > > I was wondering, too. Thanks for testing it. > > What locale did you use to get non-capitalized months? All the ones > available to me use capital letters. cer@Telcontar:~> espaniol locale LANG=es_ES.UTF-8 LC_CTYPE="es_ES.UTF-8" LC_NUMERIC="es_ES.UTF-8" LC_TIME="es_ES.UTF-8" LC_COLLATE="es_ES.UTF-8" LC_MONETARY="es_ES.UTF-8" LC_MESSAGES="es_ES.UTF-8" LC_PAPER="es_ES.UTF-8" LC_NAME="es_ES.UTF-8" LC_ADDRESS="es_ES.UTF-8" LC_TELEPHONE="es_ES.UTF-8" LC_MEASUREMENT="es_ES.UTF-8" LC_IDENTIFICATION="es_ES.UTF-8" LC_ALL=es_ES.UTF-8 cer@Telcontar:~> In Spanish, months are not capitalized. > For completeness, this also depends on the setting of "Disable Index > Locale Dates". I just tried Alpine with the above locale. I know Alpine itself is not translated: long ago I looked into it, but when I saw the strings in Alpine I saw that it was impossible, many strings are impossibly long (paragraphs). Mostly the help, it is internal to the code. So I had to remove my offer of translation. I was sad. -- Cheers / Saludos, Carlos E. R. (from 15.6 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 Tue Apr 22 10:42:55 2025 From: alpine-info at u.washington.edu (George Gutman via Alpine-info) Date: Tue Apr 22 10:43:10 2025 Subject: [Alpine-info] Converting GMail to Mbox format Message-ID: Does anyone have experience converting GMail to Mbox format that can be used by Alpine? I've tried Google's Takeout utility but have had serious problems with the results. George Gutman -------------- next part -------------- An HTML attachment was scrubbed... URL: From alpine-info at u.washington.edu Tue Apr 22 12:27:19 2025 From: alpine-info at u.washington.edu (via Alpine-info) Date: Tue Apr 22 12:27:25 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: References: Message-ID: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> > Does anyone have experience converting GMail to Mbox format that can be > used by Alpine? There are a number of ways to do this. First, Alpine can directly connect to Gmail and read your Gmail mail online, without any kind of mirroring or conversion. This is thoroughly documented on the Alpine website, and, for most folks, this is probably the best option. Second, you can use various tools to mirror your Gmail mail to a local machine, and then Alpine can read the mail from the local copy. My favorite tool for this is OfflineIMAP. OfflineIMAP can be configured to do one-way mirroring (changes to the local copy never affect the remote Gmail copy; deleting the local copy of a message will *not* delete it on the server) or two-way mirroring (changes to the local copy are pushed back to the server; deleting the local copy of a message *will* delete it on the server), and you can choose whichever you prefer for your use-case. By default OfflineIMAP stores messages in maildir format, which is the fastest and most secure local mailbox format and is completely compatible with Alpine; but you can also convert the local mailbox format to mbox or any other standard mailbox format if you're using some ancient legacy program that doesn't support maildir. Fetchmail is another tool that can be used to mirror Gmail to a local maildir or mbox. I don't use this, but a number of other folks on this list do, so you can probably get help if you run into problems. Good luck! -Jason From alpine-info at u.washington.edu Tue Apr 22 12:54:07 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Tue Apr 22 12:54:13 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> Message-ID: <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> Hi All-and-thanks, I installed offlineimap in Debian SID. Back around March 04 I asked in comp.mail.pine about converting a long file of Clari articles. If some1 can please download this 15mb file-and-suggest any way of having each of these as individual messages. https://hubert-humphrey.com/clari.mbox I suppose its possible that file is not already an mbox. Thanks so much in advance. Chime From alpine-info at u.washington.edu Tue Apr 22 13:15:44 2025 From: alpine-info at u.washington.edu (Carlos E. R. via Alpine-info) Date: Tue Apr 22 13:15:50 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> Message-ID: On 2025-04-22 21:27, via Alpine-info wrote: > >> Does anyone have experience converting GMail to Mbox format that can >> be used by Alpine? > > There are a number of ways to do this. > > First, Alpine can directly connect to Gmail and read your Gmail mail > online, without any kind of mirroring or conversion.? This is thoroughly > documented on the Alpine website, and, for most folks, this is probably > the best option. > > Second, you can use various tools to mirror your Gmail mail to a local > machine, and then Alpine can read the mail from the local copy.? My > favorite tool for this is OfflineIMAP. I have used "imapsync" to sync imap folders to a local computer, but it talks to a local imap server, like Dovecot. It is up to dovecot to decide how the local storage is done, and I do it on Mbox. -- Cheers / Saludos, Carlos E. R. (from 15.6 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 Wed Apr 23 08:02:19 2025 From: alpine-info at u.washington.edu (via Alpine-info) Date: Wed Apr 23 08:02:26 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> Message-ID: <2f0d775f-6cdd-3907-f365-64206360316c@shalott.net> > If some1 can please download this 15mb file-and-suggest any way of > having each of these as individual messages. > > https://hubert-humphrey.com/clari.mbox > > I suppose its possible that file is not already an mbox. Thanks so much > in advance. It looks like an mbox file to me. In the past, I have used this script to convert mbox to maildir: http://untroubled.org/mbox2maildir Download it to your Linux machine, and then run it as: perl mbox2maildir clari.mbox clari.maildir and you should be left with the messages as one-per-file in clari.maildir/new/. -Jason From alpine-info at u.washington.edu Wed Apr 23 17:01:59 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Wed Apr 23 17:02:04 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: <2f0d775f-6cdd-3907-f365-64206360316c@shalott.net> References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> <2f0d775f-6cdd-3907-f365-64206360316c@shalott.net> Message-ID: <9dc07034-be7e-7370-45ca-f83088fbf41d@hubert-humphrey.com> Thank you much Jason: I downloaded your script to a clari directory, ran on a clari.world.top.mbox got the following even after running a chmod 755 on your script Can't locate stat.pl in @INC (@INC entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.40.1 /usr/local/share/perl/5.40.1 /usr/lib/x86_64-linux-gnu/perl5/5.40 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.40 /usr/share/perl/5.40 /usr/local/lib/site_perl) at mbox2maildir line I am in TCSH if that matters or maybe I need to run your script with a ./ Chime From alpine-info at u.washington.edu Thu Apr 24 21:17:37 2025 From: alpine-info at u.washington.edu (via Alpine-info) Date: Thu Apr 24 21:17:41 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: <9dc07034-be7e-7370-45ca-f83088fbf41d@hubert-humphrey.com> References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> <2f0d775f-6cdd-3907-f365-64206360316c@shalott.net> <9dc07034-be7e-7370-45ca-f83088fbf41d@hubert-humphrey.com> Message-ID: > got the following even after running a chmod 755 on your script > Can't locate stat.pl in @INC You can edit that script and safely delete line 12, the one that contains "stat.pl". Once you remove that line, the script should run. -Jason From alpine-info at u.washington.edu Fri Apr 25 05:39:13 2025 From: alpine-info at u.washington.edu (Chime Hart via Alpine-info) Date: Fri Apr 25 05:39:19 2025 Subject: [Alpine-info] Converting GMail to Mbox format In-Reply-To: References: <951389ff-d9e0-0235-dfd4-77edd32b7cc5@shalott.net> <1ce910bc-5c84-bc4b-c031-862c6774b0a3@hubert-humphrey.com> <2f0d775f-6cdd-3907-f365-64206360316c@shalott.net> <9dc07034-be7e-7370-45ca-f83088fbf41d@hubert-humphrey.com> Message-ID: <0c0e6ef1-69c3-04ae-e058-88a64ef7bad1@hubert-humphrey.com> Hi Jason-and-thank you. I was away earlier this week, now cannot find your commands to run your script. Thanks so much in advance Chime