From john.thurston at alaska.gov Tue Apr 1 19:22:22 2025 From: john.thurston at alaska.gov (John Thurston) Date: Tue, 1 Apr 2025 10:22:22 -0800 Subject: [ZendTo] Making an instance read-only References: <713ae86e-4110-4f4e-84af-92c12edddb86@alaska.gov> Message-ID: Is there a simple way to render an instance of ZendTo 'read only' from the user-perspective? That is, to allow the use of existing links to download files, but to prevent anyone from creating new 'drops' ? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska -------------- next part -------------- An HTML attachment was scrubbed... URL: From klou at themusiclink.net Tue Apr 1 20:39:43 2025 From: klou at themusiclink.net (Kris Lou) Date: Tue, 1 Apr 2025 12:39:43 -0700 Subject: [ZendTo] Making an instance read-only In-Reply-To: References: <713ae86e-4110-4f4e-84af-92c12edddb86@alaska.gov> Message-ID: On Tue, Apr 1, 2025 at 11:22?AM John Thurston via ZendTo wrote: > Is there a simple way to render an instance of ZendTo 'read only' from the > user-perspective? > > That is, to allow the use of existing links to download files, but to > prevent anyone from creating new 'drops' ? > > > Maybe block ./req.php and ./verify.php ? I suppose it would be nicer to redirect those requests to an error page explaining that it's read only. And should probably inflate "numberOfDaysToRetain" as necessary. Kris Lou klou at themusiclink.neto -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.thurston at alaska.gov Tue Apr 22 18:28:33 2025 From: john.thurston at alaska.gov (John Thurston) Date: Tue, 22 Apr 2025 09:28:33 -0800 Subject: [ZendTo] Web site certificate expiration References: <44f0f5d6-7cfd-4e9d-9256-f3faac8428bd@alaska.gov> Message-ID: From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a couple of months. > Certificate chain > ?0 s:CN=zend.to > ?? i:C=US, O=Let's Encrypt, CN=E5 > ?? a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384 > ?? v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22 14:45:29 > 2025 GMT Will it come back? Has anyone heard from Jules in the last three months? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssilva at sgvwater.com Tue Apr 22 18:44:12 2025 From: ssilva at sgvwater.com (Scott Silva) Date: Tue, 22 Apr 2025 17:44:12 +0000 Subject: [ZendTo] Web site certificate expiration In-Reply-To: References: <44f0f5d6-7cfd-4e9d-9256-f3faac8428bd@alaska.gov> Message-ID: I know thru the years Jules has had health problems. Maybe he is in the hospital again? I have been involved with his work since way back in the Mailscanner days? From: ZendTo On Behalf Of John Thurston via ZendTo Sent: Tuesday, April 22, 2025 10:29 AM To: ZendTo List Cc: John Thurston Subject: [ZendTo] Web site certificate expiration From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a coup External sender > Make sure you trust this sender before taking any actions. From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a couple of months. Certificate chain 0 s:CN=zend.to i:C=US, O=Let's Encrypt, CN=E5 a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384 v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22 14:45:29 2025 GMT Will it come back? Has anyone heard from Jules in the last three months? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska This email transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential, privileged and/or proprietary information for the sole use of the intended recipient(s). If you are not an intended recipient or a person responsible for delivering it to an intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is strictly prohibited. If you have received this transmission in error, please: (1) immediately notify me by reply e-mail; and (2) destroy the original (and any copies) of this transmission and its attachments without reading or saving in any manner. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthewf at prolific.ca Tue Apr 22 18:51:39 2025 From: matthewf at prolific.ca (Matthew Fey) Date: Tue, 22 Apr 2025 17:51:39 +0000 Subject: [ZendTo] Web site certificate expiration In-Reply-To: References: <44f0f5d6-7cfd-4e9d-9256-f3faac8428bd@alaska.gov> Message-ID: I haven?t seen anything from him since the mailing list in November, but 6.15-7 was released on Feb 11, so it appears he was active up until then at least, assuming he?s the one releasing the updates. From: ZendTo On Behalf Of Scott Silva via ZendTo Sent: April 22, 2025 12:44 PM To: ZendTo Users Cc: Scott Silva Subject: Re: [ZendTo] Web site certificate expiration I know thru the years Jules has had health problems. Maybe he is in the hospital again? I have been involved with his work since way back in the Mailscanner days? From: ZendTo On Behalf Of John Thurston via ZendTo Sent: Tuesday, April 22, 2025 10:29 AM To: ZendTo List Cc: John Thurston Subject: [ZendTo] Web site certificate expiration From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a coup External sender > Make sure you trust this sender before taking any actions. From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a couple of months. Certificate chain 0 s:CN=zend.to i:C=US, O=Let's Encrypt, CN=E5 a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384 v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22 14:45:29 2025 GMT Will it come back? Has anyone heard from Jules in the last three months? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska This email transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential, privileged and/or proprietary information for the sole use of the intended recipient(s). If you are not an intended recipient or a person responsible for delivering it to an intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is strictly prohibited. If you have received this transmission in error, please: (1) immediately notify me by reply e-mail; and (2) destroy the original (and any copies) of this transmission and its attachments without reading or saving in any manner. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jules at zend.to Wed Apr 23 10:54:21 2025 From: jules at zend.to (jules at zend.to) Date: Wed, 23 Apr 2025 10:54:21 +0100 Subject: [ZendTo] Web site certificate expiration In-Reply-To: References: <44f0f5d6-7cfd-4e9d-9256-f3faac8428bd@alaska.gov> Message-ID: Hi folks! Don't worry, I'm still alive. :-) And not even been in hospital (apart from the odd scan so they can keep an eye on me) :-O Just been super-busy at work. Sorry about the website cert, just fixed it. And yes, I must fix the broken apt repo. Think I'm better off deleting it altogether and creating a new one, rather than trying to resurrect the existing one as lots of things appear to have changed over the years. Anyone know any good guides on constructing an apt repo from scratch if you've already got a GPG key? That would help speed things up a lot... Thanks! Jules. On 22/04/2025 6:51 pm, Matthew Fey via ZendTo wrote: > > I haven?t seen anything from him since the mailing list in November, > but 6.15-7 was released on Feb 11, so it appears he was active up > until then at least, assuming he?s the one releasing the updates. > > *From:*ZendTo *On Behalf Of *Scott Silva via > ZendTo > *Sent:* April 22, 2025 12:44 PM > *To:* ZendTo Users > *Cc:* Scott Silva > *Subject:* Re: [ZendTo] Web site certificate expiration > > I know thru the years Jules has had health problems. Maybe he is in > the hospital again? > > I have been involved with his work since way back in the Mailscanner days? > > *From:*ZendTo *On Behalf Of *John Thurston > via ZendTo > *Sent:* Tuesday, April 22, 2025 10:29 AM > *To:* ZendTo List > *Cc:* John Thurston > *Subject:* [ZendTo] Web site certificate expiration > > From my perspective, the cert at zend.to (port 443) is expired. It > appears to have been a Let's Encrypt cert, so should have been > scripted to auto-renew. My read of this is no one has been watching > the server error-logs for a coup > > *External sender* > Make sure you trust this sender before taking any actions. > > From my perspective, the cert at zend.to (port 443) is expired. It > appears to have been a Let's Encrypt cert, so should have been > scripted to auto-renew. My read of this is no one has been watching > the server error-logs for a couple of months. > > Certificate chain > ?0 s:CN=zend.to > ?? i:C=US, O=Let's Encrypt, CN=E5 > ?? a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384 > ?? v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22 > 14:45:29 2025 GMT > > Will it come back? > Has anyone heard from Jules in the last three months? > > -- > -- > Do things because you should, not just because you can. > John Thurston??? 907-465-8591 > John.Thurston at alaska.gov > Department of Administration > State of Alaska > > This email transmission, and any documents, files or previous e-mail > messages attached to it, may contain confidential, privileged and/or > proprietary information for the sole use of the intended recipient(s). > If you are not an intended recipient or a person responsible for > delivering it to an intended recipient, any disclosure, copying, > distribution or use of any of the information contained in or attached > to this transmission is strictly prohibited. If you have received this > transmission in error, please: (1) immediately notify me by reply > e-mail; and (2) destroy the original (and any copies) of this > transmission and its attachments without reading or saving in any manner. > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE 'Teach a man to reason, and he will think for a lifetime.' - Phil Plait www.Zend.To -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jules at Zend.To Thu Apr 24 15:05:43 2025 From: Jules at Zend.To (Jules Field) Date: Thu, 24 Apr 2025 15:05:43 +0100 Subject: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed References: <87f40a93-8859-414a-8d26-32efb7f7885c@Zend.To> Message-ID: Hi folks, I have finally fixed the apt repository on the zend.to website. I wiped it and rebuilt it using totally different tools. Please note that all the steps required to setup the repo on https://zend.to/apt.php have changed, so please ensure you do at least steps 2 and 3 on that page to install the new version of the repo correctly. Many thanks for your patience! Jules -- Julian Field MEng CEng CITP MBCS MIEEE 'Intelligence is quickness to apprehend as distinct from ability, which is capacity to act wisely on the thing apprehended.' - Alfred North Whitehead www.Zend.To -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssilva at sgvwater.com Thu Apr 24 16:07:47 2025 From: ssilva at sgvwater.com (Scott Silva) Date: Thu, 24 Apr 2025 15:07:47 +0000 Subject: [ZendTo] Web site certificate expiration In-Reply-To: References: <44f0f5d6-7cfd-4e9d-9256-f3faac8428bd@alaska.gov> Message-ID: Glad to hear you are doing OK? I remember the hospital time back in the early Mailscanner days From: ZendTo On Behalf Of Julian Field via ZendTo Sent: Wednesday, April 23, 2025 2:54 AM To: ZendTo Users Cc: jules at zend.to Subject: Re: [ZendTo] Web site certificate expiration Hi folks! Don't worry, I'm still alive. :-) And not even been in hospital (apart from the odd scan so they can keep an eye on me) :-O Just been super-busy at work. Sorry about the website cert, just fixed it. And yes, I Warning: Unusual link This message contains an unusual link, which may lead to a malicious site. Confirm the message is safe before clicking any links. Hi folks! Don't worry, I'm still alive. :-) And not even been in hospital (apart from the odd scan so they can keep an eye on me) :-O Just been super-busy at work. Sorry about the website cert, just fixed it. And yes, I must fix the broken apt repo. Think I'm better off deleting it altogether and creating a new one, rather than trying to resurrect the existing one as lots of things appear to have changed over the years. Anyone know any good guides on constructing an apt repo from scratch if you've already got a GPG key? That would help speed things up a lot... Thanks! Jules. On 22/04/2025 6:51 pm, Matthew Fey via ZendTo wrote: I haven?t seen anything from him since the mailing list in November, but 6.15-7 was released on Feb 11, so it appears he was active up until then at least, assuming he?s the one releasing the updates. From: ZendTo On Behalf Of Scott Silva via ZendTo Sent: April 22, 2025 12:44 PM To: ZendTo Users Cc: Scott Silva Subject: Re: [ZendTo] Web site certificate expiration I know thru the years Jules has had health problems. Maybe he is in the hospital again? I have been involved with his work since way back in the Mailscanner days? From: ZendTo On Behalf Of John Thurston via ZendTo Sent: Tuesday, April 22, 2025 10:29 AM To: ZendTo List Cc: John Thurston Subject: [ZendTo] Web site certificate expiration From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a coup External sender > Make sure you trust this sender before taking any actions. From my perspective, the cert at zend.to (port 443) is expired. It appears to have been a Let's Encrypt cert, so should have been scripted to auto-renew. My read of this is no one has been watching the server error-logs for a couple of months. Certificate chain 0 s:CN=zend.to i:C=US, O=Let's Encrypt, CN=E5 a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384 v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22 14:45:29 2025 GMT Will it come back? Has anyone heard from Jules in the last three months? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska This email transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential, privileged and/or proprietary information for the sole use of the intended recipient(s). If you are not an intended recipient or a person responsible for delivering it to an intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is strictly prohibited. If you have received this transmission in error, please: (1) immediately notify me by reply e-mail; and (2) destroy the original (and any copies) of this transmission and its attachments without reading or saving in any manner. _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto Jules -- Julian Field MEng CEng CITP MBCS MIEEE 'Teach a man to reason, and he will think for a lifetime.' - Phil Plait www.Zend.To -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonp at mwsco.com Thu Apr 24 18:01:38 2025 From: jasonp at mwsco.com (Jason Passow) Date: Thu, 24 Apr 2025 12:01:38 -0500 Subject: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed In-Reply-To: References: <1756947968-3854996@KMS.mwsco.com> Message-ID: I used the new repo instructions and receive the following errors: Err:11 https://zend.to/apt lynx Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:12 https://zend.to/apt trusty Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:13 https://zend.to/apt xenial Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:14 https://zend.to/apt bionic Release ? 404 ?Not Found [IP: 46.22.137.105 443] Reading package lists... Done E: The repository 'http://zend.to/apt lynx Release' does not have a Release file ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? . N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt trusty Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt xenial Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt bionic Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. This is on a 24.04 ubuntu server.? Jason Passow | Network Administrator o: (507) 494-5178 |?c: (507) 450-8178 | jasonp at mwsco.com 5150 West 6th Street, Winona, MN?55987 www.mwsco.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbe2 at lehigh.edu Thu Apr 24 18:53:51 2025 From: kbe2 at lehigh.edu (Keith Erekson) Date: Thu, 24 Apr 2025 13:53:51 -0400 Subject: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed In-Reply-To: References: <1756947968-3854996@KMS.mwsco.com> <2a5b8d86-e309-4d91-9f65-1984d5bd65bd@lehigh.edu> Message-ID: I also used the new repo instructions, and it worked fine. Looks like you might have an old repo for zendto. Check in /etc/apt/sources.list.d, and maybe grep for "lynx"? If you installed the new repo's deb package, the contents of /etc/apt/sources.list.d/zendto.list will be just a single line: deb [signed-by=/usr/share/keyrings/zendto.gpg.asc]https://zend.to/apt stable main ~Keith On 4/24/25 1:01 PM, Jason Passow via ZendTo wrote: > I used the new repo instructions and receive the following errors: > > Err:11 https://zend.to/apt lynx Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:12 https://zend.to/apt trusty Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:13 https://zend.to/apt xenial Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:14 https://zend.to/apt bionic Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Reading package lists... Done > E: The repository 'http://zend.to/apt lynx Release' does not have a > Release file ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? . > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt trusty Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt xenial Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt bionic Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > > > This is on a 24.04 ubuntu server. > > *Jason Passow* | Network Administrator > > o: (507) 494-5178 |?c: (507) 450-8178 | jasonp at mwsco.com > 5150 West 6^th Street, Winona, MN?55987 > www.mwsco.com > > > MWS Logo > VOSB Logo > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonp at mwsco.com Thu Apr 24 19:20:55 2025 From: jasonp at mwsco.com (Jason Passow) Date: Thu, 24 Apr 2025 13:20:55 -0500 Subject: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed In-Reply-To: References: <1762133609-3886243@KMS.mwsco.com> Message-ID: Oops. Turns out that lack of sleep is getting to me. I did remove all zendto repos and used only the new one. Those errors are now gone.? Jason Passow | Network Administrator o: (507) 494-5178 |?c: (507) 450-8178 | jasonp at mwsco.com 5150 West 6th Street, Winona, MN?55987 www.mwsco.com From: To: Sent: 4/24/2025 12:54 PM Subject: [External Email] ZendTo Digest, Vol 163, Issue 5 Send ZendTo mailing list submissions to ? ? zendto at zend.to To subscribe or unsubscribe via the World Wide Web, visit ? ? http://jul.es/mailman/listinfo/zendto or, via email, send a message with subject or body 'help' to ? ? zendto-request at zend.to You can reach the person managing the list at ? ? zendto-owner at zend.to When replying, please edit your Subject line so it is more specific than "Re: Contents of ZendTo digest..." Today's Topics: ? 1. Re: ANNOUNCE: ZendTo APT repo finally fixed (Jason Passow) ? 2. Re: ANNOUNCE: ZendTo APT repo finally fixed (Keith Erekson) ---------------------------------------------------------------------- Message: 1 Date: Thu, 24 Apr 2025 12:01:38 -0500 From: Jason Passow To: zendto at zend.to Subject: Re: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed Message-ID: ? ? ? ? Content-Type: text/plain; charset="utf-8" I used the new repo instructions and receive the following errors: Err:11 https://zend.to/apt lynx Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:12 https://zend.to/apt trusty Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:13 https://zend.to/apt xenial Release ? 404 ?Not Found [IP: 46.22.137.105 443] Err:14 https://zend.to/apt bionic Release ? 404 ?Not Found [IP: 46.22.137.105 443] Reading package lists... Done E: The repository 'http://zend.to/apt lynx Release' does not have a Release file ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? . N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt trusty Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt xenial Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. E: The repository 'http://zend.to/apt bionic Release' does not have a Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. N: Updating from such a repository can't be done securely, and is therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. This is on a 24.04 ubuntu server.? Jason Passow ?| Network Administrator o: (507) 494-5178 |?c: (507) 450-8178 | jasonp at mwsco.com 5150 West 6th Street, Winona, MN?55987 www.mwsco.com -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Thu, 24 Apr 2025 13:53:51 -0400 From: Keith Erekson To: Jason Passow via ZendTo Subject: Re: [ZendTo] ANNOUNCE: ZendTo APT repo finally fixed Message-ID: ? ? ? ? Content-Type: text/plain; charset="utf-8"; Format="flowed" I also used the new repo instructions, and it worked fine. Looks like you might have an old repo for zendto. Check in /etc/apt/sources.list.d, and maybe grep for "lynx"? If you installed the new repo's deb package, the contents of /etc/apt/sources.list.d/zendto.list will be just a single line: deb [signed-by=/usr/share/keyrings/zendto.gpg.asc]https://zend.to/apt stable main ~Keith On 4/24/25 1:01 PM, Jason Passow via ZendTo wrote: > I used the new repo instructions and receive the following errors: > > Err:11 https://zend.to/apt lynx Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:12 https://zend.to/apt trusty Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:13 https://zend.to/apt xenial Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Err:14 https://zend.to/apt bionic Release > ? 404 ?Not Found [IP: 46.22.137.105 443] > Reading package lists... Done > E: The repository 'http://zend.to/apt lynx Release' does not have a > Release file ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? . > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt trusty Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt xenial Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > E: The repository 'http://zend.to/apt bionic Release' does not have a > Release fi ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? le. > N: Updating from such a repository can't be done securely, and is > therefore disa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration deta ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ils. > > > This is on a 24.04 ubuntu server. > > *Jason Passow* | Network Administrator > > o: (507) 494-5178 |?c: (507) 450-8178 | jasonp at mwsco.com > 5150 West 6^th Street, Winona, MN?55987 > www.mwsco.com > > > MWS Logo > VOSB Logo > > > > > _______________________________________________ > ZendTo mailing list > ZendTo at zend.to > http://jul.es/mailman/listinfo/zendto -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ ZendTo mailing list ZendTo at zend.to http://jul.es/mailman/listinfo/zendto ------------------------------ End of ZendTo Digest, Vol 163, Issue 5 ************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From orion at nwra.com Fri Apr 25 22:38:08 2025 From: orion at nwra.com (Orion Poplawski) Date: Fri, 25 Apr 2025 15:38:08 -0600 Subject: [ZendTo] DestName limit References: <333d8002-7601-4825-b8f9-b7a25896dc22@nwra.com> Message-ID: One of our users hit a request error sending a dropoff. The only user visible error was "Sending a request to these addresses failed: ...." However the log showed: Error: Failed to add 661518051 to reqtable for greg at nwra.com. Error was Data too long for column 'DestName' at row 1 Looks like the original name was 35 characters due to various suffixes like "(Short Name) CTR (USA)" which is longer than the 32 characters currently allowed: > show columns from reqtable; +------------+---------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +------------+---------------+------+-----+---------+-------+ | Auth | varchar(64) | NO | PRI | NULL | | | SrcName | varchar(32) | YES | | NULL | | | SrcEmail | text | NO | | NULL | | | SrcOrg | varchar(256) | NO | | NULL | | | DestName | varchar(32) | YES | | NULL | | | DestEmail | text | NO | | NULL | | | Note | text | NO | | NULL | | | Subject | text | NO | | NULL | | | Expiry | bigint(20) | NO | | NULL | | | Passphrase | varchar(1024) | NO | | | | | Start | bigint(20) | NO | | 0 | | | Created | bigint(20) | NO | | 0 | | +------------+---------------+------+-----+---------+-------+ So, two requests: * Might be good to bump that limit * Can we get better error messages reported back to the user in these cases? Thanks again for the very useful software, Orion -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772-5637 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 https://www.nwra.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4087 bytes Desc: S/MIME Cryptographic Signature URL: From ricky.boone at gmail.com Fri Apr 25 23:40:59 2025 From: ricky.boone at gmail.com (Ricky Boone) Date: Fri, 25 Apr 2025 18:40:59 -0400 Subject: [ZendTo] Protip: Server Migrations and Remote Databases, Orphan Dropoff Cleanup References: Message-ID: I'm writing this while restoring [most] of the dropoffs affected by this, but wanted to at least get it out there in case anyone else attempts to do something like this (or has to clean up someone else's mess). If your ZendTo environment uses a remote database, and you want to migrate to another server, don't point the new server to the same remote database. Or, if you do, make sure the cron jobs don't run. Assuming you aren't using a synchronized file system between the old and new servers for dropoffs, you'll have one system finding a boatload of orphaned dropoffs that don't exist on the filesystem that it will want to wipe out of the database, then the other system will have a boatload of missing dropoffs that it will want to clean up from the filesystem that were just wiped by the other system. It will ignore dropoffs that are newer than 24 hours old... but that means the longer it's left in this state, more gets wiped. What fun! Also: make sure you have frequent backups, and verify them... frequently.