http://www.lsoft.com/images/listserv_64x64.pnghttp://www.lsoft.com/images/listserv_64x64.pngLSTSRV-L ListLSTSRV-L List Archiveshttp://community.emailogy.com/scripts/wa-community.exe?RSS&L=LSTSRV-L&v=ATOM1.0
This is an Atom-formatted XML feed. It is intended to be viewed in a newsreader. Alternatively, you can view the web archives at: http://community.emailogy.com/scripts/wa-community.exe?A0=LSTSRV-L.
LISTSERV 17.02024-03-29T14:35:39ZShinn Wu2023-03-09T19:25:52+00:002023-03-09T19:25:52+00:00Re: Block key words?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;5e0c28f6.2303Thank you so much, it worked! Nathan Brindle2023-03-09T18:20:09+00:002023-03-09T18:20:09+00:00Re: Block key words?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a8abcf4.2303See the CONTENT_FILTER template described in the LISTSERV documentation. Probably will help.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Shinn Wu<br>Sent: Thursday, March 09, 2023 1:11 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: Block key words?<br><br>Hi William,<br><br>Thank you for replying to my question.<br><br>We hosted more than 600 lists and they are highly diversified. Four lists have more than 5,000 subscribers. Our main mail server is behind a spam firewall, but not the Listserv. Implement a SPF hard fail might block some legitimate posters where their mail server did not have any SPF in their DNS.<br><br>Best,<br><br>Shinn Shinn Wu2023-03-09T18:10:51+00:002023-03-09T18:10:51+00:00Re: Block key words?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2f38786.2303Hi William,<br><br>Thank you for replying to my question.<br><br>We hosted more than 600 lists and they are highly diversified. Four lists have more than 5,000 subscribers. Our main mail server is behind a spam firewall, but not the Listserv. Implement a SPF hard fail might block some legitimate posters where their mail server did not have any SPF in their DNS.<br><br>Best,<br><br>Shinn Brown, William2023-03-09T16:28:45+00:002023-03-09T16:28:45+00:00Re: Block key words?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;52ffd36e.2303We have run Listserv (Windows) behind a spam filter for many years. We receive notifications of all spam to the lists which has not be bad. We have approximately 50 lists with max several hundred subscribers and only one or two get much spam. Our lists are closed with subscriber approval which may help too.<br><br>If nothing else, have the spam filters check SPF to prevent spoofing and skip any rules based detection. Shinn Wu2023-03-09T16:08:15+00:002023-03-09T16:08:15+00:00Block key words?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;51eba408.2303Hello,<br><br>We use Listserv 17.0 in RedHat. We had three incidents of 'phantom approval' this year and I had to ask the not aware editors to change the webmail settings.<br><br>I tried to use procmailrc to block the keywords. It worked on the regular account on the same server but not the listserv account. I thought that it might be aliases take precedence of procmailrc. We do not want to use a spam filter because it would cause some false-positive. Any insight suggestion to block some keywords (e.g., bitcoin, BTC wallet, and BTC address) from incoming post request?<br><br>Thank you,<br><br>Shinn Krista2023-02-22T11:41:59-05:002023-02-22T11:41:59-05:00Re: [EXTERNAL] Wrong name on message to new subscriber, but correct email.http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;31df4f8c.2302The owner wasn't subscribed.<br>I checked the subscription of the name that was inserted and their<br>email address was correct.<br>I told the owner they weren't subscribed and they went ahead and subscribed<br>themselves, and that fixed the issue. I'm not sure why, but it looked like<br>it was pulling a name to fill in the blank, from the subscribers list,<br>because the Owner didn't have a name set.<br><br>Krista Landon<br><br>On Wed, Feb 22, 2023 at 11:21 AM King, Margaret <makmaint@msu.edu> wrote:<br><br>> My guess is that the first time this owner tried to add this subscriber to<br>> the list, he or she absentmindedly typed Subscribe instead of Add. This<br>> could change the owner’s own name entry. It happens from time to time here.<br>> They should use the Register command to fix their own name.<br>><br>><br>><br>> Margaret King<br>><br>> Michigan State University<br>><br>><br>><br>> *From:* LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM><br>> *On Behalf Of *Krista<br>> *Sent:* Wednesday, February 22, 2023 11:14 AM<br>> *To:* LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> *Subject:* [EXTERNAL] Wrong name on message to new subscriber, but<br>> correct email.<br>><br>><br>><br>> A list owner reported that the emails that are going out to subscribers,<br>> once they have been added (manually) are showing the correct email address<br>> of the owner but the wrong name for that owner.<br>><br>><br>><br>> Example:<br>> You have been added to the TEST mailing list (Name of list) by WRONG<br>> NAME <correctemail@domain.com>.<br>><br>> The owner is not subscribed to their own list, I noticed. The person whose<br>> name is being inserted is, but has the appropriate email address, for them.<br>><br>><br>><br>> Any idea how this could be happening?<br>><br>><br>><br>> Krista Landon<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>> <https://urldefense.com/v3/__http:/peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1__;!!HXCxUKc!3gzFZrGlNlfqecItbG9ky3zCT5ILPVgaqZqrRJMqYoUwFUIMDLKZg0JTlwSKbWwy37iOrUkbCQtj36k$><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>King, Margaret2023-02-22T16:21:47+00:002023-02-22T16:21:47+00:00Re: [EXTERNAL] Wrong name on message to new subscriber, but correct email.http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a0eb8389.2302My guess is that the first time this owner tried to add this subscriber to the list, he or she absentmindedly typed Subscribe instead of Add. This could change the owner’s own name entry. It happens from time to time here. They should use the Register command to fix their own name.<br><br>Margaret King<br>Michigan State University<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Krista<br>Sent: Wednesday, February 22, 2023 11:14 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: [EXTERNAL] Wrong name on message to new subscriber, but correct email.<br><br>A list owner reported that the emails that are going out to subscribers, once they have been added (manually) are showing the correct email address of the owner but the wrong name for that owner.<br><br>Example:<br>You have been added to the TEST mailing list (Name of list) by WRONG NAME <correctemail@domain.com<mailto:correctemail@domain.com>>.<br><br>The owner is not subscribed to their own list, I noticed. The person whose name is being inserted is, but has the appropriate email address, for them.<br><br>Any idea how this could be happening?<br><br>Krista LandonKrista2023-02-22T11:13:49-05:002023-02-22T11:13:49-05:00Wrong name on message to new subscriber, but correct email.http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a7f98eb4.2302A list owner reported that the emails that are going out to subscribers,<br>once they have been added (manually) are showing the correct email address<br>of the owner but the wrong name for that owner.<br><br>Example:<br>You have been added to the TEST mailing list (Name of list) by WRONG<br>NAME <correctemail@domain.com>.<br><br>The owner is not subscribed to their own list, I noticed. The person whose<br>name is being inserted is, but has the appropriate email address, for them.<br><br>Any idea how this could be happening?<br><br>Krista LandonKrista2023-01-30T16:30:16-05:002023-01-30T16:30:16-05:00Re: Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;3677598f.2301Thank you! I think the short term fix will be to set Digest= No on the<br>configuration (I assume that'll work for current subscribers who have their<br>preference set to digest too) and then consider the other options for<br>future.<br><br>Krista<br><br>On Mon, Jan 30, 2023 at 4:25 PM Jacob Haller <jacob.haller@gmail.com> wrote:<br><br>> On Jan 30, 2023, at 4:11 PM, Krista <klandon@GMAIL.COM> wrote:<br>><br>> Ah, I see. These messages are being generated by a Drupal site and sent to<br>> the ListServ so I suspect it's not creating plaintext versions.<br>><br>> Is it possible to turn off the digest option for a ListServ / convert all<br>> existing subscribers to "Regular"?<br>> Or is it perhaps possible to make the digest go out HTML email synopsis?<br>><br>><br>> You can set ‘Digest= No’ in a mailing list’s configuration, which will<br>> cause all subscribers to get messages at the time they are sent out, rather<br>> than as a digest.<br>><br>> You can also make the default digest type be either HTML or MIME via<br>><br>> Default-Options= HTML<br>><br>><br>> or<br>><br>> Default-Options= MIME<br>><br>><br>> but HTML digests are not supported by some common email programs and<br>> services (web-based services in particular often break the links to<br>> individual messages), and the gmail web portal has a bug that prevents it<br>> from displaying MIME digests correctly.<br>><br>> If you do change the default digest type, then that will only affect<br>> future subscribers of the mailing list. To apply it to current subscribers,<br>> you’d issue e.g. a<br>><br>> QUIET SET nameoflist MIME FOR *@*<br>><br>><br>> command under ‘List Management’/‘LISTSERV Command’, replacing ‘nameoflist’<br>> with the name of the mailing list.<br>><br>> -jwgh<br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Jacob Haller2023-01-30T16:25:27-05:002023-01-30T16:25:27-05:00Re: Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;17086bee.2301On Jan 30, 2023, at 4:11 PM, Krista <klandon@GMAIL.COM> wrote:<br><br>> Ah, I see. These messages are being generated by a Drupal site and sent to the ListServ so I suspect it's not creating plaintext versions.<br>><br>> Is it possible to turn off the digest option for a ListServ / convert all existing subscribers to "Regular"?<br>> Or is it perhaps possible to make the digest go out HTML email synopsis?<br><br>You can set ‘Digest= No’ in a mailing list’s configuration, which will cause all subscribers to get messages at the time they are sent out, rather than as a digest.<br><br>You can also make the default digest type be either HTML or MIME via<br><br>Default-Options= HTML<br><br>or<br><br>Default-Options= MIME<br><br>but HTML digests are not supported by some common email programs and services (web-based services in particular often break the links to individual messages), and the gmail web portal has a bug that prevents it from displaying MIME digests correctly.<br><br>If you do change the default digest type, then that will only affect future subscribers of the mailing list. To apply it to current subscribers, you’d issue e.g. a<br><br>QUIET SET nameoflist MIME FOR *@*<br><br>command under ‘List Management’/‘LISTSERV Command’, replacing ‘nameoflist’ with the name of the mailing list.<br><br>-jwghKrista2023-01-30T16:11:38-05:002023-01-30T16:11:38-05:00Re: Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a9b3691.2301Ah, I see. These messages are being generated by a Drupal site and sent to<br>the ListServ so I suspect it's not creating plaintext versions.<br><br>Is it possible to turn off the digest option for a ListServ / convert all<br>existing subscribers to "Regular"?<br>Or is it perhaps possible to make the digest go out HTML email synopsis?<br><br>Krista<br><br>On Mon, Jan 30, 2023 at 4:09 PM Jacob Haller <jacob.haller@gmail.com> wrote:<br><br>> > What would cause this error in a Digest message but not in the an<br>> individual post to a List?<br>> ><br>> > [Message contains invalid MIME fields or encoding and could not be<br>> processed]<br>> ><br>> > Krista Landon<br>><br>> Basically, when LISTSERV puts together a plaintext digest, it discards<br>> everything in the message that isn’t plaintext. If, at the end of that,<br>> there’s nothing left, then you get this error. (The error might also show<br>> up in other circumstances, if some other error occurs while LISTSERV is<br>> attempting to parse the message to put it in the digest.)<br>><br>> My guess is that the message in question was either an HTML message that<br>> did not include a plaintext version of the message, or was a message that<br>> just consisted of an attached document. Most email programs automatically<br>> generate and include a plaintext version of an HTML message, and contain at<br>> least a blank plaintext part of messages containing attachments, so this<br>> sort of error is rare.<br>><br>> The default wording of the message doesn’t specifically address that<br>> scenario, but if you want, you can customize it under ‘List<br>> Management’/‘Mail Templates’ (to customize it for a specific mailing list)<br>> or ’Server Administration’/‘Mail Templates’ (to customize the default<br>> site-wide version). The template’s name is MSG_DIGEST_FRAGMENT_MIME_ERROR.<br>><br>> Thanks,<br>> jwgh<br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Jacob Haller2023-01-30T16:08:44-05:002023-01-30T16:08:44-05:00Re: Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2d90280a.2301> What would cause this error in a Digest message but not in the an individual post to a List?<br>><br>> [Message contains invalid MIME fields or encoding and could not be processed]<br>><br>> Krista Landon<br><br>Basically, when LISTSERV puts together a plaintext digest, it discards everything in the message that isn’t plaintext. If, at the end of that, there’s nothing left, then you get this error. (The error might also show up in other circumstances, if some other error occurs while LISTSERV is attempting to parse the message to put it in the digest.)<br><br>My guess is that the message in question was either an HTML message that did not include a plaintext version of the message, or was a message that just consisted of an attached document. Most email programs automatically generate and include a plaintext version of an HTML message, and contain at least a blank plaintext part of messages containing attachments, so this sort of error is rare.<br><br>The default wording of the message doesn’t specifically address that scenario, but if you want, you can customize it under ‘List Management’/‘Mail Templates’ (to customize it for a specific mailing list) or ’Server Administration’/‘Mail Templates’ (to customize the default site-wide version). The template’s name is MSG_DIGEST_FRAGMENT_MIME_ERROR.<br><br>Thanks,<br>jwghStan Horwitz2023-01-30T20:01:17+00:002023-01-30T20:01:17+00:00Re: [External] Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;b2221620.2301Please open a tuhelp request with your question. The tuhelp website is tuhelp.temple.edu<br><br>On Jan 30, 2023, at 14:59, Krista <klandon@GMAIL.COM> wrote:<br><br>What would cause this error in a Digest message but not in the an individual post to a List?<br><br>[Message contains invalid MIME fields or encoding and could not be processed]<br><br>Krista Landon Krista2023-01-30T14:59:15-05:002023-01-30T14:59:15-05:00Error help - [Message contains invalid MIME fields or encoding and could not be processed]http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;7143f872.2301What would cause this error in a Digest message but not in the an<br>individual post to a List?<br><br>[Message contains invalid MIME fields or encoding and could not be<br>processed]<br><br>Krista LandonBarthofer Michael2022-11-30T10:12:21+00:002022-11-30T10:12:21+00:00Translation for the email-subject "Command confirmation request "http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;b65d9de6.2211Dear all<br><br>I am currently translating crucial web-templates and mail-templates to german. Unfortunately I cannot find a way to translate the subject "Command confirmation request" which is the very first mail a prospective subscriber gets. I identified the mail-template "CONFIRM1" as the relevant template and changed the subject with the online-template-editor to german. I did this for a specific list and also in the same mail-template in the server administration, but the subject of the confirmation-mail still stays "Command confirmation request".<br><br>Has anyone experience with translation of Listserv?<br>We have the version 17.0<br><br>Best regards<br><br>Michael<br><br>[Linz_Logo]<br><br>Diese Nachricht inklusive aller Anh?nge kann vertrauliche Informationen enthalten. Falls diese Mail nicht richtig adressiert ist, bitten wir Sie, den/die Absender/in zu informieren und die Nachricht zu l?schen.<br><br>Kundmachung - Kommunikation mit dem Magistrat Linz (AVG, BAO) (PDF, 192 KB)<https://www.linz.at/images/files/Kundmachung_AVG_BAO.pdf> Mark Kaprow2022-10-25T23:19:28-04:002022-10-25T23:19:28-04:00Re: [EXTERNAL] list xy has no archives after file restore, but files existhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;dd463918.2211You have to create the WWW archive directory and then re-put (save) the<br>list again. I am not talking about the notebook directory containing the<br>listserv message log, but the one that displays on the Web. You just have<br>to create the directory name, and then resave the list header, making some<br>slight change, add a quiet owner or something, you can always undo that<br>change the following day.<br><br>On Tue, Oct 25, 2022 at 9:45 AM Skowronek, Markus <<br>Markus.Skowronek@urz.uni-heidelberg.de> wrote:<br><br>> Thank you for your responses,<br>><br>><br>><br>> reindexing did not help, producing the same error in first place.<br>><br>><br>><br>> Resaving the list header did help (immediately), and reindexing afterwards<br>> works again as expected.<br>><br>><br>><br>> I tried to reproduce the issue using some test-lists and found the same<br>> issues and solutions again.<br>><br>><br>><br>> I did hope the following restore order would also work (assuming *ABC* is<br>> the list,<br>><br>> /home/listserv/*notebook*/*abc* is the folder of notebook files, etc …):<br>><br>> 1. *restorecmd* /home/listserv/*notebook*/*abc*/*<br>><br>> 2. *restorecmd* /var/www/html/archives/*abc*/*<br>><br>> 3. *restorecmd* /home/listserv/home/*abc*.*<br>><br>> resulting in *abc*.list as (nearly) last restored file.<br>><br>> However, resaving the list-config afterwards still is required.<br>><br>><br>><br>> Maybe in an earlier listserv-version (16.x and earlier) restore-only was<br>> sufficient..?<br>><br>><br>><br>> Best regards<br>><br>> Markus<br>><br>><br>><br>><br>><br>> *Von:* LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM><br>> *Im Auftrag von *Jacob Haller<br>> *Gesendet:* Dienstag, 25. Oktober 2022 04:15<br>> *An:* LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> *Betreff:* Re: [EXTERNAL] list xy has no archives after file restore, but<br>> files exist<br>><br>><br>><br>> On Oct 24, 2022, at 2:36 PM, King, Margaret <makmaint@MSU.EDU> wrote:<br>><br>><br>><br>> It may need to reindex them.<br>><br>><br>><br>> There is some command to do this but I am not sure I have ever used it,<br>> because re-saving the list header generally does it as a side effect, at<br>> least on the version we have here. I.e., going into Manual Configuration<br>> and hitting Save. In my experience you do not have to actually change<br>> anything.<br>><br>><br>><br>> Margaret King<br>><br>> Michigan State University<br>><br>><br>><br>> The command’s<br>><br>><br>><br>> *reindex both nameoflist*<br>><br>><br>><br>> (replacing ’nameoflist’ with the name of the mailing list) and it can be<br>> issued under ‘List Management’/‘LISTSERV Command’. (Updating the list’s<br>> configuration, or just clicking on ’Save’ on the list configuration page,<br>> will do the same thing, as you say.)<br>><br>><br>><br>> If that doesn’t do the trick, then I would go under ’Server<br>> Administration’ to ’Site Configuration’ and look to see where<br>> WWW_ARCHIVE_DIR points to. In this location, create a subdirectory that has<br>> the same name as the mailing list. (If this is on a LISTSERV for Unix<br>> server, then make sure the directory’s name is all lower case.) Then<br>> restart LISTSERV and see if the archives are now accessible.<br>><br>><br>><br>> This is a different location from the one given in the ’Notebook=‘<br>> setting. The notebook directory contains the actual copies of the messages,<br>> while the WWW_ARCHIVE_DIR subdirectory contains files related to the web<br>> interface to the archives. Some additional information can be found at<br>> https://www.lsoft.com/manuals/16.0/htmlhelp/site%20managers/ConfiguringLSSite.html#2342978<br>> .<br>><br>><br>><br>> -jwgh<br>><br>><br>><br>><br>><br>> *From:* LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> > *On Behalf Of *Skowronek, Markus<br>> *Sent:* Monday, October 24, 2022 11:20 AM<br>> *To:* LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> *Subject:* [EXTERNAL] list xy has no archives after file restore, but<br>> files exist<br>><br>><br>><br>> Dear all,<br>><br>><br>><br>> after accidentially deleting the wrong list via web-interface, i could<br>><br>> restore the corresponding files successfully from our backup server<br>><br>><br>><br>> however listserv claims „the XYZ list has no archives“, while config<br>> clearly says it has „Notebook=yes,/home/listserv/…“<br>><br>> and folder and files have been restored<br>><br>><br>><br>> i’m quite sure (?) it has to do with the order the files and folders need<br>> to be restored …?<br>><br>><br>><br>><br>><br>><br>><br>> Best regards<br>><br>> Markus<br>><br>><br>><br>> --<br>><br>> Markus Skowronek<br>><br>> Servicebereich Core Technologies & Collaboration Services (CTCS)<br>><br>><br>><br>> Tel. +49 6221 54 20089, Fax +49 6221 54 5581<br>><br>> Markus.Skowronek@urz.uni-heidelberg.de<br>><br>><br>><br>> Universität Heidelberg<br>><br>> Universitätsrechenzentrum (URZ)<br>><br>> Im Neuenheimer Feld 330, D-69120 Heidelberg<br>><br>> http://www.urz.uni-heidelberg.de/<br>> <https://urldefense.com/v3/__http:/www.urz.uni-heidelberg.de/__;!!HXCxUKc!2i4ePvCcemwDUraag1RkDnQRl-aOuX8luA-ScoaDmAzA3_rbi5z3L7yVt2pCEdjE7nshXDNDLqoZ8cSkgwtohAT1_JiPNkGlA-lncv8$><br>><br>><br>><br>><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>> <https://urldefense.com/v3/__http:/peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1__;!!HXCxUKc!2i4ePvCcemwDUraag1RkDnQRl-aOuX8luA-ScoaDmAzA3_rbi5z3L7yVt2pCEdjE7nshXDNDLqoZ8cSkgwtohAT1_JiPNkGlpRLK4zQ$><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Skowronek, Markus2022-10-25T13:43:53+00:002022-10-25T13:43:53+00:00AW: [EXTERNAL] list xy has no archives after file restore, but files existhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;13c095ce.2211Thank you for your responses,<br><br>reindexing did not help, producing the same error in first place.<br><br>Resaving the list header did help (immediately), and reindexing afterwards works again as expected.<br><br>I tried to reproduce the issue using some test-lists and found the same issues and solutions again.<br><br>I did hope the following restore order would also work (assuming ABC is the list,<br>/home/listserv/notebook/abc is the folder of notebook files, etc …):<br><br>1. restorecmd /home/listserv/notebook/abc/*<br><br>2. restorecmd /var/www/html/archives/abc/*<br><br>3. restorecmd /home/listserv/home/abc.*<br>resulting in abc.list as (nearly) last restored file.<br>However, resaving the list-config afterwards still is required.<br><br>Maybe in an earlier listserv-version (16.x and earlier) restore-only was sufficient..?<br><br>Best regards<br>Markus<br><br>Von: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> Im Auftrag von Jacob Haller<br>Gesendet: Dienstag, 25. Oktober 2022 04:15<br>An: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Betreff: Re: [EXTERNAL] list xy has no archives after file restore, but files exist<br><br>On Oct 24, 2022, at 2:36 PM, King, Margaret <makmaint@MSU.EDU<mailto:makmaint@MSU.EDU>> wrote:<br><br>It may need to reindex them.<br><br>There is some command to do this but I am not sure I have ever used it, because re-saving the list header generally does it as a side effect, at least on the version we have here. I.e., going into Manual Configuration and hitting Save. In my experience you do not have to actually change anything.<br><br>Margaret King<br>Michigan State University<br><br>The command’s<br><br>reindex both nameoflist<br><br>(replacing ’nameoflist’ with the name of the mailing list) and it can be issued under ‘List Management’/‘LISTSERV Command’. (Updating the list’s configuration, or just clicking on ’Save’ on the list configuration page, will do the same thing, as you say.)<br><br>If that doesn’t do the trick, then I would go under ’Server Administration’ to ’Site Configuration’ and look to see where WWW_ARCHIVE_DIR points to. In this location, create a subdirectory that has the same name as the mailing list. (If this is on a LISTSERV for Unix server, then make sure the directory’s name is all lower case.) Then restart LISTSERV and see if the archives are now accessible. [...]Jacob Haller2022-10-24T22:14:58-04:002022-10-24T22:14:58-04:00Re: [EXTERNAL] list xy has no archives after file restore, but files existhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;f9cb720e.2211On Oct 24, 2022, at 2:36 PM, King, Margaret <makmaint@MSU.EDU> wrote:<br><br>> It may need to reindex them.<br>><br>> There is some command to do this but I am not sure I have ever used it, because re-saving the list header generally does it as a side effect, at least on the version we have here. I.e., going into Manual Configuration and hitting Save. In my experience you do not have to actually change anything.<br>><br>> Margaret King<br>> Michigan State University<br><br>The command’s<br><br>reindex both nameoflist<br><br>(replacing ’nameoflist’ with the name of the mailing list) and it can be issued under ‘List Management’/‘LISTSERV Command’. (Updating the list’s configuration, or just clicking on ’Save’ on the list configuration page, will do the same thing, as you say.)<br><br>If that doesn’t do the trick, then I would go under ’Server Administration’ to ’Site Configuration’ and look to see where WWW_ARCHIVE_DIR points to. In this location, create a subdirectory that has the same name as the mailing list. (If this is on a LISTSERV for Unix server, then make sure the directory’s name is all lower case.) Then restart LISTSERV and see if the archives are now accessible.<br><br>This is a different location from the one given in the ’Notebook=‘ setting. The notebook directory contains the actual copies of the messages, while the WWW_ARCHIVE_DIR subdirectory contains files related to the web interface to the archives. Some additional information can be found at https://www.lsoft.com/manuals/16.0/htmlhelp/site%20managers/ConfiguringLSSite.html#2342978 <https://www.lsoft.com/manuals/16.0/htmlhelp/site%20managers/ConfiguringLSSite.html#2342978> .<br><br>-jwgh<br><br>><br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Skowronek, Markus<br>> Sent: Monday, October 24, 2022 11:20 AM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: [EXTERNAL] list xy has no archives after file restore, but files exist<br>><br>> Dear all,<br>><br>> after accidentially deleting the wrong list via web-interface, i could<br>> restore the corresponding files successfully from our backup server<br>><br>> however listserv claims „the XYZ list has no archives“, while config clearly says it has „Notebook=yes,/home/listserv/…“<br>> and folder and files have been restored<br>><br>> i’m quite sure (?) it has to do with the order the files and folders need to be restored …?<br>><br>><br>><br>> Best regards<br>> Markus<br>><br>> --<br>> Markus Skowronek<br>> Servicebereich Core Technologies & Collaboration Services (CTCS)<br>><br>> Tel. +49 6221 54 20089, Fax +49 6221 54 5581<br>> Markus.Skowronek@urz.uni-heidelberg.de <mailto:Markus.Skowronek@urz.uni-heidelberg.de><br>><br>> Universität Heidelberg<br>> Universitätsrechenzentrum (URZ)<br>> Im Neuenheimer Feld 330, D-69120 Heidelberg<br>> http://www.urz.uni-heidelberg.de/ <https://urldefense.com/v3/__http:/www.urz.uni-heidelberg.de/__;!!HXCxUKc!2i4ePvCcemwDUraag1RkDnQRl-aOuX8luA-ScoaDmAzA3_rbi5z3L7yVt2pCEdjE7nshXDNDLqoZ8cSkgwtohAT1_JiPNkGlA-lncv8$><br>><br>><br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1 <https://urldefense.com/v3/__http:/peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1__;!!HXCxUKc!2i4ePvCcemwDUraag1RkDnQRl-aOuX8luA-ScoaDmAzA3_rbi5z3L7yVt2pCEdjE7nshXDNDLqoZ8cSkgwtohAT1_JiPNkGlpRLK4zQ$><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1 <http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1>King, Margaret2022-10-24T18:36:33+00:002022-10-24T18:36:33+00:00Re: [EXTERNAL] list xy has no archives after file restore, but files existhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c0549a01.2211It may need to reindex them.<br><br>There is some command to do this but I am not sure I have ever used it, because re-saving the list header generally does it as a side effect, at least on the version we have here. I.e., going into Manual Configuration and hitting Save. In my experience you do not have to actually change anything.<br><br>Margaret King<br>Michigan State University<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Skowronek, Markus<br>Sent: Monday, October 24, 2022 11:20 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: [EXTERNAL] list xy has no archives after file restore, but files exist<br><br>Dear all,<br><br>after accidentially deleting the wrong list via web-interface, i could<br>restore the corresponding files successfully from our backup server<br><br>however listserv claims "the XYZ list has no archives", while config clearly says it has "Notebook=yes,/home/listserv/..."<br>and folder and files have been restored<br><br>i'm quite sure (?) it has to do with the order the files and folders need to be restored ...?<br><br>Best regards<br>Markus Skowronek, Markus2022-10-24T15:20:10+00:002022-10-24T15:20:10+00:00list xy has no archives after file restore, but files existhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c42ca2d1.2211Dear all,<br><br>after accidentially deleting the wrong list via web-interface, i could<br>restore the corresponding files successfully from our backup server<br><br>however listserv claims "the XYZ list has no archives", while config clearly says it has "Notebook=yes,/home/listserv/..."<br>and folder and files have been restored<br><br>i'm quite sure (?) it has to do with the order the files and folders need to be restored ...?<br><br>Best regards<br>Markus Steven J Depinet2022-10-13T16:04:35+00:002022-10-13T16:04:35+00:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;549d73e4.2210Great!<br><br>Thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Oct 13, 2022, at 8:55 AM, Jacob Haller <jacob.haller@GMAIL.COM> wrote:<br>><br>><br>><br>> On Oct 13, 2022, at 11:45 AM, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>>> As I mentioned, this looks very promising if we should decide to pursue it, but I’m a bit confused about the definition of the DEL_FILTER entry point.<br>>><br>>> The Advanced Topics Manual for LISTSERV 17.0, Section 4.2 List Exit Points, sub para 4.2.2 DELETE/SIGNOFF/CHANGE Entry Points, under Name: DEL_FILTER says: "Description: This exit point is called for all SIGNOFF commands, and for DELETE commands issued by a registered Node Administrator. It is NOT called for DELETE commands originating from the list owner”.<br>>><br>>> When a user tries to unsubscribe, does that use the SIGNOFF command? I’ve looked in the User (sorry, List Subscribers) Manual and List Admin (List Owner’s) Manual, and don’t see the email command for a user to unsubscribe themself from a list. I’ve always used delete, but that’s as an admin, I can’t say that I’ve used email to unsubscribe myself from a list...<br>><br>> Yes, SIGNOFF (or its synonym UNSUBSCRIBE) is the command to leave a mailing list. See https://www.lsoft.com/manuals/17.0/commands/11Listsubscriptioncommands.html for information about this and other subscription-related commands available to users.<br>><br>>> Presumable, the Web Interface would use the same code, just generate the same params as the mail interface uses, so that would also use SIGNOFF, rather than DELETE?<br>><br>> Right. If a user leaves a list, wa.exe communicates this to LISTSERV by sending a SIGNOFF command.<br>><br>> Thanks,<br>> jwgh<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Jacob Haller2022-10-13T11:55:28-04:002022-10-13T11:55:28-04:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;f3061f3a.2210On Oct 13, 2022, at 11:45 AM, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br><br>> As I mentioned, this looks very promising if we should decide to pursue it, but I’m a bit confused about the definition of the DEL_FILTER entry point.<br>><br>> The Advanced Topics Manual for LISTSERV 17.0, Section 4.2 List Exit Points, sub para 4.2.2 DELETE/SIGNOFF/CHANGE Entry Points, under Name: DEL_FILTER says: "Description: This exit point is called for all SIGNOFF commands, and for DELETE commands issued by a registered Node Administrator. It is NOT called for DELETE commands originating from the list owner”.<br>><br>> When a user tries to unsubscribe, does that use the SIGNOFF command? I’ve looked in the User (sorry, List Subscribers) Manual and List Admin (List Owner’s) Manual, and don’t see the email command for a user to unsubscribe themself from a list. I’ve always used delete, but that’s as an admin, I can’t say that I’ve used email to unsubscribe myself from a list...<br><br>Yes, SIGNOFF (or its synonym UNSUBSCRIBE) is the command to leave a mailing list. See https://www.lsoft.com/manuals/17.0/commands/11Listsubscriptioncommands.html <https://www.lsoft.com/manuals/17.0/commands/11Listsubscriptioncommands.html> for information about this and other subscription-related commands available to users.<br><br>> Presumable, the Web Interface would use the same code, just generate the same params as the mail interface uses, so that would also use SIGNOFF, rather than DELETE?<br><br>Right. If a user leaves a list, wa.exe communicates this to LISTSERV by sending a SIGNOFF command.<br><br>Thanks,<br>jwghSteven J Depinet2022-10-13T15:45:02+00:002022-10-13T15:45:02+00:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;ea04902e.2210As I mentioned, this looks very promising if we should decide to pursue it, but I’m a bit confused about the definition of the DEL_FILTER entry point.<br><br>The Advanced Topics Manual for LISTSERV 17.0, Section 4.2 List Exit Points, sub para 4.2.2 DELETE/SIGNOFF/CHANGE Entry Points, under Name: DEL_FILTER says: "Description: This exit point is called for all SIGNOFF commands, and for DELETE commands issued by a registered Node Administrator. It is NOT called for DELETE commands originating from the list owner”.<br><br>When a user tries to unsubscribe, does that use the SIGNOFF command? I’ve looked in the User (sorry, List Subscribers) Manual and List Admin (List Owner’s) Manual, and don’t see the email command for a user to unsubscribe themself from a list. I’ve always used delete, but that’s as an admin, I can’t say that I’ve used email to unsubscribe myself from a list...<br><br>Presumable, the Web Interface would use the same code, just generate the same params as the mail interface uses, so that would also use SIGNOFF, rather than DELETE?<br><br>TIA,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Oct 12, 2022, at 12:29 PM, Kenny, Melissa S. <Melissa_Kenny@HMS.HARVARD.EDU> wrote:<br>><br>> Hi,<br>><br>> Here, we use the "EXIT" keyword, which specifies an external command to run, in lists we don't want users to unsubscribe from. These are all administrative lists and are used only for important messages we want to be sure that faculty, staff, and/or students get all of these messages. In our case, we use a PERL script that we got from a former frequent poster to this list who has since retired.<br>><br>> Melissa Kenny<br>><br>> Web Administrator<br>> Harvard Medical School IT<br>><br>> 401 Park Drive<br>> Suite 504 West<br>> Boston, MA 02215<br>><br>><br>><br>><br>> -----Original Message-----<br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Groot, Joost de (UT-LISA)<br>> Sent: Monday, October 10, 2022 3:55 AM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: [LSTSRV-L] FW: Subcription= keyword<br>><br>> Hi Steve,<br>><br>> The easiest way I have found to block users from unsubscribing is to issue a "get <listname> (Header" command in the command box. This will lock the list and nobody is able to make changes anymore. So subscribers can't unsubscribe themselves anymore. This also blocks listowners from making changes, so choose the right time to lock the list. When a user sends an unsubscribe mail to the list they will receive this message:<br>><br>> "Sorry, the <listname> list has been locked since 2022-10-10 09:01:45 by <email listowner>. Try again later and contact the list owner if the condition persists."<br>><br>> To unlock the list you have to send "unlock <listname>" in the command box.<br>><br>> Hope this helps,<br>><br>> Kind regards,<br>><br>> Joost de Groot<br>><br>> -----Original Message-----<br>> From: Steven J Depinet <Steve.dePinet@NAU.EDU><br>> Sent: vrijdag 7 oktober 2022 17:30<br>> Subject: Subcription= keyword<br>><br>> Greetings All,<br>><br>> I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br>><br>> Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br>><br>> Thanks,<br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Steven J Depinet2022-10-12T19:53:49+00:002022-10-12T19:53:49+00:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a689a26a.2210Melissa,<br><br>Thanks for sharing that. After reading up on the Exit keyword, it seems to be something that’s possible, and my Management might be interested in having implemented. Which, of course, means work for me...<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Oct 12, 2022, at 12:29 PM, Kenny, Melissa S. <Melissa_Kenny@HMS.HARVARD.EDU> wrote:<br>><br>> Hi,<br>><br>> Here, we use the "EXIT" keyword, which specifies an external command to run, in lists we don't want users to unsubscribe from. These are all administrative lists and are used only for important messages we want to be sure that faculty, staff, and/or students get all of these messages. In our case, we use a PERL script that we got from a former frequent poster to this list who has since retired.<br>><br>> Melissa Kenny<br>><br>> Web Administrator<br>> Harvard Medical School IT<br>><br>> 401 Park Drive<br>> Suite 504 West<br>> Boston, MA 02215<br>><br>><br>><br>><br>> -----Original Message-----<br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Groot, Joost de (UT-LISA)<br>> Sent: Monday, October 10, 2022 3:55 AM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: [LSTSRV-L] FW: Subcription= keyword<br>><br>> Hi Steve,<br>><br>> The easiest way I have found to block users from unsubscribing is to issue a "get <listname> (Header" command in the command box. This will lock the list and nobody is able to make changes anymore. So subscribers can't unsubscribe themselves anymore. This also blocks listowners from making changes, so choose the right time to lock the list. When a user sends an unsubscribe mail to the list they will receive this message:<br>><br>> "Sorry, the <listname> list has been locked since 2022-10-10 09:01:45 by <email listowner>. Try again later and contact the list owner if the condition persists."<br>><br>> To unlock the list you have to send "unlock <listname>" in the command box.<br>><br>> Hope this helps,<br>><br>> Kind regards,<br>><br>> Joost de Groot<br>><br>> -----Original Message-----<br>> From: Steven J Depinet <Steve.dePinet@NAU.EDU><br>> Sent: vrijdag 7 oktober 2022 17:30<br>> Subject: Subcription= keyword<br>><br>> Greetings All,<br>><br>> I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br>><br>> Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br>><br>> Thanks,<br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Kenny, Melissa S.2022-10-12T19:29:59+00:002022-10-12T19:29:59+00:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c8c3ee50.2210Hi,<br><br>Here, we use the "EXIT" keyword, which specifies an external command to run, in lists we don't want users to unsubscribe from. These are all administrative lists and are used only for important messages we want to be sure that faculty, staff, and/or students get all of these messages. In our case, we use a PERL script that we got from a former frequent poster to this list who has since retired.<br><br>Melissa Kenny<br><br>Web Administrator<br>Harvard Medical School IT<br><br>401 Park Drive<br>Suite 504 West<br>Boston, MA 02215<br><br>-----Original Message-----<br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Groot, Joost de (UT-LISA)<br>Sent: Monday, October 10, 2022 3:55 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: [LSTSRV-L] FW: Subcription= keyword<br><br>Hi Steve,<br><br>The easiest way I have found to block users from unsubscribing is to issue a "get <listname> (Header" command in the command box. This will lock the list and nobody is able to make changes anymore. So subscribers can't unsubscribe themselves anymore. This also blocks listowners from making changes, so choose the right time to lock the list. When a user sends an unsubscribe mail to the list they will receive this message:<br><br>"Sorry, the <listname> list has been locked since 2022-10-10 09:01:45 by <email listowner>. Try again later and contact the list owner if the condition persists."<br><br>To unlock the list you have to send "unlock <listname>" in the command box.<br><br>Hope this helps,<br><br>Kind regards,<br><br>Joost de Groot<br><br>-----Original Message-----<br>From: Steven J Depinet <Steve.dePinet@NAU.EDU><br>Sent: vrijdag 7 oktober 2022 17:30<br>Subject: Subcription= keyword<br><br>Greetings All,<br><br>I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner. [...] Groot, Joost de (UT-LISA)2022-10-10T07:54:57+00:002022-10-10T07:54:57+00:00FW: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a8d7990.2210Hi Steve,<br><br>The easiest way I have found to block users from unsubscribing is to issue a "get <listname> (Header" command in the command box. This will lock the list and nobody is able to make changes anymore. So subscribers can't unsubscribe themselves anymore. This also blocks listowners from making changes, so choose the right time to lock the list. When a user sends an unsubscribe mail to the list they will receive this message:<br><br>"Sorry, the <listname> list has been locked since 2022-10-10 09:01:45 by <email listowner>. Try again later and contact the list owner if the condition persists."<br><br>To unlock the list you have to send "unlock <listname>" in the command box.<br><br>Hope this helps,<br><br>Kind regards,<br><br>Joost de Groot<br><br>-----Original Message-----<br>From: Steven J Depinet <Steve.dePinet@NAU.EDU><br>Sent: vrijdag 7 oktober 2022 17:30<br>Subject: Subcription= keyword<br><br>Greetings All,<br><br>I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br><br>Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br><br>Thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843 J de Groot2022-10-10T03:07:17-04:002022-10-10T03:07:17-04:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;decf4092.2210Hi Steve,<br><br>This simplest way i have found to stop people unsubscribing is to issue a "get <listname> (header" in the listserv command box. You will receive an email with the listheader and the list will be locked. That makes it impossible to unsubscribe or edit the list. The unsubscriber will receive this message:<br><br>"Sorry, the <Listname> list has been locked since 2022-10-10 09:01:45 by<br><email listowner>. Try again later and contact the list owner if the<br>condition persists.<br><br>You have to issue a "unlock <listname>" in the command box to be able to edit the list again.<br><br>Hope this helps.<br><br>Kind regards,<br><br>Joost de GrootSteven J Depinet2022-10-07T16:25:26+00:002022-10-07T16:25:26+00:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2193e7e9.2210Thanks so much, Jacob. I was under that impression, but the “help” next to “Subscription=“ in the List Config page on the Web Interface only talks about Subscription, not unsubscription. So it’s nice to hear that.<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Oct 7, 2022, at 9:22 AM, Jacob Haller <jacob.haller@GMAIL.COM> wrote:<br>><br>> On Oct 7, 2022, at 11:30 AM, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>>> Greetings All,<br>>><br>>> I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br>>><br>>> Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br>><br>> No, the ‘Subscription=‘ setting only controls what happens to subscription requests, and has no effect on attempts to leave the mailing list. Generally, preventing people from leaving a mailing list is not something I would recommend — it generally leads to spam complaints, which damages your mail server’s reputation, which makes it more likely that your subscribers’ mail servers will classify your mail as spam.<br>><br>> There are some approaches to preventing subscribers from leaving a mailing list, though, in cases where that might be appropriate (for instance, your organization might have a staff mailing list that is supposed to go to all employees). There’s a FAQ that deals with these approaches:<br>><br>> https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html<br>><br>> You can also customize the banner that’s added to messages posted to a mailing list, so that they no longer include instructions on how to leave the mailing list, by going under ‘List Management’ to ‘Mail Templates’ and editing the BOTTOM_BANNER and BOTTOM_BANNER_HTML mail templates. (The latter is added to HTML-formatted messages, the former to other types of messages, so if you edit one you should also edit the other.)<br>><br>> -jwgh<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Jacob Haller2022-10-07T12:22:01-04:002022-10-07T12:22:01-04:00Re: Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;f3a3ed68.2210On Oct 7, 2022, at 11:30 AM, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br><br>> Greetings All,<br>><br>> I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br>><br>> Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br><br>No, the ‘Subscription=‘ setting only controls what happens to subscription requests, and has no effect on attempts to leave the mailing list. Generally, preventing people from leaving a mailing list is not something I would recommend — it generally leads to spam complaints, which damages your mail server’s reputation, which makes it more likely that your subscribers’ mail servers will classify your mail as spam.<br><br>There are some approaches to preventing subscribers from leaving a mailing list, though, in cases where that might be appropriate (for instance, your organization might have a staff mailing list that is supposed to go to all employees). There’s a FAQ that deals with these approaches:<br><br>https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html <https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html><br><br>You can also customize the banner that’s added to messages posted to a mailing list, so that they no longer include instructions on how to leave the mailing list, by going under ‘List Management’ to ‘Mail Templates’ and editing the BOTTOM_BANNER and BOTTOM_BANNER_HTML mail templates. (The latter is added to HTML-formatted messages, the former to other types of messages, so if you edit one you should also edit the other.) [...]Steven J Depinet2022-10-07T15:30:06+00:002022-10-07T15:30:06+00:00Subcription= keywordhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a23d2f35.2210Greetings All,<br><br>I have a question from a list owner, asking about people being able to unsubscribe from a list, where Subscription= Owner, and the bottom (to unsubscribe...) banner.<br><br>Does Subscription=Owner prevent people from unsubscribing (by clicking on the link in the bottom banner)? If so (or not), can the banner be eliminated from posts to a specific list?<br><br>Thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843 Jon Schwendemann2022-09-20T20:08:06+00:002022-09-20T20:08:06+00:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;12fa05ba.2209Well, the exchange admin, dispite other email working, went and bumped space, and it is working for now. Doesn't answer the question on why it had been working for years, as it was, then decided no Bueno. There hadn't been any changed to either exchange or listserv. No changes in the types of messages going out. So, who knows.<br><br>-----Original Message-----<br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Ben Parker<br>Sent: Friday, September 16, 2022 1:41 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: listserv error<br><br>On Thu, 15 Sep 2022 18:36:59 +0000, Jon Schwendemann <schwende@CORD.EDU><br>wrote:<br><br>>Insufficient system resources (UsedDiskSpace[C:\Program<br>>Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>This error screams insufficient disk space. If the error occurs in the LISTSERV Log file, then look just before this to see what list is being mailed to and how many recipients there are. The message size will not be noted but the LISTNAME and # of recipients will be. If the list has Archives, you can determine the message size from that.<br><br>If the list is largish (1,000 rcpts) and assume the message is 10K in size, the exchange server suddenly needs 10MB of disk space to handle the transient load. If the message is larger and even if #rcpts is smaller Exchange still needs gobs of disk space, but only for a short time.<br><br>Reducing MAXBSMTP may be helpful here, but first you need to understand the size of instantaneous traffic needed for your list(s) (#rcpts) and average message size. That error message says Exchange doesn't have enough disk space to handle the load. I dunno what space is available but clearly Exchange thinks it doesn't have enough. You either need more space (never a bad idea) or make the load from LISTSERV into more, but smaller chunks that Exchange can handle (reducing MAXBSMTP). [...] James Chamier2022-09-16T17:26:32+00:002022-09-16T17:26:32+00:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;eb34f63e.2209This may be of use to your Exchange admin, and aligns with Ben Parker's suggestion.<br>https://docs.microsoft.com/en-us/answers/questions/649462/exchange-2016-insufficient-system-storage.html<br><br>James<br>(Ex admin of Exchange 2003). Ben Parker2022-09-16T00:41:24-06:002022-09-16T00:41:24-06:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;ff180052.2209On Thu, 15 Sep 2022 18:36:59 +0000, Jon Schwendemann <schwende@CORD.EDU><br>wrote:<br><br>>Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>This error screams insufficient disk space. If the error occurs in the<br>LISTSERV Log file, then look just before this to see what list is being<br>mailed to and how many recipients there are. The message size will not be<br>noted but the LISTNAME and # of recipients will be. If the list has<br>Archives, you can determine the message size from that.<br><br>If the list is largish (1,000 rcpts) and assume the message is 10K in size,<br>the exchange server suddenly needs 10MB of disk space to handle the<br>transient load. If the message is larger and even if #rcpts is smaller<br>Exchange still needs gobs of disk space, but only for a short time.<br><br>Reducing MAXBSMTP may be helpful here, but first you need to understand the<br>size of instantaneous traffic needed for your list(s) (#rcpts) and average<br>message size. That error message says Exchange doesn't have enough disk<br>space to handle the load. I dunno what space is available but clearly<br>Exchange thinks it doesn't have enough. You either need more space (never a<br>bad idea) or make the load from LISTSERV into more, but smaller chunks that<br>Exchange can handle (reducing MAXBSMTP).<br><br>Take your largest list #rcpts and your largest message (from any list),<br>multiply that and then multiply that answer X3. that's how much free disk<br>space you need in the mailer queue (Exchange in this case) to handle<br>surprise large mailings through LISTSERV along with other traffic. Jon Schwendemann2022-09-15T22:18:41+00:002022-09-15T22:18:41+00:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;508cfd45.2209My SMTP_FORWARD_N is set to the exchange server. I do have a rhel smtp server, but I don’t think that is in play on this. However, exchange might be using it in some way. Either way, disk space on the smtp has been unchanged for a long time. However, I’ll have the queues and transport logs on exchange checked.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Krista<br>Sent: Thursday, September 15, 2022 4:54 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: listserv error<br><br>This is probably unrelated, but, something to check... What's your MAXBSMTP set to? Maybe this is a really roundabout way of the SMTP server complaining that you're trying to send to too many recipients in each message? I've set our server to 50 so our SMTP server doesn't assume it's a spam attack or something.<br><br>But the SMTP server admin really needs to check drive space, IMO.<br><br>Krista Landon<br><br>On Thu, Sep 15, 2022 at 4:47 PM Jacob Haller <jacob.haller@gmail.com<mailto:jacob.haller@gmail.com>> wrote:<br><br>On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <schwende@CORD.EDU<mailto:schwende@CORD.EDU>> wrote:<br><br>It shows under the listserv.log.<br>The exchange admin has looked at some things. I think he has a hard time believing it’s exchange since all other mail is fine.<br><br>OK. It sounds like the error is probably happening when LISTSERV tries to deliver the mail to its outgoing mail server. Perhaps that’s a different server than your main Exchange server? Anyway you can check LISTSERV’s configuration under ’Server Administration’/’Site Configuration’ in LISTSERV’s web interface and look at the SMTP_FORWARD_N setting. (The similarly-named SMTP_FORWARD setting isn’t normally used to send mail and is probably not relevant here.) [...]Krista2022-09-15T17:53:52-04:002022-09-15T17:53:52-04:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;af4ba103.2209This is probably unrelated, but, something to check... What's your<br>MAXBSMTP set to? Maybe this is a really roundabout way of the SMTP server<br>complaining that you're trying to send to too many recipients in each<br>message? I've set our server to 50 so our SMTP server doesn't assume it's a<br>spam attack or something.<br><br>But the SMTP server admin really needs to check drive space, IMO.<br><br>Krista Landon<br><br>On Thu, Sep 15, 2022 at 4:47 PM Jacob Haller <jacob.haller@gmail.com> wrote:<br><br>><br>><br>> On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <schwende@CORD.EDU> wrote:<br>><br>> It shows under the listserv.log.<br>> The exchange admin has looked at some things. I think he has a hard time<br>> believing it’s exchange since all other mail is fine.<br>><br>><br>> OK. It sounds like the error is probably happening when LISTSERV tries to<br>> deliver the mail to its outgoing mail server. Perhaps that’s a different<br>> server than your main Exchange server? Anyway you can check LISTSERV’s<br>> configuration under ’Server Administration’/’Site Configuration’ in<br>> LISTSERV’s web interface and look at the SMTP_FORWARD_N setting. (The<br>> similarly-named SMTP_FORWARD setting isn’t normally used to send mail and<br>> is probably not relevant here.)<br>><br>> In terms of tracking down the error, looking at the entries in the logs<br>> that surround the errors should give you the date and time, which hopefully<br>> will give the admin of LISTSERV’s outgoing mail server some additional<br>> information on where to look in the logs.<br>><br>> I don’t know the exact context of this error, or how long it’s happening,<br>> but I can’t think of a reason why LISTSERV itself would be trying to write<br>> files to C:\Program Files\Microsoft\Exchange<br>> Server\V15\TransportRoles\data\Queue.<br>><br>> Thanks,<br>> Jacob Haller<br>><br>> *From:* LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> > *On Behalf Of *Jacob Haller<br>> *Sent:* Thursday, September 15, 2022 2:04 PM<br>> *To:* LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> *Subject:* Re: listserv error<br>><br>> Where is the error showing up? In an email, in the LISTSERV log, or<br>> elsewhere?<br>><br>> -jwgh<br>><br>><br>> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <schwende@CORD.EDU> wrote:<br>><br>> I am receiving an error in my listserv, that seems to indicate it is an<br>> exchange issue.<br>> Insufficient system resources (UsedDiskSpace[C:\Program<br>> Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br>><br>> I am running on rhel 7.9, with listserv 16.5<br>> Now, of course I could upgrade listserv, but it was doing fine till just<br>> the last couple weeks, when this message cropped up.<br>><br>> My exchange person doesn’t seem to find anything, so I am wondering if<br>> there is something else, on the listserv, that could cause this.<br>> Thanks<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Jacob Haller2022-09-15T16:47:43-04:002022-09-15T16:47:43-04:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8c48b883.2209On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <schwende@CORD.EDU> wrote:<br><br>> It shows under the listserv.log.<br>> The exchange admin has looked at some things. I think he has a hard time believing it’s exchange since all other mail is fine.<br><br>OK. It sounds like the error is probably happening when LISTSERV tries to deliver the mail to its outgoing mail server. Perhaps that’s a different server than your main Exchange server? Anyway you can check LISTSERV’s configuration under ’Server Administration’/’Site Configuration’ in LISTSERV’s web interface and look at the SMTP_FORWARD_N setting. (The similarly-named SMTP_FORWARD setting isn’t normally used to send mail and is probably not relevant here.)<br><br>In terms of tracking down the error, looking at the entries in the logs that surround the errors should give you the date and time, which hopefully will give the admin of LISTSERV’s outgoing mail server some additional information on where to look in the logs.<br><br>I don’t know the exact context of this error, or how long it’s happening, but I can’t think of a reason why LISTSERV itself would be trying to write files to C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue.<br><br>Thanks,<br>Jacob Haller<br><br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Jacob Haller<br>> Sent: Thursday, September 15, 2022 2:04 PM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: Re: listserv error<br>><br>> Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?<br>><br>> -jwgh<br>><br>><br>> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <schwende@CORD.EDU <mailto:schwende@CORD.EDU>> wrote:<br>><br>> I am receiving an error in my listserv, that seems to indicate it is an exchange issue.<br>> Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br>><br>> I am running on rhel 7.9, with listserv 16.5<br>> Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.<br>><br>> My exchange person doesn’t seem to find anything, so I am wondering if there is something else, on the listserv, that could cause this.<br>> ThanksJon Schwendemann2022-09-15T19:59:02+00:002022-09-15T19:59:02+00:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;82c2173b.2209It shows under the listserv.log.<br>The exchange admin has looked at some things. I think he has a hard time believing it’s exchange since all other mail is fine.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Jacob Haller<br>Sent: Thursday, September 15, 2022 2:04 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: listserv error<br><br>Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?<br><br>-jwgh<br><br>On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <schwende@CORD.EDU<mailto:schwende@CORD.EDU>> wrote:<br><br>I am receiving an error in my listserv, that seems to indicate it is an exchange issue.<br>Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>I am running on rhel 7.9, with listserv 16.5<br>Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.<br><br>My exchange person doesn’t seem to find anything, so I am wondering if there is something else, on the listserv, that could cause this.<br>ThanksJacob Haller2022-09-15T15:03:36-04:002022-09-15T15:03:36-04:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8db677f4.2209Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?<br><br>-jwgh<br><br>> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <schwende@CORD.EDU> wrote:<br>><br>> I am receiving an error in my listserv, that seems to indicate it is an exchange issue.<br>> Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br>><br>> I am running on rhel 7.9, with listserv 16.5<br>> Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.<br>><br>> My exchange person doesn’t seem to find anything, so I am wondering if there is something else, on the listserv, that could cause this.<br>> ThanksRob Murray2022-09-15T18:55:03+00:002022-09-15T18:55:03+00:00Re: listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;1daa017a.2209Your exchange system is probably rejecting emails due to the configured threshold for available disk space ?<br><br>So your exchange person can’t do a web search ?<br><br>Have them check the queuers and Transport Logs.<br><br>Rob Murray<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Jon Schwendemann<br>Sent: September 15, 2022 3:37 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: listserv error<br><br>⚠External message: Use caution.<br>I am receiving an error in my listserv, that seems to indicate it is an exchange issue.<br>Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>I am running on rhel 7.9, with listserv 16.5<br>Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.<br><br>My exchange person doesn’t seem to find anything, so I am wondering if there is something else, on the listserv, that could cause this.<br>ThanksJon Schwendemann2022-09-15T18:36:59+00:002022-09-15T18:36:59+00:00listserv errorhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;fee823cf.2209I am receiving an error in my listserv, that seems to indicate it is an exchange issue.<br>Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>I am running on rhel 7.9, with listserv 16.5<br>Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.<br><br>My exchange person doesn't seem to find anything, so I am wondering if there is something else, on the listserv, that could cause this.<br>Thanks Jon Schwendemann2022-09-13T16:07:24+00:002022-09-13T16:07:24+00:00insufficient system resourceshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;55864ba2.2209I am receiving this error in my listserv.log file:<br>452 4.3.1 Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])<br><br>Most everything I find seems to point to the exchange server as the problem. However, is there any other possibility it is something in listserv? I have 35G free on the disk, and almost all the ram is free. Jon Schwendemann2022-09-09T19:51:29+00:002022-09-09T19:51:29+00:00Re: file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;638aa3a0.2209Can't say I do. I've only been working with listserv for about 6 years, and never used anything of that stuff.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Nathan Brindle<br>Sent: Friday, September 9, 2022 2:46 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: file validities<br><br>Not if you remember BITNET and EARN (as I see another respondent does). The file is text, you can look at it and see it's just a list of registered BITNET nodes. Just don't try to edit it (or either of the other two).<br><br>The reason BITEARN NODES and PEERS.NAMESUM and several of the other BITNET-era networking files are still part of LISTSERV is there were questions as to what might break in obscure parts of the code if those files were removed. So they remain part of LISTSERV even though BITNET is long gone.<br><br>PERMVARS FILE is LISTSERV's working cache, and you absolutely do not want to fiddle with it or you will break things.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Jon Schwendemann<br>Sent: Friday, September 09, 2022 3:35 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: Re: file validities<br><br>Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Nathan Brindle<br>Sent: Friday, September 9, 2022 2:28 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: Re: file validities<br><br>Those files have been part of LISTSERV since 1986. They were originally named using the 8x8 file naming convention under VM/CMS. There was no reason to change the names when LISTSERV was ported to the "workstation" operating systems, thus they remain with those names to this day. [...] Nathan Brindle2022-09-09T19:46:03+00:002022-09-09T19:46:03+00:00Re: file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;70d4a9f6.2209Not if you remember BITNET and EARN (as I see another respondent does). The file is text, you can look at it and see it's just a list of registered BITNET nodes. Just don't try to edit it (or either of the other two).<br><br>The reason BITEARN NODES and PEERS.NAMESUM and several of the other BITNET-era networking files are still part of LISTSERV is there were questions as to what might break in obscure parts of the code if those files were removed. So they remain part of LISTSERV even though BITNET is long gone.<br><br>PERMVARS FILE is LISTSERV's working cache, and you absolutely do not want to fiddle with it or you will break things.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Jon Schwendemann<br>Sent: Friday, September 09, 2022 3:35 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: file validities<br><br>Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Nathan Brindle<br>Sent: Friday, September 9, 2022 2:28 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: Re: file validities<br><br>Those files have been part of LISTSERV since 1986. They were originally named using the 8x8 file naming convention under VM/CMS. There was no reason to change the names when LISTSERV was ported to the "workstation" operating systems, thus they remain with those names to this day.<br><br>Nathan<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Jon Schwendemann<br>Sent: Friday, September 09, 2022 3:22 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: file validities<br><br>I have a question on some files I found in the listserv/home directory.<br>Peers.namesum<br>Permvars.file<br>Bitearn.nodes [...] Kern, Thomas (CONTR)2022-09-09T19:41:45+00:002022-09-09T19:41:45+00:00Re: file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;afd1a3c2.2209Bitearn comes from:<br><br>Bitnet - because it’s time network<br>EARN - European Applied Research Network<br><br>—<br>Thomas Kern<br>Phone: 301-905-6427<br>Thomas.Kern@hq,doe.gov Jon Schwendemann2022-09-09T19:34:55+00:002022-09-09T19:34:55+00:00Re: file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8f6663f5.2209Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Nathan Brindle<br>Sent: Friday, September 9, 2022 2:28 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: file validities<br><br>Those files have been part of LISTSERV since 1986. They were originally named using the 8x8 file naming convention under VM/CMS. There was no reason to change the names when LISTSERV was ported to the "workstation" operating systems, thus they remain with those names to this day.<br><br>Nathan<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Jon Schwendemann<br>Sent: Friday, September 09, 2022 3:22 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: file validities<br><br>I have a question on some files I found in the listserv/home directory.<br>Peers.namesum<br>Permvars.file<br>Bitearn.nodes<br><br>Seems to me, if these are legit, they could perhaps be named better. Nathan Brindle2022-09-09T19:27:30+00:002022-09-09T19:27:30+00:00Re: file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;1e74377e.2209Those files have been part of LISTSERV since 1986. They were originally named using the 8x8 file naming convention under VM/CMS. There was no reason to change the names when LISTSERV was ported to the "workstation" operating systems, thus they remain with those names to this day.<br><br>Nathan<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Jon Schwendemann<br>Sent: Friday, September 09, 2022 3:22 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: file validities<br><br>I have a question on some files I found in the listserv/home directory.<br>Peers.namesum<br>Permvars.file<br>Bitearn.nodes<br><br>Seems to me, if these are legit, they could perhaps be named better. Jon Schwendemann2022-09-09T19:22:04+00:002022-09-09T19:22:04+00:00file validitieshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c9a1caa.2209I have a question on some files I found in the listserv/home directory.<br>Peers.namesum<br>Permvars.file<br>Bitearn.nodes<br><br>Seems to me, if these are legit, they could perhaps be named better. deb cady2022-08-23T06:26:58+00:002022-08-23T06:26:58+00:00Digest dropping message?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;95bbe840.2208I just noticed that HTML digests seem to be dropping items. There is no text for item 13 in this TOC. Is this a known issue? <br><br>The item in question was simple text with 1 urk and no attachments<br>Deb<br><br>----- Forwarded message ----- From: AUTOCAT automatic digest system <listserv@listserv.syr.edu>To: "autocat@listserv.syr.edu" <autocat@listserv.syr.edu>Sent: Monday, 22 August 2022 at 09:00:12 pm GMT-7Subject: AUTOCAT Digest - 21 Aug 2022 to 22 Aug 2022 (#2022-243)<br><br>| | | |<br><br>|<br>|<br>AUTOCAT Digest - 21 Aug 2022 to 22 Aug 2022 (#2022-243)<br><br>Table of contents:<br><br>- Test 2: IMAGE Friday Funny (2)<br>- ADLaM Romanization Table Review: Request for specialized help<br>- Core Web Course: Fundamentals of Digital Library Projects Session 5<br>- Core Web Course: Fundamentals of Metadata Session 5<br>- BIBFRAME Man (5)<br>- [EXTERNAL] [AUTOCAT] BIBFRAME Man<br>- Subdivision Comic books, strips, etc.<br>- JOB: Collection Development and Metadata Librarian: Johnson C Smith, Univ, Charlotte NC<br>- JOB: Data Services Librarian, Boston College, MA<br>- JOB (take 2): Data Services Librarian, Boston College, Chestnut Hill MA<br>- Librarians do Gaga (4)<br>- Two cataloging workshops coming up soon!<br>- new semester video<br>- Help with Church Slavic transcription?<br>- Slavonic resources<br><br>- Test 2: IMAGE Friday Funny<br>- Re: Test 2: IMAGE Friday Funny (08/22)<br>From: "Klocek, Angela" <aklocek@SCCL.LIB.MI.US><br>- Re: Test 2: IMAGE Friday Funny (08/22)<br>From: Lisa Hatt <hattlisa@FHDA.EDU><br><br>- ADLaM Romanization Table Review: Request for specialized help<br>- ADLaM Romanization Table Review: Request for specialized help (08/22)<br>From: "Freas-Smith, Erin" <efre@LOC.GOV><br><br>- Core Web Course: Fundamentals of Digital Library Projects Session 5<br>- Core Web Course: Fundamentals of Digital Library Projects Session 5 (08/22)<br>From: Core-CE Announce <alcts.ce.announce@GMAIL.COM><br><br>- Core Web Course: Fundamentals of Metadata Session 5<br>- Core Web Course: Fundamentals of Metadata Session 5 (08/22)<br>From: Core-CE Announce <alcts.ce.announce@GMAIL.COM> [...]Nathan Brindle2022-08-22T12:44:16+00:002022-08-22T12:44:16+00:00Re: embedded images set uphttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;89c271bf.22081. Make sure you are using HTML email format and not "rich text" email format. This usually is more of an Outlook problem than anything else, but it may be something you can select in other products. The "rich text" option in Outlook causes Outlook/Exchange to create winmail.dat attachments, which are proprietary to Microsoft, and can't usually be decoded by anything other than Outlook, and point of fact, LISTSERV strips winmail.dat by default for that reason. That can be overridden, but if others are not using Outlook, it won't help them to do so. (By "Outlook" I mean both the separate client and the webmail versions.)<br><br>1. Binary attachments such as images are normally encoded, usually using Base64, which does increase the size of the attachments, but usually it does not double the size of the attachment. I would raise the Sizelim= setting to something large enough that you won't have to worry about it. 51K seems oddly specific. You might want to try an arbitrary setting of 100K.<br><br>1. Note also that allowing "image" alone may not be sufficient today. You might need "image,image/*". For instance, there is a MIME type for PNG images (image/png) which simply setting "image" would miss. On the other hand, JPG and GIF images should pass through with simply "image". It depends, actually, on how the originating mail client describes the attachment. (For instance, the old Eudora client used to call every binary attachment an "octet-string" rather than try to determine the actual content type and generate a proper MIME header accordingly.) The full list of image types is found at http://www.iana.org/assignments/media-types/media-types.xhtml#image . And if you are sending images, a lot of images these days are larger than 100KB, so you might want to consider just how large the images are that you are sending, and reset Sizelim= accordingly. [...] Nathan Brindle2022-08-22T12:22:03+00:002022-08-22T12:22:03+00:00Re: HTML DIgests will they ever be functional?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;11f34d74.2208HTML digests are not standardized across webmail platforms and there is no IETF RFC governing how they work. Your best bet if your mail client does not support LISTSERV's HTML digests is to use MIME DIGEST (as the manual states).<br><br>The fact is that digests were introduced originally when mail reading software was much simpler and primarily text-based. Text-only digests are compliant with RFC 1153 which governs text digests. Because there was (and is) no RFC on the subject of HTML digests, there was no way to develop a "one size fits all" solution. Therefore the HTML digests are what they are, and are unlikely to change absent a decision on the part of a majority of mail reader developers to agree on a standard.<br><br>Another historical fact about digests is that they were added at a time when mail readers did not necessarily contain automatic filters (or at least, automatic filters that were easy for the end user to configure) and everything showed up in users' inboxes. Today you have the option of adding an inbox filter that can move list mail into separate folders and keep your inbox clear for mail you need to read immediately. At least in my view, this makes it unlikely that further development of HTML digests will occur, and to be honest, I consider digest format emails mostly obsolete.<br><br>Nathan<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of deb cady<br>Sent: Friday, August 19, 2022 11:27 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: HTML DIgests will they ever be functional?<br><br>Given the information in the List Admin manual that: [...] deb cady2022-08-20T06:15:51+00:002022-08-20T06:15:51+00:00follow up - embedded images set uphttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;64b79dd9.2208This is a sizing issue related ot the attachments tab on Listowner screens. Basically assume any image file submitted appears to double in size for transmission. I have to think about the limit of message size I want for this list.<br>Just fyi.<br>Debdeb cady2022-08-20T04:36:58+00:002022-08-20T04:36:58+00:00embedded images set uphttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;126bfd37.2208I am a member of a list that send posts with embeded images to its users with no problem. But I can't get my own list at post email with embedded images. <br>How does listserv need to be setup to post emails with embedded images? <br><br>I have the attachments flag set for "image"; and have the message size at 51K . Is there someting I need on the server level?<br>Thanks,<br>Debdeb cady2022-08-20T03:27:24+00:002022-08-20T03:27:24+00:00HTML DIgests will they ever be functional?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;ac320aed.2208Given the information in the List Admin manual that:<br>Since the digest includes all of the messages as MIME attachments, all of the links in the HTML digest index are of the form: "cid: content-id" (see RFC 2111 for more information about this type of URL). Unfortunately, some email clients, even some that otherwise support HTML, do not handle such references correctly. For this reason, some subscribers may not be able to use HTML digests.<br><br>And given that most large institutions are using web-based email services (Gmail, Yahoo, Amazon, Office 365, etc...)<br><br>Is there any plan to move away from this encoding and provide a functional text+ digest?<br><br>DebBen Parker2022-08-12T08:39:48-06:002022-08-12T08:39:48-06:00Re: Where do I define dynamic queries in Linux LISTSERVhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;777dfb45.2208On Thu, 11 Aug 2022 10:38:45 -0400, Ari Rabinowitz <arimr@CS.COLUMBIA.EDU><br>wrote:<br><br>>Specifically which should we edit, ~listserv/go.user or ~listserv/home/sitecfg.file?<br><br>You should only edit ~listserv/go.user. It is not safe to edit<br>~listserv/home/sitecfg.file as this file is maintained by LISTSERV and has a<br>specific format which is not documented and which you may not understand.<br><br>>Also confusing to me is what happens if I make changes in the Web GUI. Which file(s) does that update?<br><br>Changes via the www interface go into ~listserv/home/sitecfg.file but since<br>LISTSERV is writing that file it knows how to do it correctly.<br><br>In all cases (changes via go.user or via www interface) you must restart the<br>LISTSERV process for the changes to take effect. If you make changes via<br>the www interface there is a handy 'button' you can click on to do this. If<br>you edit go.user, then you need to restart from the command line.<br><br>Also, when editing string variables in go.user don't forget to 'export' that<br>variable name. Ari Rabinowitz2022-08-11T10:38:45-04:002022-08-11T10:38:45-04:00Re: Where do I define dynamic queries in Linux LISTSERVhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;5f2a56b.2208I found the typo in my query which was causing the error and now my query is working, but I'm still confused about the relationship between the various configuration files in Linux. Specifically which should we edit, ~listserv/go.user or ~listserv/home/sitecfg.file? Also confusing to me is what happens if I make changes in the Web GUI. Which file(s) does that update?<br><br>Thanks,<br>AriAri Rabinowitz2022-08-04T09:32:12-04:002022-08-04T09:32:12-04:00Where do I define dynamic queries in Linux LISTSERVhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2c81600.2208Hi,<br>I'm confused by the various different files and file names in the<br>documentation. I'm trying to set up a dynamic query against an external<br>MySQL database. I have relinked lsv to include the uodbc library, but I<br>can't get my listserv to connect to the database and test my dynamic query.<br>It isn't clear to me exactly what the relationship is between the go.user<br>file and the home/sitecfg.file and where I should define my DYN_QUERY_CTS<br>variable.<br>Can someone please give me some guidance. I've looked at all the<br>documentation I could find, but I'm still confused. I thought I had it<br>defined correctly, but when I try a "DEBUG QUERY QUERY(CTS)" I get a<br>"Abstract: No DBMS driver available" error.<br>Here are what I think are the relevant lines from my home/sitecfg.file file:<br>DYN_QUERY_CTS TYPE=DBMS SERVER=CHO E-MAIL=mail NAME=full_name DBMS=ODBC<br>SEARCH='select email from persons_person where role=''tech-staff'''<br>UODBC_AUTH [REDACTED]<br>UODBC_AUTH_CHO [REDACTED]<br>UODBC_DSN listserv<br>UODBC_DSN_CHO listserv<br>UODBC_UID mice_read_only<br>UODBC_UID_CHO mice_read_only<br>export DYN_QUERY_CTS UODBC_AUTH_CHO UODBC_DSN_CHO UODBC_UID_CHO<br><br>And here is a list of the libraries used by lsv, showing that it is linked<br>with the uodbc library:<br>$ ldd lsv<br>linux-vdso.so.1 (0x00007ffc9dfef000)<br>libldap_r-2.4.so.2 => /lib/x86_64-linux-gnu/libldap_r-2.4.so.2<br>(0x00007f8ea000d000)<br>liblber-2.4.so.2 => /lib/x86_64-linux-gnu/liblber-2.4.so.2<br>(0x00007f8e9fffc000)<br>libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2<br>(0x00007f8e9ffe0000)<br>*libodbc.so.2 => /usr/local/lib/libodbc.so.2 (0x00007f8e9ff65000)*<br>libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8e9fd73000)<br>libsasl2.so.2 => /lib/x86_64-linux-gnu/libsasl2.so.2<br>(0x00007f8e9fd56000)<br>libgssapi.so.3 => /lib/x86_64-linux-gnu/libgssapi.so.3<br>(0x00007f8e9fd0f000)<br>libgnutls.so.30 => /lib/x86_64-linux-gnu/libgnutls.so.30<br>(0x00007f8e9fb39000)<br>libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0<br>(0x00007f8e9fb16000)<br>libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8e9fb10000)<br>/lib64/ld-linux-x86-64.so.2 (0x00007f8ea006d000)<br>libheimntlm.so.0 => /lib/x86_64-linux-gnu/libheimntlm.so.0<br>(0x00007f8e9fb04000)<br>libkrb5.so.26 => /lib/x86_64-linux-gnu/libkrb5.so.26<br>(0x00007f8e9fa71000)<br>libasn1.so.8 => /lib/x86_64-linux-gnu/libasn1.so.8<br>(0x00007f8e9f9c8000)<br>libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2<br>(0x00007f8e9f9c1000)<br>libhcrypto.so.4 => /lib/x86_64-linux-gnu/libhcrypto.so.4<br>(0x00007f8e9f989000)<br>libroken.so.18 => /lib/x86_64-linux-gnu/libroken.so.18<br>(0x00007f8e9f970000)<br>libp11-kit.so.0 => /lib/x86_64-linux-gnu/libp11-kit.so.0<br>(0x00007f8e9f83a000)<br>libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0<br>(0x00007f8e9f819000)<br>libunistring.so.2 => /lib/x86_64-linux-gnu/libunistring.so.2<br>(0x00007f8e9f695000)<br>libtasn1.so.6 => /lib/x86_64-linux-gnu/libtasn1.so.6<br>(0x00007f8e9f67f000)<br>libnettle.so.7 => /lib/x86_64-linux-gnu/libnettle.so.7<br>(0x00007f8e9f645000)<br>libhogweed.so.5 => /lib/x86_64-linux-gnu/libhogweed.so.5<br>(0x00007f8e9f60e000)<br>libgmp.so.10 => /lib/x86_64-linux-gnu/libgmp.so.10<br>(0x00007f8e9f58a000)<br>libwind.so.0 => /lib/x86_64-linux-gnu/libwind.so.0<br>(0x00007f8e9f560000)<br>libheimbase.so.1 => /lib/x86_64-linux-gnu/libheimbase.so.1<br>(0x00007f8e9f54c000)<br>libhx509.so.5 => /lib/x86_64-linux-gnu/libhx509.so.5<br>(0x00007f8e9f4fe000)<br>libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0<br>(0x00007f8e9f3d5000)<br>libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1<br>(0x00007f8e9f39a000)<br>libffi.so.7 => /lib/x86_64-linux-gnu/libffi.so.7<br>(0x00007f8e9f38e000)<br>libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f8e9f23d000)<br>Note that I am able to use "isql listserv" as the user listserv to access<br>the external database so I know that my uodbc definitions are working.<br>What am I missing? [...]James Chamier2022-08-04T11:46:25+00:002022-08-04T11:46:25+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;cfbae7bd.2208That makes sense, the "unwanted MIME part" that LISTSERV found is the TNEF/Winmail.dat content that in my opinion should never leave an Exchange environment, the MS support team obviously felt differently!<br><br>James<br>former Exchange admin<br>LISTSERV LITE Site Owner Nathan Brindle2022-08-03T18:11:12+00:002022-08-03T18:11:12+00:00Re: Moving list Archiveshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c5a93883.2208I’d recommend the following:<br><br>Assuming the LISTSERV administrator has access to the machine’s file system, the simplest solution is to clone the list, then copy the relevant archive files over from the old list into the new list’s archive directory, and rename them so they match the name of the renamed list. Then do a<br><br>REINDEX BOTH IMMEDIATE listname<br><br>(where listname is the name of the new list) to rebuild the archive and web index files. (Note that there is no need to copy the index files from the web directory; as long as there is a directory under the /archives URL for the list in question, LISTSERV will rebuild those indexes.)<br><br>There isn’t any real reason to get into the archive files themselves and change anything in them so long as people understand these are archives from a previous incarnation of this list. Indeed, I’d recommend NOT doing that.<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Glenn Eichel<br>Sent: Wednesday, August 03, 2022 2:00 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: Moving list Archives<br><br>Thanks Peter, I'll give it a whirl.<br><br>Glenn<br><br>[Image removed by sender. UMSIT:SDS Logo]<br><br>Glenn R. Eichel<br><br>SSA<br><br>UMSIT - Service Delivery and Support<br>Lecturer<br>UMaine Department of Sociology<br><br>207-581-4631<br><br>201-H Fernald Hall<br><br>Orono, Maine 04469<br><br>glenn.eichel@maine.edu<mailto:glenn.eichel@maine.edu><br><br>On Wed, Aug 3, 2022 at 1:35 PM Peter M. Weiss <Pete-Weiss@psu.edu<mailto:Pete-Weiss@psu.edu>> wrote:<br>My guess:<br><br>INDEX listname<br><br>edit and GET all files<br><br>save each filename in the new archives with the new fn.<br><br>Re-index as appropriate.<br><br>Or some listserv admin can probably do some scripting.<br><br>Update all of the template, welcome / farewall, and other docs to reflect the changes.<br><br>On 8/3/2022 12:46, Glenn Eichel wrote:<br>Greetings from wonderful Maine. [...]Glenn Eichel2022-08-03T14:00:02-04:002022-08-03T14:00:02-04:00Re: Moving list Archiveshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;58550be0.2208Thanks Peter, I'll give it a whirl.<br><br>Glenn<br><br>[image: UMSIT:SDS Logo]<br>Glenn R. Eichel<br>*SSA*<br>*UMSIT - Service Delivery and Support*<br>*Lecturer*<br>*UMaine Department of Sociology*<br>207-581-4631<br>201-H Fernald Hall<br>Orono, Maine 04469<br>glenn.eichel@maine.edu<br><br>On Wed, Aug 3, 2022 at 1:35 PM Peter M. Weiss <Pete-Weiss@psu.edu> wrote:<br><br>> My guess:<br>><br>> INDEX listname<br>><br>> edit and GET all files<br>><br>> save each filename in the new archives with the new fn.<br>><br>> Re-index as appropriate.<br>><br>> Or some listserv admin can probably do some scripting.<br>><br>> Update all of the template, welcome / farewall, and other docs to reflect<br>> the changes.<br>><br>><br>> On 8/3/2022 12:46, Glenn Eichel wrote:<br>><br>> Greetings from wonderful Maine.<br>><br>> Our school of business maintains 5 or so lists on our server. A new<br>> primary owner has taken over and wants new names to reflect a formal name<br>> change of the school. Normal practice is to clone the existing list with a<br>> new name. However, several of their lists have extensive log and notebook<br>> files that they would like to save. What do you do in this situation?<br>><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Steven J Depinet2022-08-03T17:44:31+00:002022-08-03T17:44:31+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;ab00ff51.2208Update:<br><br>The Exchange Admin unset the TNEF Option, (back to NULL), and suddenly, attachments are being distributed to the list. Ie: Listserv stopped "Removing unwanted MIME message part”...<br><br>Thanks for suggestions, this list has been a lifesaver in the past, and maybe discussion of this issue will help someone else, in the future.<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Aug 3, 2022, at 10:27, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Of course, I saw all of that when I added the Attachments keyword via the web interface. Since there’s no size limit specified, the default would be assumed, not sure what that is, but would hope that the error message would indicate that it was a size issue, not a type issue.<br>><br>> BREAKING NEWS!<br>><br>> One of my Exchange Admins just told me that they made a change (in Exchange) on the 29th, Something about Transport Neutral Encapsulation Format (TNEF). It had been set to NULL, they were asked by Micro$oft to set it (I wasn’t informed what it was set to, but the just unset it, so I’ll be testing that and will let the list know.<br>><br>> FYI: https://docs.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion?view=exchserver-2019<br>><br>> talks about TNEF...<br>><br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>><br>><br>><br>>> On Aug 2, 2022, at 15:45, deb cady <0000071b687b0306-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>>><br>>> Also have you checked sizelimit? Maybe the attachemnts are too big?<br>>><br>>> If set, this keyword causes LISTSERV to reject all messages to the list that exceed the number of lines (including the email headers) indicated. You may also use "K" or "M" to specify the size in kilobytes or megabytes rather than as a number of lines, for example, "Sizelim= 50K".<br>>><br>>> This can be helpful in discouraging subscribers from posting large messages or attachments to your list. It can also be set higher than the LISTSERV default if desired. Check with your LISTSERV administrator before changing this upward.<br>>><br>>> Deb<br>>><br>>><br>>> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br>>><br>>><br>>> So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br>>><br>>> Steven J Depinet Systems Administrator, Sr.<br>>> Steve.dePinet@nau.eduInformation Technology Services<br>>> (928) 523-6843Northern Arizona University<br>>><br>>><br>>><br>>><br>>>> On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>>>><br>>>> Greetings,<br>>>><br>>>> Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>>>><br>>>> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>>>><br>>>> Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>>>><br>>>> Thanks,<br>>>><br>>>> Steve dePinetNorthern Arizona University<br>>>> Systems Programmer, Sr.Box 5100<br>>>> Information Technology ServicesFlagstaff, Az 86011<br>>>> Steve.dePinet@nau.edu(928) 523-6843<br>>>><br>>>><br>>>><br>>>><br>>>><br>>>> ############################<br>>>><br>>>> To unsubscribe from the LSTSRV-L list:<br>>>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>>>> or click the following link:<br>>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>><br>>><br>>><br>>> ############################<br>>><br>>> To unsubscribe from the LSTSRV-L list:<br>>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>>> or click the following link:<br>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>><br>>> To unsubscribe from the LSTSRV-L list, click the following link:<br>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Peter M. Weiss2022-08-03T13:34:35-04:002022-08-03T13:34:35-04:00Re: Moving list Archiveshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8915d9bf.2208Full message available at: <a href="http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8915d9bf.2208">Re: Moving list Archives</a>Steven J Depinet2022-08-03T17:27:35+00:002022-08-03T17:27:35+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;fe0de8.2208Of course, I saw all of that when I added the Attachments keyword via the web interface. Since there’s no size limit specified, the default would be assumed, not sure what that is, but would hope that the error message would indicate that it was a size issue, not a type issue.<br><br>BREAKING NEWS!<br><br>One of my Exchange Admins just told me that they made a change (in Exchange) on the 29th, Something about Transport Neutral Encapsulation Format (TNEF). It had been set to NULL, they were asked by Micro$oft to set it (I wasn’t informed what it was set to, but the just unset it, so I’ll be testing that and will let the list know.<br><br>FYI: https://docs.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion?view=exchserver-2019<br><br>talks about TNEF...<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Aug 2, 2022, at 15:45, deb cady <0000071b687b0306-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Also have you checked sizelimit? Maybe the attachemnts are too big?<br>><br>> If set, this keyword causes LISTSERV to reject all messages to the list that exceed the number of lines (including the email headers) indicated. You may also use "K" or "M" to specify the size in kilobytes or megabytes rather than as a number of lines, for example, "Sizelim= 50K".<br>><br>> This can be helpful in discouraging subscribers from posting large messages or attachments to your list. It can also be set higher than the LISTSERV default if desired. Check with your LISTSERV administrator before changing this upward.<br>><br>> Deb<br>><br>><br>> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br>><br>><br>> So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br>><br>> Steven J Depinet Systems Administrator, Sr.<br>> Steve.dePinet@nau.eduInformation Technology Services<br>> (928) 523-6843Northern Arizona University<br>><br>><br>><br>><br>> > On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>> ><br>> > Greetings,<br>> ><br>> > Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>> ><br>> > For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>> ><br>> > Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>> ><br>> > Thanks,<br>> ><br>> > Steve dePinetNorthern Arizona University<br>> > Systems Programmer, Sr.Box 5100<br>> > Information Technology ServicesFlagstaff, Az 86011<br>> > Steve.dePinet@nau.edu(928) 523-6843<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > ############################<br>> ><br>> > To unsubscribe from the LSTSRV-L list:<br>> > write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> > or click the following link:<br>> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Steven J Depinet2022-08-03T17:20:37+00:002022-08-03T17:20:37+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a761abf9.2208Yes, I had the sender include me in another attempt to send the attachments. I got it, Listserv removed the attachments (Removing unwanted MIME message parts) for the subscribers of the list.<br><br>Looking at the message headers, I see:<br><br>Content-Type: multipart/mixed; boundary="_004_03a236a56b7f4e009ab542af454d6b06nauedu_"<br>Content-Language: en-US<br><br>Without digging out the RFC’s, I don’t see anything wrong with that. The List config does not specify any types to allow, but Attachments=All.<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Aug 2, 2022, at 15:42, deb cady <0000071b687b0306-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Did you see this note about attachments?<br>><br>> The ability of LISTSERV to filter or reject messages that contain MIME attachments is completely dependent on the ability of the poster's mail client to properly identify the MIME attachment when the mail is originally sent. Filtering/rejection is done based on the Content-Type headers found in the message, not by evaluation of the actual contents of the attachment.<br>><br>> Did you look at the original headers of the sent mail? Perhaps that's where the problem lies.<br>><br>> Alternatively there are a large number of possible attachemnt types so, for security sake, you may want to limit to be safe.<br>><br>> We use 17.0 and the attachments woorks just fine - so could be a local email admin decision.<br>><br>><br>> Deb<br>><br>><br>> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br>><br>><br>> So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br>><br>><br>><br>> Steven J Depinet Systems Administrator, Sr.<br>> Steve.dePinet@nau.eduInformation Technology Services<br>> (928) 523-6843Northern Arizona University<br>><br>><br>><br>><br>> > On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>> ><br>> > Greetings,<br>> ><br>> > Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>> ><br>> > For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>> ><br>> > Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>> ><br>> > Thanks,<br>> ><br>> > Steve dePinetNorthern Arizona University<br>> > Systems Programmer, Sr.Box 5100<br>> > Information Technology ServicesFlagstaff, Az 86011<br>> > Steve.dePinet@nau.edu(928) 523-6843<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > ############################<br>> ><br>> > To unsubscribe from the LSTSRV-L list:<br>> > write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> > or click the following link:<br>> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Glenn Eichel2022-08-03T12:46:59-04:002022-08-03T12:46:59-04:00Moving list Archiveshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;49c27e72.2208Greetings from wonderful Maine.<br><br>Our school of business maintains 5 or so lists on our server. A new primary<br>owner has taken over and wants new names to reflect a formal name change of<br>the school. Normal practice is to clone the existing list with a new name.<br>However, several of their lists have extensive log and notebook files that<br>they would like to save. What do you do in this situation?<br><br>Glenn<br>[image: UMSIT:SDS Logo]<br>Glenn R. Eichel<br>*SSA*<br>*UMSIT - Service Delivery and Support*<br>*Lecturer*<br>*UMaine Department of Sociology*<br>207-581-4631<br>201-H Fernald Hall<br>Orono, Maine 04469<br>glenn.eichel@maine.eduJacob Haller2022-08-02T23:28:40-04:002022-08-02T23:28:40-04:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;7276dadf.2208> On Aug 2, 2022, at 5:32 PM, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br><br>My guess is that<br><br>Misc-Options= KEEP_EXCHANGE_DATA<br><br>will have the desired effect. This isn’t a new LISTSERV feature, though, so if this is something you’ve only started noticing recently, it is probably due to some change on the sender’s end (but it may be easier to use the above setting than to figure out what happened on the sender’s end).<br><br>See this tech tip:<br><br>https://www.lsoft.com/news/techtipLSV-issue5-2017.asp <https://www.lsoft.com/news/techtipLSV-issue5-2017.asp><br><br>for additional information about this setting and ‘Attachments= All’.<br><br>-jwghdeb cady2022-08-02T22:45:25+00:002022-08-02T22:45:25+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;7f60bc31.2208Also have you checked sizelimit? Maybe the attachemnts are too big?<br>If set, this keyword causes LISTSERV to reject all messages to the list that exceed the number of lines (including the email headers) indicated. You may also use "K" or "M" to specify the size in kilobytes or megabytes rather than as a number of lines, for example, "Sizelim= 50K".<br><br>This can be helpful in discouraging subscribers from posting large messages or attachments to your list. It can also be set higher than the LISTSERV default if desired. Check with your LISTSERV administrator before changing this upward.<br><br>Deb<br><br>On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br><br>So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br><br>Steven J Depinet Systems Administrator, Sr.<br>Steve.dePinet@nau.eduInformation Technology Services<br>(928) 523-6843Northern Arizona University<br><br>> On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Greetings,<br>><br>> Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>><br>> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>><br>> Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>><br>> Thanks,<br>><br>> Steve dePinetNorthern Arizona University<br>> Systems Programmer, Sr.Box 5100<br>> Information Technology ServicesFlagstaff, Az 86011<br>> Steve.dePinet@nau.edu(928) 523-6843<br>><br>><br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1deb cady2022-08-02T22:42:04+00:002022-08-02T22:42:04+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;586b4dc4.2208Did you see this note about attachments?<br>The ability of LISTSERV to filter or reject messages that contain MIME attachments is completely dependent on the ability of the poster's mail client to properly identify the MIME attachment when the mail is originally sent. Filtering/rejection is done based on the Content-Type headers found in the message, not by evaluation of the actual contents of the attachment. <br><br>Did you look at the original headers of the sent mail? Perhaps that's where the problem lies.<br>Alternatively there are a large number of possible attachemnt types so, for security sake, you may want to limit to be safe.<br>We use 17.0 and the attachments woorks just fine - so could be a local email admin decision.<br><br>Deb<br><br>On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br><br>So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br><br>Steven J Depinet Systems Administrator, Sr.<br>Steve.dePinet@nau.eduInformation Technology Services<br>(928) 523-6843Northern Arizona University<br><br>> On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Greetings,<br>><br>> Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>><br>> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>><br>> Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>><br>> Thanks,<br>><br>> Steve dePinetNorthern Arizona University<br>> Systems Programmer, Sr.Box 5100<br>> Information Technology ServicesFlagstaff, Az 86011<br>> Steve.dePinet@nau.edu(928) 523-6843<br>><br>><br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Steven J Depinet2022-08-02T21:32:59+00:002022-08-02T21:32:59+00:00Re: Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2253e3d7.2208So, setting "Attachments=All” does not solve the issue, and I have 3 other list owners with the same complaint today, Any Idea what’s going on? Did Microsoft change something in Exchange? The Mime type for the one that failed with Attachments=All was Content-Type: multipart/mixed; but since it was ALL, I would think that that doesn’t matter.<br><br>Steven J Depinet Systems Administrator, Sr.<br>Steve.dePinet@nau.eduInformation Technology Services<br>(928) 523-6843Northern Arizona University<br><br>> On Aug 2, 2022, at 08:38, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> Greetings,<br>><br>> Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br>><br>> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br>><br>> Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br>><br>> Thanks,<br>><br>> Steve dePinetNorthern Arizona University<br>> Systems Programmer, Sr.Box 5100<br>> Information Technology ServicesFlagstaff, Az 86011<br>> Steve.dePinet@nau.edu(928) 523-6843<br>><br>><br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Steven J Depinet2022-08-02T15:38:50+00:002022-08-02T15:38:50+00:00Removing unwanted MIME message partshttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;2eb5cfd8.2208Greetings,<br><br>Since the upgrade to Listserv v17.0 (and/or whatever changes to Exchange that may have been applied), I’ve had a few complaints that attachments did not get sent to a list. Neither list has the “Attachments-“ keyword, but in both cases, the list owner has stated that they have sent attachments thru the list in the past. Was there a change in the default? The doc doesn’t specify a default explicitly, but “Attachments=no” is listed first in the help… Since neither list had the keyword, I tried adding “Attachments=yes” to one list. The same issue, the Listserv log shows: “...Removing unwanted MIME message parts…”.<br><br>For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.<br><br>Was there a change in default behavior for attachments for v17.0 (from v16.5)? Should the “Attachments=all” work for .pdf and .docx attachments? Or do I need to add the MIME-Types?<br><br>Thanks,<br><br>Steve dePinetNorthern Arizona University<br>Systems Programmer, Sr.Box 5100<br>Information Technology ServicesFlagstaff, Az 86011<br>Steve.dePinet@nau.edu(928) 523-6843Richter, Andy2022-07-22T14:00:27+00:002022-07-22T14:00:27+00:00Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;a6e9f537.2207I appreciate all of the feedback. We eventually get Amazon SES to work by adding the following line to sitecfg.file.<br>DEBUG_DMARC_REWRITE *<br>This feature uses DMARC functionality to rewrite the "From" address on every message passing through LISTSERV so that all messages sent "From" ...@list.vanderbilt.edu.<br>This has the desired result of all email flowing and being delivered properly.<br><br>At Vanderbilt we had also implemented an anti-phishing policy within the last few months that warns users the first time they receive a message from a new address.<br>Somehow the confluence of these two changes has resulted in one our list owners seeing the following.<br><br>[cid:image001.png@01D89DA9.7B4F5460]<br><br>I told her this might happen at first, but then it should cease once people receive several messages from the same sender. She reported she sends messages almost daily and this has been happening for a month. I asked Microsoft about it, and was told they have an algorithm for determining when to warn users that they don't publish so it won't be abused. Any ideas or suggestions?<br><br>Andy<br><br>[Vanderbilt]<br><br>Andy Richter<br>Senior System Administrator, Hosting Services<br>Information Technology | Vanderbilt University<br>615.343.4518 | andy.richter@vanderbilt.edu<mailto:andy.richter@vanderbilt.edu><br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Barth, Michael<br>Sent: Tuesday, June 14, 2022 8:58 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)<br><br>My gut tells me it's the TLS changes that occurred with outlook. They started requiring TLS 1.2 and higher. You might be hitting a legacy route for that, or an invalid SMTP relay. I'd check into what those TLS requirements are<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM>> On Behalf Of Phelps, Eli Jackson<br>Sent: Tuesday, June 14, 2022 8:45 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<mailto:LSTSRV-L@PEACH.EASE.LSOFT.COM><br>Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES) [...] Peter M. Weiss2022-07-16T10:04:41-04:002022-07-16T10:04:41-04:00Re: unusual Gmail bouncehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8c3c4503.2207Full message available at: <a href="http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8c3c4503.2207">Re: unusual Gmail bounce</a>Jacob Haller2022-07-16T09:22:19-04:002022-07-16T09:22:19-04:00Re: unusual Gmail bouncehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;60d907e4.2207The IP addresses listed in the monitoring report belong to hostmonster.com <http://hostmonster.com/>, it looks like. Are those IP addresses you would expect LISTSERV’s mail to be coming from?<br><br>Is the address in questions actually subscribed to the mailing list?<br><br>If the answer to either of these questions is ’no’, then I would suspect that some other address is subscribed to the mailing list that is forwarding to the gmail address.<br><br>-jwgh<br><br>On Jul 16, 2022, at 9:13 AM, Peter M. Weiss <Pete-Weiss@PSU.EDU> wrote:<br><br>> This week, I have received two similiar bounce reports for the same Gmail subscriber recipient. This list had had 17 messages distributed in this 1-week time-frame. The other 80 Gmail subscribers are not having this issue. I checked with our site's admin and NTF.<br>><br>> That particular email address is also a QUIET: owner and does NOT receive list's admin messages (errors, moderation).<br>><br>> Thoughts? e.g., listserv Peer backbone?<br>><br>> 1 07/11 07/11 <[suppressed]@GMAIL.COM> <mailto:CARMINE.PRESTIA@GMAIL.COM><br>> Last error: 5.7.25 550-5.7.25 [74.220.200.20] The IP address<br>> sending this message does not have a 550-5.7.25 PTR<br>> record setup, or the corresponding forward DNS<br>> entry does not 550-5.7.25 point to the sending IP.<br>> As a policy, Gmail does not accept messages<br>> 550-5.7.25 from IPs with missing PTR records.<br>> Please visi... (165 bytes suppressed)<br>><br>> 1 07/15 07/15 <[suppressed]@GMAIL.COM> <mailto:CARMINE.PRESTIA@GMAIL.COM><br>> Last error: 5.7.25 550-5.7.25 [67.20.84.70] The IP address<br>> sending this message does not have a PTR 550-5.7.25<br>> record setup, or the corresponding forward DNS<br>> entry does not point 550-5.7.25 to the sending IP.<br>> As a policy, Gmail does not accept messages from<br>> 550-5.7.25 IPs with missing PTR records. Please<br>> visit ... (165 bytes suppressed)<br>> --<br>><br>> Pete <https://www.llrx.com/author/pete-weiss/><br>> Sr. Systems Configurator, emeritus<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1 <http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1>Peter M. Weiss2022-07-16T09:13:55-04:002022-07-16T09:13:55-04:00unusual Gmail bouncehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;cc6bbf45.2207Full message available at: <a href="http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;cc6bbf45.2207">unusual Gmail bounce</a>Shinn Wu2022-07-05T18:58:53+00:002022-07-05T18:58:53+00:00Re: OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;c3cd8027.2207Thank Jacob, I am sure that the cookies expired after 48 hours from Friday noon because I did not see the ss-staff.ok*.<br><br>Shinn Jacob Haller2022-07-05T14:53:56-04:002022-07-05T14:53:56-04:00Re: OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;8ce6481f.2207Use the ‘All Moderators’ option and you should see all messages awaiting moderation or confirmation.<br><br>-jwgh<br><br>> On Jul 5, 2022, at 10:12 AM, Shinn Wu <shinn@SSCERT.UCLA.EDU> wrote:<br>><br>> Hello Peter and Jacob,<br>><br>> The list is configured as 'Send= Confirm...'. The sender did not click the confirmation URL, so it did not send out (i.e. not moderated).<br>><br>> <image.png><br>><br>> Thank you and good to know the command.<br>><br>> Shinn<br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> on behalf of Jacob Haller <jacob.haller@GMAIL.COM><br>> Sent: Tuesday, July 5, 2022 7:03 AM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM <LSTSRV-L@PEACH.EASE.LSOFT.COM><br>> Subject: Re: OK Confirmation<br>><br>> On Jul 5, 2022, at 8:25 AM, Peter M. Weiss <Pete-Weiss@PSU.EDU <mailto:Pete-Weiss@PSU.EDU>> wrote:<br>><br>>> insert listname:<br>>><br>>> https://lists.psu.edu/cgi-bin/wa?MOD= <https://lists.psu.edu/cgi-bin/wa?MOD=>listname<br>><br>> That’ll do the trick. I would just add that, if you are not one of the people the moderation request was sent to, you will have to check the ‘All Moderators’ box and click the ‘Refresh’ button.<br>><br>> -jwgh<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1 <http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1 <http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1>Shinn Wu2022-07-05T14:12:13+00:002022-07-05T14:12:13+00:00Re: OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;7a683672.2207Hello Peter and Jacob,<br><br>The list is configured as 'Send= Confirm...'. The sender did not click the confirmation URL, so it did not send out (i.e. not moderated).<br><br>[cid:b1765892-606b-41c9-9a46-88f02094d0f4]<br><br>Thank you and good to know the command.<br><br>Shinn Jacob Haller2022-07-05T10:03:05-04:002022-07-05T10:03:05-04:00Re: OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;eb91c791.2207On Jul 5, 2022, at 8:25 AM, Peter M. Weiss <Pete-Weiss@PSU.EDU> wrote:<br><br>> insert listname:<br>><br>> https://lists.psu.edu/cgi-bin/wa?MOD= <https://lists.psu.edu/cgi-bin/wa?MOD=>listname<br><br>That’ll do the trick. I would just add that, if you are not one of the people the moderation request was sent to, you will have to check the ‘All Moderators’ box and click the ‘Refresh’ button.<br><br>-jwghPeter M. Weiss2022-07-05T08:25:09-04:002022-07-05T08:25:09-04:00Re: OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;d5a52519.2207Full message available at: <a href="http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;d5a52519.2207">Re: OK Confirmation</a>Shinn Wu2022-07-03T01:20:34+00:002022-07-03T01:20:34+00:00OK Confirmationhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;6f9e5546.2207Hello,<br><br>We are using RHL 17.0 Listserv.<br><br>One faculty sent a post to a list but he failed to click the 'OK' URL which was sent to his account yesterday at noon. How will I as a Listserv admin release the post (e.g. ss-staff.ok21d8b3) by web or email? The cookies will expire in less than 18 hours and we could not contact the faculty because of July 4th long weekend.<br><br>Thank you,<br><br>Shinn Jacob Haller2022-06-27T00:23:34-04:002022-06-27T00:23:34-04:00Re: Post to List - Turnaround Timehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;921fb544.2206On Jun 26, 2022, at 6:57 PM, Orrell, Justin <000007326c001a5a-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br><br>> We’re running v17 on a Server 2019 virtual server and I’m wondering if it’s possible to tweak the handling time for email sends to lists.<br>><br>> For example, we have a list with just over 1500 recipients and posting to the list takes 35 minutes to be sent to recipients; is this normal? Can this be tweaked at all?<br><br>That does seem slow, just over 40 recipients per second. I would look in the LISTSERV log file to see when LISTSERV started processing the message and how long it took. The log file entries to look for should be along these lines:<br><br>27 Jun 2022 08:11:16 Processing file 5023707 from MAILER@LISTS.EXAMPLE.COM<br>27 Jun 2022 08:11:16 Processing mail from chris@EXAMPLE.COM for TEST-L<br>DMARC(EXAMPLE.COM)> v=DMARC1; p=none;<br>27 Jun 2022 08:11:16 Distributing mail ("TEST-L") from owner-TEST-L@LISTS.EXAMPLE.COM...<br>[...]<br>27 Jun 2022 08:15:08 Enqueued for background delivery, ID=N-33F39B0A<br>27 Jun 2022 08:15:08 Done - 2 outbound file (1500 rcpts).<br>27 Jun 2022 08:15:08 Message DISTRIBUTEd to 1500 recipients.<br><br>If the message is from a non-subscriber, or a new subscriber, then the message may be delayed by ten minutes as part of LISTSERV’s anti-spam feature. In that case, looking ten minute before the above you would see:<br><br>27 Jun 2022 08:01:16 Processing file 5023707 from MAILER@SPIDER.EASE.LSOFT.COM<br>27 Jun 2022 08:01:16 -> Inserting top/bottom banners...<br>-> Not a subscriber, will process in 10 minutes.<br><br>This ten minute ’spam quarantine’ is normal and part of LISTSERV’s anti-spam feature. If the mailing list is set up so that spam isn’t a concern, then it can be reduced or removed using the ‘Loopcheck= Spam-Delay()‘ setting described at http://www.lsoft.com/manuals/17.0/listkwd/kLoopcheck.html <http://www.lsoft.com/manuals/17.0/listkwd/kLoopcheck.html> . [...]Krista2022-06-27T00:05:24-04:002022-06-27T00:05:24-04:00Re: Post to List - Turnaround Timehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;66cc645a.2206How many workers do you have set? I'm on 16.5 so things might be a bit<br>different but we set up 4 worker processes and have I only set out 50 at a<br>time.<br><br>On Mon, Jun 27, 2022, 12:02 AM Orrell, Justin <<br>000007326c001a5a-dmarc-request@peach.ease.lsoft.com> wrote:<br><br>> We’re running v17 on a Server 2019 virtual server and I’m wondering if<br>> it’s possible to tweak the handling time for email sends to lists.<br>><br>><br>><br>> For example, we have a list with just over 1500 recipients and posting to<br>> the list takes 35 minutes to be sent to recipients; is this normal? Can<br>> this be tweaked at all?<br>><br>><br>><br>> Thanks,<br>><br>><br>><br>> Justin<br>><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Orrell, Justin2022-06-26T22:57:50+00:002022-06-26T22:57:50+00:00Post to List - Turnaround Timehttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;66e190cc.2206We're running v17 on a Server 2019 virtual server and I'm wondering if it's possible to tweak the handling time for email sends to lists.<br><br>For example, we have a list with just over 1500 recipients and posting to the list takes 35 minutes to be sent to recipients; is this normal? Can this be tweaked at all?<br><br>Thanks,<br><br>Justin Steven J Depinet2022-06-15T22:43:00+00:002022-06-15T22:43:00+00:00files in spool directoryhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;fbbce408.2206Greetings,<br><br>After having upgraded to Listserv v17.0 , I started seeing files like "in62aa5923-09c40” in listserv’s spool directory. Any idea what they are for? Is there a utility for me to see what’s in or causing them?<br><br>Thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843Barth, Michael2022-06-14T13:58:28+00:002022-06-14T13:58:28+00:00Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;94e265d5.2206My gut tells me it’s the TLS changes that occurred with outlook. They started requiring TLS 1.2 and higher. You might be hitting a legacy route for that, or an invalid SMTP relay. I’d check into what those TLS requirements are<br><br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Phelps, Eli Jackson<br>Sent: Tuesday, June 14, 2022 8:45 AM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)<br><br>CAUTION: This email originated from outside of Indian Prairie School District 204. Do not click on any links or open/save attachments unless you recognize the sender's email address and know that the content is safe.<br>…Almost identical issue here too:<br><br>We have hosted our own LISTSERV environment on-prem for almost two decades now. As of about 2 months ago all of a sudden no external partners can post on our lists either but, can receive from those same lists. Our mail exchange has been using …mail.protection.outlook.com for the last several years. I’ve spent the last 2 months troubleshooting with numerous Microsoft engineers and we’re just going in circles.<br><br>Thanks,<br>Eli PhelpsPhelps, Eli Jackson2022-06-14T13:45:13+00:002022-06-14T13:45:13+00:00Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;82000796.2206…Almost identical issue here too:<br><br>We have hosted our own LISTSERV environment on-prem for almost two decades now. As of about 2 months ago all of a sudden no external partners can post on our lists either but, can receive from those same lists. Our mail exchange has been using …mail.protection.outlook.com for the last several years. I’ve spent the last 2 months troubleshooting with numerous Microsoft engineers and we’re just going in circles.<br><br>Thanks,<br>Eli Phelps✉ Nick Abiola-Bisiolu2022-06-14T09:24:28-04:002022-06-14T09:24:28-04:00Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;b2eb2a43.2206Instead of using Amazon SES as your Listserv email gateway why not route<br>the traffic to your domain gateway SMTP server to handle the outbound<br>traffic. I noticed that your email is primary host is Microsoft Outlook.<br>They might have a service similar to Google SMTP Gateway to support your<br>domain SMTP traffic.<br>Our Listserv is hosted on Amazon AWS and forwarded all outbound emails to<br>our Google SMTP gateway successfully for many years now.<br><br>Regards,<br>Nick<br>IEEE<br><br>On Tue, Jun 14, 2022 at 9:14 AM Richter, Andy <<br>00000727343bd47b-dmarc-request@peach.ease.lsoft.com> wrote:<br><br>> We have LISTSERV configured to work properly with Amazon Simple Email<br>> Service for messages that originate from Vanderbilt.edu. However, all of<br>> our LISTSERV messages that originate from our external partners are being<br>> blocked because we are unable to verify their email addresses to Amazon<br>> SES. If you have LISTSERV fully working with Amazon SES, I would appreciate<br>> any advice on what I need to do to make it fully work for Vanderbilt<br>> University.<br>><br>><br>><br>> [image: Vanderbilt]<br>><br>><br>><br>> *Andy Richter*<br>> Senior System Administrator, Hosting Services<br>> Information Technology | Vanderbilt University<br>> 615.343.4518 | andy.richter@vanderbilt.edu<br>><br>><br>><br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Richter, Andy2022-06-14T13:12:59+00:002022-06-14T13:12:59+00:00configuring LISTSERV to work with Amazon Simple Email Service (SES)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;cee3eb5e.2206We have LISTSERV configured to work properly with Amazon Simple Email Service for messages that originate from Vanderbilt.edu. However, all of our LISTSERV messages that originate from our external partners are being blocked because we are unable to verify their email addresses to Amazon SES. If you have LISTSERV fully working with Amazon SES, I would appreciate any advice on what I need to do to make it fully work for Vanderbilt University.<br><br>[Vanderbilt]<br><br>Andy Richter<br>Senior System Administrator, Hosting Services<br>Information Technology | Vanderbilt University<br>615.343.4518 | andy.richter@vanderbilt.edu<mailto:andy.richter@vanderbilt.edu> Peter Ip2022-05-26T14:52:18-04:002022-05-26T14:52:18-04:00antispam/antivirus for Listserv?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;364e55ed.2206Hi,<br><br>I'm an administrator of the Listserv for the University of Toronto and we<br>are currently running Sophos PureMessage for antivirus/antispam in front<br>of Listserv. We are looking to decommission Sophos PureMessage.<br><br>We would be interested to know what others, esp other universities, are<br>using for antispam/antivirus. Any pros/cons would be appreciated.<br><br>Thanks,<br><br>Peter Ip<br>Systems and Solutions Group, ITS<br>University of Toronto<br>email: peter.ip@utoronto.ca Peter M. Weiss2022-04-20T13:39:50-04:002022-04-20T13:39:50-04:00Re: Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;1d0f8af0.2204Full message available at: <a href="http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;1d0f8af0.2204">Re: Broken list archive after copy from old system</a>✉ Nick Abiola-Bisiolu2022-04-20T12:41:08-04:002022-04-20T12:41:08-04:00Re: Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;5f62e75.2204Hi All,<br><br>What was the command a user can send via email to listserv to update his<br>name associated with his subscribed email address?<br>If you're subscribed as (kevin Joe <k.joe@name.com>) and want to update it<br>to (Dr. Kevin Joe <k.joe@name.com>).<br><br>On Mon, Apr 18, 2022 at 2:17 PM Steven J Depinet <<br>000006f7973f2bb4-dmarc-request@peach.ease.lsoft.com> wrote:<br><br>> Ok, never mind, I found it in List Configuration…<br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>><br>><br>><br>> > On Apr 18, 2022, at 11:11, Steven J Depinet <<br>> 000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>> ><br>> > So, how do I tell it to look in /home, instead of /export/home. Or do I<br>> have to symlink /export/home to /home. I’ve been modifying the old Solariw<br>> written scripts to just use /home, but this path is probably stored<br>> somewhere in the list<br>> > file. Encrypted, so I can’t modify it without using a Listserv utility,<br>> if it exists.<br>> ><br>> > Or, is the symlink required anyway. It existed on the old system, but I<br>> was trying to eliminate references to /export/hoe on the new system.<br>> ><br>> > Steve dePinet Northern Arizona University<br>> > Systems Programmer, Sr. Box 5100<br>> > Information Technology Services Flagstaff, Az 86011<br>> > Steve.dePinet@nau.edu (928) 523-6843<br>> ><br>> ><br>> ><br>> ><br>> >> On Apr 18, 2022, at 10:49, Nathan Brindle <nathan@LSOFT.COM> wrote:<br>> >><br>> >> The directory /export/home/listserv/notebook/buslib-l does not exist,<br>> you will have to create it.<br>> >><br>> >> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html<br>> >><br>> >> Nathan<br>> >><br>> >> -----Original Message-----<br>> >> From: LISTSERV Site Administrators' Forum <<br>> LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Steven J Depinet<br>> >> Sent: Monday, April 18, 2022 1:40 PM<br>> >> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> >> Subject: Broken list archive after copy from old system<br>> >><br>> >> Greetings,<br>> >><br>> >> I copied my Listserv installation from an old RHEL6 VM to a new RHEL7<br>> system and installed the RHEL7 binary over the weekend. Now, I have one of<br>> my oldest lists complaining:<br>> >><br>> >> An error occurred while logging mail to the archives of the BUSLIB-L<br>> list.<br>> >> An incomplete copy of the message might be present in the archive<br>> file. The<br>> >> list is being held to prevent further occurrences of this error. Please<br>> take<br>> >> corrective action and issue a "FREE BUSLIB-L" command when you<br>> want the<br>> >> message to be reprocessed.<br>> >><br>> >> Serious error occurred - traceback follows<br>> >> ------------------------------------------<br>> >>>>> Error X'00000011' opening file<br>> /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<<br>> >> -> Severity: Warning<br>> >> -> Facility: Generic error codes<br>> >> -> Abstract: File/major entity not found<br>> >> -> I/O mode: Record write<br>> >>>>> Error X'00000011' logging message to archives <<<<br>> >> -> Severity: Warning<br>> >> -> Facility: Generic error codes<br>> >> -> Abstract: File/major entity not found<br>> >><br>> >> I tried a reindex and then a free, but the error re-occurred (possibly<br>> on the 2nd attempt to copy the same post).<br>> >><br>> >> Any ideas on what to try next?<br>> >><br>> >><br>> >> Steve dePinet Northern Arizona<br>> University<br>> >> Systems Programmer, Sr. Box 5100<br>> >> Information Technology Services Flagstaff, Az 86011<br>> >> Steve.dePinet@nau.edu (928) 523-6843<br>> >><br>> >> ############################<br>> >><br>> >> To unsubscribe from the LSTSRV-L list:<br>> >> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> >> or click the following link:<br>> >> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>> >><br>> >> ############################<br>> >><br>> >> To unsubscribe from the LSTSRV-L list:<br>> >> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> >> or click the following link:<br>> >> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>> ><br>> ><br>> > ############################<br>> ><br>> > To unsubscribe from the LSTSRV-L list:<br>> > write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> > or click the following link:<br>> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Steven J Depinet2022-04-18T18:17:45+00:002022-04-18T18:17:45+00:00Re: Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;aa1b7e1c.2204Ok, never mind, I found it in List Configuration…<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Apr 18, 2022, at 11:11, Steven J Depinet <000006f7973f2bb4-dmarc-request@PEACH.EASE.LSOFT.COM> wrote:<br>><br>> So, how do I tell it to look in /home, instead of /export/home. Or do I have to symlink /export/home to /home. I’ve been modifying the old Solariw written scripts to just use /home, but this path is probably stored somewhere in the list<br>> file. Encrypted, so I can’t modify it without using a Listserv utility, if it exists.<br>><br>> Or, is the symlink required anyway. It existed on the old system, but I was trying to eliminate references to /export/hoe on the new system.<br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>><br>><br>><br>>> On Apr 18, 2022, at 10:49, Nathan Brindle <nathan@LSOFT.COM> wrote:<br>>><br>>> The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.<br>>><br>>> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html<br>>><br>>> Nathan<br>>><br>>> -----Original Message-----<br>>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Steven J Depinet<br>>> Sent: Monday, April 18, 2022 1:40 PM<br>>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>>> Subject: Broken list archive after copy from old system<br>>><br>>> Greetings,<br>>><br>>> I copied my Listserv installation from an old RHEL6 VM to a new RHEL7 system and installed the RHEL7 binary over the weekend. Now, I have one of my oldest lists complaining:<br>>><br>>> An error occurred while logging mail to the archives of the BUSLIB-L list.<br>>> An incomplete copy of the message might be present in the archive file. The<br>>> list is being held to prevent further occurrences of this error. Please take<br>>> corrective action and issue a "FREE BUSLIB-L" command when you want the<br>>> message to be reprocessed.<br>>><br>>> Serious error occurred - traceback follows<br>>> ------------------------------------------<br>>>>>> Error X'00000011' opening file /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<<br>>> -> Severity: Warning<br>>> -> Facility: Generic error codes<br>>> -> Abstract: File/major entity not found<br>>> -> I/O mode: Record write<br>>>>>> Error X'00000011' logging message to archives <<<<br>>> -> Severity: Warning<br>>> -> Facility: Generic error codes<br>>> -> Abstract: File/major entity not found<br>>><br>>> I tried a reindex and then a free, but the error re-occurred (possibly on the 2nd attempt to copy the same post).<br>>><br>>> Any ideas on what to try next?<br>>><br>>><br>>> Steve dePinet Northern Arizona University<br>>> Systems Programmer, Sr. Box 5100<br>>> Information Technology Services Flagstaff, Az 86011<br>>> Steve.dePinet@nau.edu (928) 523-6843<br>>><br>>> ############################<br>>><br>>> To unsubscribe from the LSTSRV-L list:<br>>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>>> or click the following link:<br>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>><br>>> ############################<br>>><br>>> To unsubscribe from the LSTSRV-L list:<br>>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>>> or click the following link:<br>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Steven J Depinet2022-04-18T18:11:34+00:002022-04-18T18:11:34+00:00Re: Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;26a622aa.2204So, how do I tell it to look in /home, instead of /export/home. Or do I have to symlink /export/home to /home. I’ve been modifying the old Solariw written scripts to just use /home, but this path is probably stored somewhere in the list<br>file. Encrypted, so I can’t modify it without using a Listserv utility, if it exists.<br><br>Or, is the symlink required anyway. It existed on the old system, but I was trying to eliminate references to /export/hoe on the new system.<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Apr 18, 2022, at 10:49, Nathan Brindle <nathan@LSOFT.COM> wrote:<br>><br>> The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.<br>><br>> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html<br>><br>> Nathan<br>><br>> -----Original Message-----<br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Steven J Depinet<br>> Sent: Monday, April 18, 2022 1:40 PM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: Broken list archive after copy from old system<br>><br>> Greetings,<br>><br>> I copied my Listserv installation from an old RHEL6 VM to a new RHEL7 system and installed the RHEL7 binary over the weekend. Now, I have one of my oldest lists complaining:<br>><br>> An error occurred while logging mail to the archives of the BUSLIB-L list.<br>> An incomplete copy of the message might be present in the archive file. The<br>> list is being held to prevent further occurrences of this error. Please take<br>> corrective action and issue a "FREE BUSLIB-L" command when you want the<br>> message to be reprocessed.<br>><br>> Serious error occurred - traceback follows<br>> ------------------------------------------<br>>>>> Error X'00000011' opening file /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<<br>> -> Severity: Warning<br>> -> Facility: Generic error codes<br>> -> Abstract: File/major entity not found<br>> -> I/O mode: Record write<br>>>>> Error X'00000011' logging message to archives <<<<br>> -> Severity: Warning<br>> -> Facility: Generic error codes<br>> -> Abstract: File/major entity not found<br>><br>> I tried a reindex and then a free, but the error re-occurred (possibly on the 2nd attempt to copy the same post).<br>><br>> Any ideas on what to try next?<br>><br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1Nathan Brindle2022-04-18T17:49:48+00:002022-04-18T17:49:48+00:00Re: Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;40165de3.2204The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.<br><br>http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html<br><br>Nathan<br><br>-----Original Message-----<br>From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Steven J Depinet<br>Sent: Monday, April 18, 2022 1:40 PM<br>To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>Subject: Broken list archive after copy from old system<br><br>Greetings,<br><br>I copied my Listserv installation from an old RHEL6 VM to a new RHEL7 system and installed the RHEL7 binary over the weekend. Now, I have one of my oldest lists complaining:<br><br>An error occurred while logging mail to the archives of the BUSLIB-L list.<br>An incomplete copy of the message might be present in the archive file. The<br>list is being held to prevent further occurrences of this error. Please take<br>corrective action and issue a "FREE BUSLIB-L" command when you want the<br>message to be reprocessed.<br><br>Serious error occurred - traceback follows Steven J Depinet2022-04-18T17:40:15+00:002022-04-18T17:40:15+00:00Broken list archive after copy from old systemhttp://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;cd89d020.2204Greetings,<br><br>I copied my Listserv installation from an old RHEL6 VM to a new RHEL7 system and installed the RHEL7 binary over the weekend. Now, I have one of my oldest lists complaining:<br><br>An error occurred while logging mail to the archives of the BUSLIB-L list.<br>An incomplete copy of the message might be present in the archive file. The<br>list is being held to prevent further occurrences of this error. Please take<br>corrective action and issue a "FREE BUSLIB-L" command when you want the<br>message to be reprocessed.<br><br>Serious error occurred - traceback follows Steven J Depinet2022-04-15T15:54:34+00:002022-04-15T15:54:34+00:00Re: SELinux (RHEL7) and port 2306 (Listserv V17.0)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;e5c1a3fb.2204Thanks Nathan, I’ll add "setsebool -P httpd_can_network_connect 1" (one of the settings that I had seen mentioned, but didn’t know if it was required) to the "semanage port -a -t http_port_t -p tcp 2306” that I’ve run. That names (locally) the tcp port 2306, which, I’m told) is required for the httpd daemon to use it under SELinux.<br><br>Again, thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843<br><br>> On Apr 15, 2022, at 06:05, Nathan Brindle <nathan@LSOFT.COM> wrote:<br>><br>> I don't know if this will fix your specific problem, but if the web pages are visible in the browser, and the problem is you can't execute anything that would require WA to talk to port 2306, you may need to run the following at the shell prompt:<br>><br>> sudo setsebool -P httpd_can_network_connect 1<br>><br>> You have to do this if the firewall is set to be restrictive/enforcing. So in order for httpd to communicate with LISTSERV, it has to be able to connect to the network. The default is to disallow this (0) so it must be set manually to 1.<br>><br>> If you later experience problems with WA writing to the "upload" directory, you may also need to execute<br>><br>> sudo semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/archives/upload'<br>> sudo restorecon -v '/var/www/html/archives/upload'<br>><br>> (change the path to the upload directory if it differs in your installation).<br>><br>> This is not to say there isn't something else going on in SELinux that needs to be modified, but that's usually the first thing to look at.<br>><br>> Note that in most cases I know of, there is no reason to allow external access to port 2306. As long as WA can talk to port 2306 locally, that's all that's strictly necessary.<br>><br>> I'll finish by saying I'm not an SELinux expert by any stretch of the imagination. Most of the above was discovered the hard way when I was building CentOS 7 sandbox machines in our cloud several years ago – lots of Googling and digging through the Linux documentation. So if the above doesn't work for you, I'm not sure what else I can say. It did work for me.<br>><br>> -----Original Message-----<br>> From: LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM> On Behalf Of Steven J Depinet<br>> Sent: Thursday, April 14, 2022 1:34 PM<br>> To: LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> Subject: SELinux (RHEL7) and port 2306 (Listserv V17.0)<br>><br>> Greetings,<br>><br>> I’m trying to upgrade the OS of my Listserv (V17.0) machine, and ran into issues with SELinux not liking was use of port 2306. A google search showed enough to determine that wa uses 2306 to communicate with Listserv, but that’s about all I got from that. The error I get is:<br>><br>> SELinux is preventing wa from name_connect access on the tcp_socket port 2306.<br>><br>> It goes on to suggest:<br>> If you want to allow wa to connect to network port 2306, Then you need to modify the port type.<br>><br>> Then provides the command:<br>> semanage port -a -t PORT_TYPE -p tcp 2306, where PORT_TYPE is one of the following: dns_port_t, dnssec_port_t, kerberos_port_t, ocsp_port_t<br>><br>> I note that the old machine is RHEL6, and uses iptables, whereas the new RHEL7 machine uses firewalld, but I do not see any iptables rules for port 2306 on the old machine, but it does not run selinux, either.<br>><br>> Any ideas? Do I need a firewalld rule allowing localhost to use port 2306, or do I follow the suggestion and modify the port type? If the latter, what type?<br>><br>> Thanks,<br>><br>> Steve dePinet Northern Arizona University<br>> Systems Programmer, Sr. Box 5100<br>> Information Technology Services Flagstaff, Az 86011<br>> Steve.dePinet@nau.edu (928) 523-6843<br>><br>><br>><br>><br>><br>> ############################<br>><br>> To unsubscribe from the LSTSRV-L list:<br>> write to: mailto:LSTSRV-L-SIGNOFF-REQUEST@PEACH.EASE.LSOFT.COM<br>> or click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>Nathan Brindle2022-04-15T13:05:44+00:002022-04-15T13:05:44+00:00Re: SELinux (RHEL7) and port 2306 (Listserv V17.0)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;873d00c5.2204I don't know if this will fix your specific problem, but if the web pages are visible in the browser, and the problem is you can't execute anything that would require WA to talk to port 2306, you may need to run the following at the shell prompt:<br><br>sudo setsebool -P httpd_can_network_connect 1<br><br>You have to do this if the firewall is set to be restrictive/enforcing. So in order for httpd to communicate with LISTSERV, it has to be able to connect to the network. The default is to disallow this (0) so it must be set manually to 1.<br><br>If you later experience problems with WA writing to the "upload" directory, you may also need to execute<br><br>sudo semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/archives/upload'<br>sudo restorecon -v '/var/www/html/archives/upload'<br><br>(change the path to the upload directory if it differs in your installation).<br><br>This is not to say there isn't something else going on in SELinux that needs to be modified, but that's usually the first thing to look at.<br><br>Note that in most cases I know of, there is no reason to allow external access to port 2306. As long as WA can talk to port 2306 locally, that's all that's strictly necessary.<br><br>I'll finish by saying I'm not an SELinux expert by any stretch of the imagination. Most of the above was discovered the hard way when I was building CentOS 7 sandbox machines in our cloud several years ago – lots of Googling and digging through the Linux documentation. So if the above doesn't work for you, I'm not sure what else I can say. It did work for me. [...]Steven J Depinet2022-04-14T17:33:31+00:002022-04-14T17:33:31+00:00SELinux (RHEL7) and port 2306 (Listserv V17.0)http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;e1603f6d.2204Greetings,<br><br>I’m trying to upgrade the OS of my Listserv (V17.0) machine, and ran into issues with SELinux not liking was use of port 2306. A google search showed enough to determine that wa uses 2306 to communicate with Listserv, but that’s about all I got from that. The error I get is:<br><br>SELinux is preventing wa from name_connect access on the tcp_socket port 2306.<br><br>It goes on to suggest:<br>If you want to allow wa to connect to network port 2306, Then you need to modify the port type.<br><br>Then provides the command:<br>semanage port -a -t PORT_TYPE -p tcp 2306, where PORT_TYPE is one of the following: dns_port_t, dnssec_port_t, kerberos_port_t, ocsp_port_t<br><br>I note that the old machine is RHEL6, and uses iptables, whereas the new RHEL7 machine uses firewalld, but I do not see any iptables rules for port 2306 on the old machine, but it does not run selinux, either.<br><br>Any ideas? Do I need a firewalld rule allowing localhost to use port 2306, or do I follow the suggestion and modify the port type? If the latter, what type?<br><br>Thanks,<br><br>Steve dePinet Northern Arizona University<br>Systems Programmer, Sr. Box 5100<br>Information Technology Services Flagstaff, Az 86011<br>Steve.dePinet@nau.edu (928) 523-6843Krista2022-04-13T15:31:52-04:002022-04-13T15:31:52-04:00Re: Possible to force DMAC From rewrite for specific domain?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;eed152dd.2204Actually I found the answer in an old listserv message:<br><br>DEBUG_DMARC_REWRITE<br>https://peach.ease.lsoft.com/scripts/wa-PEACH.exe?A3=1609&L=LSTSRV-L&E=quoted-printable&P=67574&B=--&T=text%2Fplain;%20charset=ISO-8859-1&header=1<br><br>I couldn't find where to set it in the GUI but it worked in the site.cfg file.<br><br>Krista<br><br>On Wed, Apr 13, 2022 at 2:13 PM Krista <klandon@gmail.com> wrote:<br><br>> We're having problems with O365 refusing routing messages to Junk if<br>> they're coming from our ListServ server on our Intranet. It looks like it<br>> would work if p=reject were set for the top domain (of which our server is<br>> a subdomain) but it's only set on their external DNS records, and not on<br>> the Internal DNS record, which the ListServ server looks at.<br>><br>> Is it possible to get the server to rewrite the From as if the p=reject<br>> were set for that specific domain? I know it's usually an automatic<br>> process but we need to require it manually (I don't think I'd be<br>> successful in getting them to add the DMARC p=reject to the internal DNS<br>> record).<br>><br>> Krista Landon<br>>Krista2022-04-13T14:13:08-04:002022-04-13T14:13:08-04:00Possible to force DMAC From rewrite for specific domain?http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;7f54bce.2204We're having problems with O365 refusing routing messages to Junk if<br>they're coming from our ListServ server on our Intranet. It looks like it<br>would work if p=reject were set for the top domain (of which our server is<br>a subdomain) but it's only set on their external DNS records, and not on<br>the Internal DNS record, which the ListServ server looks at.<br><br>Is it possible to get the server to rewrite the From as if the p=reject<br>were set for that specific domain? I know it's usually an automatic<br>process but we need to require it manually (I don't think I'd be<br>successful in getting them to add the DMARC p=reject to the internal DNS<br>record).<br><br>Krista LandonKrista2022-04-04T14:47:40-04:002022-04-04T14:47:40-04:00Re: Using ListServ with O365http://community.emailogy.com/scripts/wa-community.exe?A2=LSTSRV-L;4fc9862.2204Thank you! I'm running that past the exchange administrator. If it's a<br>single NAT IP, that would be an easy fix. I believe strongly in Murphy's<br>law though ;)<br><br>On Mon, Apr 4, 2022 at 2:29 PM Irons, Joseph R <Joe.Irons@cuchicago.edu><br>wrote:<br><br>> “…one or more of the Hybrid exchange servers before it is routed via a<br>> nated IP to Microsoft production servers…”<br>><br>><br>><br>> This is the IP you need to add to your listserv SPF. You are routing all<br>> email for your primary domain through your hybrid exchange servers to get<br>> to O365 which is why listserv messages for your domain are showing that<br>> address. If your multiple exchange servers are not all NATing to the same<br>> address then you’ll need to add each of their external addresses to<br>> listserv’s SPF.<br>><br>><br>><br>> Joe<br>><br>><br>><br>> *From:* LISTSERV Site Administrators' Forum <LSTSRV-L@PEACH.EASE.LSOFT.COM><br>> *On Behalf Of *Krista<br>> *Sent:* Monday, April 4, 2022 12:47 PM<br>> *To:* LSTSRV-L@PEACH.EASE.LSOFT.COM<br>> *Subject:* Re: Using ListServ with O365<br>><br>><br>><br>> I did. The ListServ is on a subdomain. I pointed to include:<br>> spf.protection.outlook.com. He said:<br>> "that is what we have for our (topleveldomain) SPF records, but the IP<br>> records contained in the spf.protection.outlook.com records do not<br>> contain the Microsoft production servers."<br>><br>> It doesn't seem like it should be this difficult...<br>> But maybe this is why Lsoft wrote the article with this as a potential<br>> solution:<br>> " The solution is to use the Microsoft SMTPSVC mailer on the LISTSERV<br>> machine in a slightly different manner than described above and let SMTPSVC<br>> do the necessary authentication so that the email will be accepted by the<br>> Exchange Online server and forwarded on to wherever it needs to go."<br>><br>> Krista Landon<br>><br>><br>><br>> On Mon, Apr 4, 2022 at 1:33 PM Ricardo Stella <stella@rider.edu> wrote:<br>><br>><br>><br>> Sends this to your admin?<br>><br>><br>><br>><br>> https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-spf-in-office-365-to-help-prevent-spoofing?view=o365-worldwide<br>><br>><br>><br>> On Mon, Apr 4, 2022 at 1:26 PM Krista <klandon@gmail.com> wrote:<br>><br>> The admin tells me:<br>> "As to fix the SPF signature and alignment settings we will need to add<br>> all Microsoft production server IPs ( because this will keep changing ).<br>> And Microsoft will not make that list available to us."<br>><br>> "It is going to multiple MTAs (Message transport agents). In this case it<br>> will start with the SMTP relay server which will forward the message to one<br>> or more of the Hybrid exchange servers before it is routed via a nated IP<br>> to Microsoft production servers where is will be inspected by EOP"<br>><br>><br>><br>> On Mon, Apr 4, 2022 at 1:10 PM Sunil Chauhan <sunilkms@gmail.com> wrote:<br>><br>> The server which talking to eop should be on the spf.<br>><br>><br>><br>> If you listserv directly sending to eop, then the connecting up should be<br>> on spf. Or route via the mailrelay which I believe would be already on spf.<br>><br>><br>><br>> On Mon, 4 Apr, 2022, 10:11 PM Krista, <klandon@gmail.com> wrote:<br>><br>> Is this article still the most current on how to get ListServ to work with<br>> O365 and not have messages being sent go into Junk?<br>><br>> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp<br>><br>> Our ListServ is running on Windows and is on the Intranet of our<br>> organization, which has switched to using O365 for email. We currently use<br>> an SMTP relay. Messages that go to external addresses are fine, as the<br>> ListServ's domain has an SPF record that contains the ESAs, but if a<br>> message comes From the organization's main domain, from O365 to the<br>> ListServ, and the subscribers have a mailbox on the org's main domain (in<br>> O365), the messages takes a direct route to the microsoft production server<br>> and EOP, so the SPF check fails, and ironically internal mail, going to the<br>> listserv, then sent back to internal mail, gets tossed into subscriber's<br>> junk folders.<br>><br>> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just<br>> going based on what our engineer is telling me.<br>><br>><br>><br>> If anyone has more up to date suggestions on how to work with O365 (cloud)<br>> from an internal ListServ, please let me know.<br>><br>><br>><br>> Krista Landon<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>><br>><br>> --<br>><br>> °(((*=*((*===°°°*(((*================================================*<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>><br>> ------------------------------<br>><br>> To unsubscribe from the LSTSRV-L list, click the following link:<br>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1<br>>