We 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.

If nothing else, have the spam filters check SPF to prevent spoofing and skip any rules based detection.

Hi William,

Thank you for replying to my question.

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.

Best,

Shinn

See the CONTENT_FILTER template described in the LISTSERV documentation. Probably will help.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Shinn Wu
Sent: Thursday, March 09, 2023 1:11 PM
To: [log in to unmask]
Subject: Re: Block key words?

Hi William,

Thank you for replying to my question.

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.

Best,

Shinn

Thank you so much, it worked!

> What would cause this error in a Digest message but not in the an individual post to a List?
>
> [Message contains invalid MIME fields or encoding and could not be processed]
>
> Krista Landon

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.)

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.

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.

Thanks,
jwgh

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.

Is it possible to turn off the digest option for a ListServ / convert all
existing subscribers to "Regular"?
Or is it perhaps possible to make the digest go out HTML email synopsis?

Krista

On Mon, Jan 30, 2023 at 4:09 PM Jacob Haller <[log in to unmask]> wrote:

> > What would cause this error in a Digest message but not in the an
> individual post to a List?
> >
> > [Message contains invalid MIME fields or encoding and could not be
> processed]
> >
> > Krista Landon
>
> 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.)
>
> 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.
>
> 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.
>
> Thanks,
> jwgh
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

On Jan 30, 2023, at 4:11 PM, Krista <[log in to unmask]> wrote:

> 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.
>
> Is it possible to turn off the digest option for a ListServ / convert all existing subscribers to "Regular"?
> Or is it perhaps possible to make the digest go out HTML email synopsis?

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.

You can also make the default digest type be either HTML or MIME via

Default-Options= HTML

or

Default-Options= MIME

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.

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

QUIET SET nameoflist MIME FOR *@*

command under ‘List Management’/‘LISTSERV Command’, replacing ‘nameoflist’ with the name of the mailing list.

-jwgh

Thank you! I think the short term fix will be to set Digest= No on the
configuration (I assume that'll work for current subscribers who have their
preference set to digest too) and then consider the other options for
future.

Krista

On Mon, Jan 30, 2023 at 4:25 PM Jacob Haller <[log in to unmask]> wrote:

> On Jan 30, 2023, at 4:11 PM, Krista <[log in to unmask]> wrote:
>
> 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.
>
> Is it possible to turn off the digest option for a ListServ / convert all
> existing subscribers to "Regular"?
> Or is it perhaps possible to make the digest go out HTML email synopsis?
>
>
> 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.
>
> You can also make the default digest type be either HTML or MIME via
>
> Default-Options= HTML
>
>
> or
>
> Default-Options= MIME
>
>
> 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.
>
> 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
>
> QUIET SET nameoflist MIME FOR *@*
>
>
> command under ‘List Management’/‘LISTSERV Command’, replacing ‘nameoflist’
> with the name of the mailing list.
>
> -jwgh
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

On Oct 7, 2022, at 11:30 AM, Steven J Depinet <[log in to unmask]> wrote:

> Greetings All,
>
> 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.
>
> 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?

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.

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:

https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html <https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html>

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.) 

[More ...]

Thanks 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.

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Oct 7, 2022, at 9:22 AM, Jacob Haller <[log in to unmask]> wrote:
>
> On Oct 7, 2022, at 11:30 AM, Steven J Depinet <[log in to unmask]> wrote:
>
>> Greetings All,
>>
>> 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.
>>
>> 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?
>
> 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.
>
> 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:
>
> https://www.lsoft.com/manuals/owner-faq/19CanIstoppeoplefromunsubscribin.html
>
> 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.)
>
> -jwgh
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Hi Steve,

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:

"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.

You have to issue a "unlock <listname>" in the command box to be able to edit the list again.

Hope this helps.

Kind regards,

Joost de Groot

Hi Steve,

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:

"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."

To unlock the list you have to send "unlock <listname>" in the command box.

Hope this helps,

Kind regards,

Joost de Groot

-----Original Message-----
From: Steven J Depinet <[log in to unmask]>
Sent: vrijdag 7 oktober 2022 17:30
Subject: Subcription= keyword

Greetings All,

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.

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?

Thanks,

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

Hi,

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.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Groot, Joost de (UT-LISA)
Sent: Monday, October 10, 2022 3:55 AM
To: [log in to unmask]
Subject: [LSTSRV-L] FW: Subcription= keyword

Hi Steve,

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:

"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."

To unlock the list you have to send "unlock <listname>" in the command box.

Hope this helps,

Kind regards,

Joost de Groot

-----Original Message-----
From: Steven J Depinet <[log in to unmask]>
Sent: vrijdag 7 oktober 2022 17:30
Subject: Subcription= keyword

Greetings All,

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. 

[More ...]

Melissa,

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...

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Oct 12, 2022, at 12:29 PM, Kenny, Melissa S. <[log in to unmask]> wrote:
>
> Hi,
>
> 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.
>
> Melissa Kenny
>
> Web Administrator
> Harvard Medical School IT
>
> 401 Park Drive
> Suite 504 West
> Boston, MA 02215
>
>
>
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Groot, Joost de (UT-LISA)
> Sent: Monday, October 10, 2022 3:55 AM
> To: [log in to unmask]
> Subject: [LSTSRV-L] FW: Subcription= keyword
>
> Hi Steve,
>
> 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:
>
> "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."
>
> To unlock the list you have to send "unlock <listname>" in the command box.
>
> Hope this helps,
>
> Kind regards,
>
> Joost de Groot
>
> -----Original Message-----
> From: Steven J Depinet <[log in to unmask]>
> Sent: vrijdag 7 oktober 2022 17:30
> Subject: Subcription= keyword
>
> Greetings All,
>
> 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.
>
> 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?
>
> Thanks,
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

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.

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”.

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...

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?

TIA,

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Oct 12, 2022, at 12:29 PM, Kenny, Melissa S. <[log in to unmask]> wrote:
>
> Hi,
>
> 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.
>
> Melissa Kenny
>
> Web Administrator
> Harvard Medical School IT
>
> 401 Park Drive
> Suite 504 West
> Boston, MA 02215
>
>
>
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Groot, Joost de (UT-LISA)
> Sent: Monday, October 10, 2022 3:55 AM
> To: [log in to unmask]
> Subject: [LSTSRV-L] FW: Subcription= keyword
>
> Hi Steve,
>
> 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:
>
> "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."
>
> To unlock the list you have to send "unlock <listname>" in the command box.
>
> Hope this helps,
>
> Kind regards,
>
> Joost de Groot
>
> -----Original Message-----
> From: Steven J Depinet <[log in to unmask]>
> Sent: vrijdag 7 oktober 2022 17:30
> Subject: Subcription= keyword
>
> Greetings All,
>
> 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.
>
> 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?
>
> Thanks,
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

On Oct 13, 2022, at 11:45 AM, Steven J Depinet <[log in to unmask]> wrote:

> 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.
>
> 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”.
>
> 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...

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.

> 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?

Right. If a user leaves a list, wa.exe communicates this to LISTSERV by sending a SIGNOFF command.

Thanks,
jwgh

Great!

Thanks,

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Oct 13, 2022, at 8:55 AM, Jacob Haller <[log in to unmask]> wrote:
>
>
>
> On Oct 13, 2022, at 11:45 AM, Steven J Depinet <[log in to unmask]> wrote:
>
>> 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.
>>
>> 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”.
>>
>> 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...
>
> 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.
>
>> 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?
>
> Right. If a user leaves a list, wa.exe communicates this to LISTSERV by sending a SIGNOFF command.
>
> Thanks,
> jwgh
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Your exchange system is probably rejecting emails due to the configured threshold for available disk space ?

So your exchange person can’t do a web search ?

Have them check the queuers and Transport Logs.

Rob Murray

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jon Schwendemann
Sent: September 15, 2022 3:37 PM
To: [log in to unmask]
Subject: listserv error

⚠External message: Use caution.
I am receiving an error in my listserv, that seems to indicate it is an exchange issue.
Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])

I am running on rhel 7.9, with listserv 16.5
Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.

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.
Thanks

Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?

-jwgh

> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <[log in to unmask]> wrote:
>
> I am receiving an error in my listserv, that seems to indicate it is an exchange issue.
> Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])
>
> I am running on rhel 7.9, with listserv 16.5
> Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.
>
> 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.
> Thanks

It shows under the listserv.log.
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.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jacob Haller
Sent: Thursday, September 15, 2022 2:04 PM
To: [log in to unmask]
Subject: Re: listserv error

Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?

-jwgh

On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <[log in to unmask]<mailto:[log in to unmask]>> wrote:

I am receiving an error in my listserv, that seems to indicate it is an exchange issue.
Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])

I am running on rhel 7.9, with listserv 16.5
Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.

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.
Thanks

On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <[log in to unmask]> wrote:

> It shows under the listserv.log.
> 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.

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.)

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.

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.

Thanks,
Jacob Haller

> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jacob Haller
> Sent: Thursday, September 15, 2022 2:04 PM
> To: [log in to unmask]
> Subject: Re: listserv error
>
> Where is the error showing up? In an email, in the LISTSERV log, or elsewhere?
>
> -jwgh
>
>
> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>
> I am receiving an error in my listserv, that seems to indicate it is an exchange issue.
> Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])
>
> I am running on rhel 7.9, with listserv 16.5
> Now, of course I could upgrade listserv, but it was doing fine till just the last couple weeks, when this message cropped up.
>
> 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.
> Thanks

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.

But the SMTP server admin really needs to check drive space, IMO.

Krista Landon

On Thu, Sep 15, 2022 at 4:47 PM Jacob Haller <[log in to unmask]> wrote:

>
>
> On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <[log in to unmask]> wrote:
>
> It shows under the listserv.log.
> 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.
>
>
> 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.)
>
> 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.
>
> 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.
>
> Thanks,
> Jacob Haller
>
> *From:* LISTSERV Site Administrators' Forum <[log in to unmask]
> > *On Behalf Of *Jacob Haller
> *Sent:* Thursday, September 15, 2022 2:04 PM
> *To:* [log in to unmask]
> *Subject:* Re: listserv error
>
> Where is the error showing up? In an email, in the LISTSERV log, or
> elsewhere?
>
> -jwgh
>
>
> On Sep 15, 2022, at 2:36 PM, Jon Schwendemann <[log in to unmask]> wrote:
>
> I am receiving an error in my listserv, that seems to indicate it is an
> exchange issue.
> Insufficient system resources (UsedDiskSpace[C:\Program
> Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])
>
> I am running on rhel 7.9, with listserv 16.5
> Now, of course I could upgrade listserv, but it was doing fine till just
> the last couple weeks, when this message cropped up.
>
> 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.
> Thanks
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

My 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.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Krista
Sent: Thursday, September 15, 2022 4:54 PM
To: [log in to unmask]
Subject: Re: listserv error

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.

But the SMTP server admin really needs to check drive space, IMO.

Krista Landon

On Thu, Sep 15, 2022 at 4:47 PM Jacob Haller <[log in to unmask]<mailto:[log in to unmask]>> wrote:

On Sep 15, 2022, at 3:59 PM, Jon Schwendemann <[log in to unmask]<mailto:[log in to unmask]>> wrote:

It shows under the listserv.log.
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.

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.) 

[More ...]

On Thu, 15 Sep 2022 18:36:59 +0000, Jon Schwendemann <[log in to unmask]>
wrote:

>Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])

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.

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.

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).

Take your largest list #rcpts and your largest message (from any list),
multiply that and then multiply that answer X3. that's how much free disk
space you need in the mailer queue (Exchange in this case) to handle
surprise large mailings through LISTSERV along with other traffic.

This may be of use to your Exchange admin, and aligns with Ben Parker's suggestion.
https://docs.microsoft.com/en-us/answers/questions/649462/exchange-2016-insufficient-system-storage.html

James
(Ex admin of Exchange 2003).

Well, 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.

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Ben Parker
Sent: Friday, September 16, 2022 1:41 AM
To: [log in to unmask]
Subject: Re: listserv error

On Thu, 15 Sep 2022 18:36:59 +0000, Jon Schwendemann <[log in to unmask]>
wrote:

>Insufficient system resources (UsedDiskSpace[C:\Program
>Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue])

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.

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.

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). 

[More ...]

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

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jon Schwendemann
Sent: Friday, September 09, 2022 3:22 PM
To: [log in to unmask]
Subject: file validities

I have a question on some files I found in the listserv/home directory.
Peers.namesum
Permvars.file
Bitearn.nodes

Seems to me, if these are legit, they could perhaps be named better.

Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Nathan Brindle
Sent: Friday, September 9, 2022 2:28 PM
To: [log in to unmask]
Subject: Re: file validities

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

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Jon Schwendemann
Sent: Friday, September 09, 2022 3:22 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: file validities

I have a question on some files I found in the listserv/home directory.
Peers.namesum
Permvars.file
Bitearn.nodes

Seems to me, if these are legit, they could perhaps be named better.

Bitearn comes from:

Bitnet - because it’s time network
EARN - European Applied Research Network

—
Thomas Kern
Phone: 301-905-6427
Thomas.Kern@hq,doe.gov

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).

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.

PERMVARS FILE is LISTSERV's working cache, and you absolutely do not want to fiddle with it or you will break things.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jon Schwendemann
Sent: Friday, September 09, 2022 3:35 PM
To: [log in to unmask]
Subject: Re: file validities

Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Nathan Brindle
Sent: Friday, September 9, 2022 2:28 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: file validities

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

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Jon Schwendemann
Sent: Friday, September 09, 2022 3:22 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: file validities

I have a question on some files I found in the listserv/home directory.
Peers.namesum
Permvars.file
Bitearn.nodes 

[More ...]

Can't say I do. I've only been working with listserv for about 6 years, and never used anything of that stuff.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Nathan Brindle
Sent: Friday, September 9, 2022 2:46 PM
To: [log in to unmask]
Subject: Re: file validities

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).

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.

PERMVARS FILE is LISTSERV's working cache, and you absolutely do not want to fiddle with it or you will break things.

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Jon Schwendemann
Sent: Friday, September 09, 2022 3:35 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: file validities

Well, alrighty then. The first 2, I thought might be ok. But bitearn really sounds like something used for cryptomining.

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Nathan Brindle
Sent: Friday, September 9, 2022 2:28 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: file validities

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. 

[More ...]

1. 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.)

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.

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. 

[More ...]

HTML 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).

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.

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.

Nathan

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of deb cady
Sent: Friday, August 19, 2022 11:27 PM
To: [log in to unmask]
Subject: HTML DIgests will they ever be functional?

Given the information in the List Admin manual that: 

[More ...]

I 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?

Thanks,
Ari

On Thu, 11 Aug 2022 10:38:45 -0400, Ari Rabinowitz <[log in to unmask]>
wrote:

>Specifically which should we edit, ~listserv/go.user or ~listserv/home/sitecfg.file?

You should only edit ~listserv/go.user. It is not safe to edit
~listserv/home/sitecfg.file as this file is maintained by LISTSERV and has a
specific format which is not documented and which you may not understand.

>Also confusing to me is what happens if I make changes in the Web GUI. Which file(s) does that update?

Changes via the www interface go into ~listserv/home/sitecfg.file but since
LISTSERV is writing that file it knows how to do it correctly.

In all cases (changes via go.user or via www interface) you must restart the
LISTSERV process for the changes to take effect. If you make changes via
the www interface there is a handy 'button' you can click on to do this. If
you edit go.user, then you need to restart from the command line.

Also, when editing string variables in go.user don't forget to 'export' that
variable name.

No abstract is available available for this message. [Read Message ...]

Thanks Peter, I'll give it a whirl.

Glenn

[image: UMSIT:SDS Logo]
Glenn R. Eichel
*SSA*
*UMSIT - Service Delivery and Support*
*Lecturer*
*UMaine Department of Sociology*
207-581-4631
201-H Fernald Hall
Orono, Maine 04469
[log in to unmask]

On Wed, Aug 3, 2022 at 1:35 PM Peter M. Weiss <[log in to unmask]> wrote:

> My guess:
>
> INDEX listname
>
> edit and GET all files
>
> save each filename in the new archives with the new fn.
>
> Re-index as appropriate.
>
> Or some listserv admin can probably do some scripting.
>
> Update all of the template, welcome / farewall, and other docs to reflect
> the changes.
>
>
> On 8/3/2022 12:46, Glenn Eichel wrote:
>
> Greetings from wonderful Maine.
>
> Our school of business maintains 5 or so lists on our server. A new
> primary owner has taken over and wants new names to reflect a formal name
> change of the school. Normal practice is to clone the existing list with a
> new name. However, several of their lists have extensive log and notebook
> files that they would like to save. What do you do in this situation?
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

I’d recommend the following:

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

REINDEX BOTH IMMEDIATE listname

(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.)

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.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Glenn Eichel
Sent: Wednesday, August 03, 2022 2:00 PM
To: [log in to unmask]
Subject: Re: Moving list Archives

Thanks Peter, I'll give it a whirl.

Glenn

[Image removed by sender. UMSIT:SDS Logo]

Glenn R. Eichel

SSA

UMSIT - Service Delivery and Support
Lecturer
UMaine Department of Sociology

207-581-4631

201-H Fernald Hall

Orono, Maine 04469

[log in to unmask]<mailto:[log in to unmask]>

On Wed, Aug 3, 2022 at 1:35 PM Peter M. Weiss <[log in to unmask]<mailto:[log in to unmask]>> wrote:
My guess:

INDEX listname

edit and GET all files

save each filename in the new archives with the new fn.

Re-index as appropriate.

Or some listserv admin can probably do some scripting.

Update all of the template, welcome / farewall, and other docs to reflect the changes.

On 8/3/2022 12:46, Glenn Eichel wrote:
Greetings from wonderful Maine. 

[More ...]

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.

Steven J Depinet Systems Administrator, Sr.
[log in to unmask] Technology Services
(928) 523-6843Northern Arizona University

> On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
>
> Greetings,
>
> 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…”.
>
> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
>
> 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?
>
> Thanks,
>
> Steve dePinetNorthern Arizona University
> Systems Programmer, Sr.Box 5100
> Information Technology ServicesFlagstaff, Az 86011
> [log in to unmask](928) 523-6843
>
>
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

Did you see this note about attachments?
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. 

Did you look at the original headers of the sent mail?  Perhaps that's where the problem lies.
Alternatively there are a large number of possible attachemnt types so, for security sake, you may want to limit to be safe.
We use 17.0 and the attachments woorks just fine - so could be a local email admin decision.

Deb

On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <[log in to unmask]> wrote:

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.

Steven J Depinet Systems Administrator, Sr.
[log in to unmask] Technology Services
(928) 523-6843Northern Arizona University

> On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
>
> Greetings,
>
> 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…”.
>
> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
>
> 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?
>
> Thanks,
>
> Steve dePinetNorthern Arizona University
> Systems Programmer, Sr.Box 5100
> Information Technology ServicesFlagstaff, Az 86011
> [log in to unmask](928) 523-6843
>
>
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

Also have you checked sizelimit?  Maybe the attachemnts are too big?
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".

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.

Deb

On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <[log in to unmask]> wrote:

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.

Steven J Depinet Systems Administrator, Sr.
[log in to unmask] Technology Services
(928) 523-6843Northern Arizona University

> On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
>
> Greetings,
>
> 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…”.
>
> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
>
> 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?
>
> Thanks,
>
> Steve dePinetNorthern Arizona University
> Systems Programmer, Sr.Box 5100
> Information Technology ServicesFlagstaff, Az 86011
> [log in to unmask](928) 523-6843
>
>
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

> On Aug 2, 2022, at 5:32 PM, Steven J Depinet <[log in to unmask]> wrote:
>
> 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.

My guess is that

Misc-Options= KEEP_EXCHANGE_DATA

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).

See this tech tip:

https://www.lsoft.com/news/techtipLSV-issue5-2017.asp <https://www.lsoft.com/news/techtipLSV-issue5-2017.asp>

for additional information about this setting and ‘Attachments= All’.

-jwgh

Yes, 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.

Looking at the message headers, I see:

Content-Type: multipart/mixed; boundary="_004_03a236a56b7f4e009ab542af454d6b06nauedu_"
Content-Language: en-US

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.

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Aug 2, 2022, at 15:42, deb cady <[log in to unmask]> wrote:
>
> Did you see this note about attachments?
>
> 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.
>
> Did you look at the original headers of the sent mail? Perhaps that's where the problem lies.
>
> Alternatively there are a large number of possible attachemnt types so, for security sake, you may want to limit to be safe.
>
> We use 17.0 and the attachments woorks just fine - so could be a local email admin decision.
>
>
> Deb
>
>
> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <[log in to unmask]> wrote:
>
>
> 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.
>
>
>
> Steven J Depinet Systems Administrator, Sr.
> [log in to unmask] Technology Services
> (928) 523-6843Northern Arizona University
>
>
>
>
> > On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
> >
> > Greetings,
> >
> > 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…”.
> >
> > For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
> >
> > 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?
> >
> > Thanks,
> >
> > Steve dePinetNorthern Arizona University
> > Systems Programmer, Sr.Box 5100
> > Information Technology ServicesFlagstaff, Az 86011
> > [log in to unmask](928) 523-6843
> >
> >
> >
> >
> >
> > ############################
> >
> > To unsubscribe from the LSTSRV-L list:
> > write to: mailto:[log in to unmask]
> > or click the following link:
> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

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.

BREAKING NEWS!

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.

FYI: https://docs.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion?view=exchserver-2019

talks about TNEF...

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Aug 2, 2022, at 15:45, deb cady <[log in to unmask]> wrote:
>
> Also have you checked sizelimit? Maybe the attachemnts are too big?
>
> 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".
>
> 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.
>
> Deb
>
>
> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <[log in to unmask]> wrote:
>
>
> 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.
>
> Steven J Depinet Systems Administrator, Sr.
> [log in to unmask] Technology Services
> (928) 523-6843Northern Arizona University
>
>
>
>
> > On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
> >
> > Greetings,
> >
> > 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…”.
> >
> > For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
> >
> > 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?
> >
> > Thanks,
> >
> > Steve dePinetNorthern Arizona University
> > Systems Programmer, Sr.Box 5100
> > Information Technology ServicesFlagstaff, Az 86011
> > [log in to unmask](928) 523-6843
> >
> >
> >
> >
> >
> > ############################
> >
> > To unsubscribe from the LSTSRV-L list:
> > write to: mailto:[log in to unmask]
> > or click the following link:
> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Update:

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”...

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.

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Aug 3, 2022, at 10:27, Steven J Depinet <[log in to unmask]> wrote:
>
> 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.
>
> BREAKING NEWS!
>
> 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.
>
> FYI: https://docs.microsoft.com/en-us/exchange/mail-flow/content-conversion/tnef-conversion?view=exchserver-2019
>
> talks about TNEF...
>
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
>
>
>
>> On Aug 2, 2022, at 15:45, deb cady <[log in to unmask]> wrote:
>>
>> Also have you checked sizelimit? Maybe the attachemnts are too big?
>>
>> 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".
>>
>> 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.
>>
>> Deb
>>
>>
>> On Tuesday, 2 August 2022 at 02:33:15 pm GMT-7, Steven J Depinet <[log in to unmask]> wrote:
>>
>>
>> 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.
>>
>> Steven J Depinet Systems Administrator, Sr.
>> [log in to unmask] Technology Services
>> (928) 523-6843Northern Arizona University
>>
>>
>>
>>
>>> On Aug 2, 2022, at 08:38, Steven J Depinet <[log in to unmask]> wrote:
>>>
>>> Greetings,
>>>
>>> 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…”.
>>>
>>> For the same list that i tried “Attachments=yes”, I tried “Attachments=all”, but haven’t heard what effect that has yet.
>>>
>>> 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?
>>>
>>> Thanks,
>>>
>>> Steve dePinetNorthern Arizona University
>>> Systems Programmer, Sr.Box 5100
>>> Information Technology ServicesFlagstaff, Az 86011
>>> [log in to unmask](928) 523-6843
>>>
>>>
>>>
>>>
>>>
>>> ############################
>>>
>>> To unsubscribe from the LSTSRV-L list:
>>> write to: mailto:[log in to unmask]
>>> or click the following link:
>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>>
>>
>> ############################
>>
>> To unsubscribe from the LSTSRV-L list:
>> write to: mailto:[log in to unmask]
>> or click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

That 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!

James
former Exchange admin
LISTSERV LITE Site Owner

The 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?

Is the address in questions actually subscribed to the mailing list?

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.

-jwgh

On Jul 16, 2022, at 9:13 AM, Peter M. Weiss <[log in to unmask]> wrote:

> 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.
>
> That particular email address is also a QUIET: owner and does NOT receive list's admin messages (errors, moderation).
>
> Thoughts? e.g., listserv Peer backbone?
>
> 1 07/11 07/11 <[suppressed]@GMAIL.COM> <mailto:[log in to unmask]>
> Last error: 5.7.25 550-5.7.25 [74.220.200.20] The IP address
> sending this message does not have a 550-5.7.25 PTR
> record setup, or the corresponding forward DNS
> entry does not 550-5.7.25 point to the sending IP.
> As a policy, Gmail does not accept messages
> 550-5.7.25 from IPs with missing PTR records.
> Please visi... (165 bytes suppressed)
>
> 1 07/15 07/15 <[suppressed]@GMAIL.COM> <mailto:[log in to unmask]>
> Last error: 5.7.25 550-5.7.25 [67.20.84.70] The IP address
> sending this message does not have a PTR 550-5.7.25
> record setup, or the corresponding forward DNS
> entry does not point 550-5.7.25 to the sending IP.
> As a policy, Gmail does not accept messages from
> 550-5.7.25 IPs with missing PTR records. Please
> visit ... (165 bytes suppressed)
> --
>
> Pete <https://www.llrx.com/author/pete-weiss/>
> Sr. Systems Configurator, emeritus
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

No abstract is available available for this message. [Read Message ...]

No abstract is available available for this message. [Read Message ...]

On Jul 5, 2022, at 8:25 AM, Peter M. Weiss <[log in to unmask]> wrote:

> insert listname:
>
> https://lists.psu.edu/cgi-bin/wa?MOD= <https://lists.psu.edu/cgi-bin/wa?MOD=>listname

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.

-jwgh

Hello Peter and Jacob,

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).

[cid:b1765892-606b-41c9-9a46-88f02094d0f4]

Thank you and good to know the command.

Shinn

Use the ‘All Moderators’ option and you should see all messages awaiting moderation or confirmation.

-jwgh

> On Jul 5, 2022, at 10:12 AM, Shinn Wu <[log in to unmask]> wrote:
>
> Hello Peter and Jacob,
>
> 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).
>
> <image.png>
>
> Thank you and good to know the command.
>
> Shinn
> From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Jacob Haller <[log in to unmask]>
> Sent: Tuesday, July 5, 2022 7:03 AM
> To: [log in to unmask] <[log in to unmask]>
> Subject: Re: OK Confirmation
>
> On Jul 5, 2022, at 8:25 AM, Peter M. Weiss <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>
>> insert listname:
>>
>> https://lists.psu.edu/cgi-bin/wa?MOD= <https://lists.psu.edu/cgi-bin/wa?MOD=>listname
>
> 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.
>
> -jwgh
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

Thank Jacob, I am sure that the cookies expired after 48 hours from Friday noon because I did not see the ss-staff.ok*.

Shinn

How many workers do you have set? I'm on 16.5 so things might be a bit
different but we set up 4 worker processes and have I only set out 50 at a
time.

On Mon, Jun 27, 2022, 12:02 AM Orrell, Justin <
[log in to unmask]> wrote:

> 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.
>
>
>
> 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?
>
>
>
> Thanks,
>
>
>
> Justin
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

On Jun 26, 2022, at 6:57 PM, Orrell, Justin <[log in to unmask]> wrote:

> 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.
>
> 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?

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:

27 Jun 2022 08:11:16 Processing file 5023707 from [log in to unmask]
27 Jun 2022 08:11:16 Processing mail from [log in to unmask] for TEST-L
DMARC(EXAMPLE.COM)> v=DMARC1; p=none;
27 Jun 2022 08:11:16 Distributing mail ("TEST-L") from owner-TEST-L@LISTS.EXAMPLE.COM...


[More ...]
27 Jun 2022 08:15:08 Enqueued for background delivery, ID=N-33F39B0A
27 Jun 2022 08:15:08 Done - 2 outbound file (1500 rcpts).
27 Jun 2022 08:15:08 Message DISTRIBUTEd to 1500 recipients.

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:

27 Jun 2022 08:01:16 Processing file 5023707 from [log in to unmask]
27 Jun 2022 08:01:16 -> Inserting top/bottom banners...
-> Not a subscriber, will process in 10 minutes.

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> . 

[More ...]

Instead of using Amazon SES as your Listserv email gateway why not route
the traffic to your domain gateway SMTP server to handle the outbound
traffic. I noticed that your email is primary host is Microsoft Outlook.
They might have a service similar to Google SMTP Gateway to support your
domain SMTP traffic.
Our Listserv is hosted on Amazon AWS and forwarded all outbound emails to
our Google SMTP gateway successfully for many years now.

Regards,
Nick
IEEE

On Tue, Jun 14, 2022 at 9:14 AM Richter, Andy <
[log in to unmask]> wrote:

> We 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.
>
>
>
> [image: Vanderbilt]
>
>
>
> *Andy Richter*
> Senior System Administrator, Hosting Services
> Information Technology | Vanderbilt University
> 615.343.4518 | [log in to unmask]
>
>
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

…Almost identical issue here too:

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.

Thanks,
Eli Phelps

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

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Phelps, Eli Jackson
Sent: Tuesday, June 14, 2022 8:45 AM
To: [log in to unmask]
Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)

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.
…Almost identical issue here too:

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.

Thanks,
Eli Phelps

I appreciate all of the feedback. We eventually get Amazon SES to work by adding the following line to sitecfg.file.
DEBUG_DMARC_REWRITE *
This feature uses DMARC functionality to rewrite the "From" address on every message passing through LISTSERV so that all messages sent "From" [log in to unmask]
This has the desired result of all email flowing and being delivered properly.

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.
Somehow the confluence of these two changes has resulted in one our list owners seeing the following.

[cid:image001.png@01D89DA9.7B4F5460]

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?

Andy

[Vanderbilt]

Andy Richter
Senior System Administrator, Hosting Services
Information Technology | Vanderbilt University
615.343.4518 | [log in to unmask]<mailto:[log in to unmask]>

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Barth, Michael
Sent: Tuesday, June 14, 2022 8:58 AM
To: [log in to unmask]
Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES)

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

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Phelps, Eli Jackson
Sent: Tuesday, June 14, 2022 8:45 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: configuring LISTSERV to work with Amazon Simple Email Service (SES) 

[More ...]

The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.

http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html

Nathan

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Steven J Depinet
Sent: Monday, April 18, 2022 1:40 PM
To: [log in to unmask]
Subject: Broken list archive after copy from old system

Greetings,

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:

An error occurred while logging mail to the archives of the BUSLIB-L list.
An incomplete copy of the message might be present in the archive file. The
list is being held to prevent further occurrences of this error. Please take
corrective action and issue a "FREE BUSLIB-L" command when you want the
message to be reprocessed.

Serious error occurred - traceback follows

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
file. Encrypted, so I can’t modify it without using a Listserv utility, if it exists.

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.

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Apr 18, 2022, at 10:49, Nathan Brindle <[log in to unmask]> wrote:
>
> The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.
>
> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html
>
> Nathan
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Steven J Depinet
> Sent: Monday, April 18, 2022 1:40 PM
> To: [log in to unmask]
> Subject: Broken list archive after copy from old system
>
> Greetings,
>
> 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:
>
> An error occurred while logging mail to the archives of the BUSLIB-L list.
> An incomplete copy of the message might be present in the archive file. The
> list is being held to prevent further occurrences of this error. Please take
> corrective action and issue a "FREE BUSLIB-L" command when you want the
> message to be reprocessed.
>
> Serious error occurred - traceback follows
> ------------------------------------------
>>>> Error X'00000011' opening file /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<
> -> Severity: Warning
> -> Facility: Generic error codes
> -> Abstract: File/major entity not found
> -> I/O mode: Record write
>>>> Error X'00000011' logging message to archives <<<
> -> Severity: Warning
> -> Facility: Generic error codes
> -> Abstract: File/major entity not found
>
> I tried a reindex and then a free, but the error re-occurred (possibly on the 2nd attempt to copy the same post).
>
> Any ideas on what to try next?
>
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

Ok, never mind, I found it in List Configuration…

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Apr 18, 2022, at 11:11, Steven J Depinet <[log in to unmask]> wrote:
>
> 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
> file. Encrypted, so I can’t modify it without using a Listserv utility, if it exists.
>
> 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.
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
>
>
>
>> On Apr 18, 2022, at 10:49, Nathan Brindle <[log in to unmask]> wrote:
>>
>> The directory /export/home/listserv/notebook/buslib-l does not exist, you will have to create it.
>>
>> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html
>>
>> Nathan
>>
>> -----Original Message-----
>> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Steven J Depinet
>> Sent: Monday, April 18, 2022 1:40 PM
>> To: [log in to unmask]
>> Subject: Broken list archive after copy from old system
>>
>> Greetings,
>>
>> 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:
>>
>> An error occurred while logging mail to the archives of the BUSLIB-L list.
>> An incomplete copy of the message might be present in the archive file. The
>> list is being held to prevent further occurrences of this error. Please take
>> corrective action and issue a "FREE BUSLIB-L" command when you want the
>> message to be reprocessed.
>>
>> Serious error occurred - traceback follows
>> ------------------------------------------
>>>>> Error X'00000011' opening file /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<
>> -> Severity: Warning
>> -> Facility: Generic error codes
>> -> Abstract: File/major entity not found
>> -> I/O mode: Record write
>>>>> Error X'00000011' logging message to archives <<<
>> -> Severity: Warning
>> -> Facility: Generic error codes
>> -> Abstract: File/major entity not found
>>
>> I tried a reindex and then a free, but the error re-occurred (possibly on the 2nd attempt to copy the same post).
>>
>> Any ideas on what to try next?
>>
>>
>> Steve dePinet Northern Arizona University
>> Systems Programmer, Sr. Box 5100
>> Information Technology Services Flagstaff, Az 86011
>> [log in to unmask] (928) 523-6843
>>
>> ############################
>>
>> To unsubscribe from the LSTSRV-L list:
>> write to: mailto:[log in to unmask]
>> or click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>> ############################
>>
>> To unsubscribe from the LSTSRV-L list:
>> write to: mailto:[log in to unmask]
>> or click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

Hi All,

What was the command a user can send via email to listserv to update his
name associated with his subscribed email address?
If you're subscribed as (kevin Joe <[log in to unmask]>) and want to update it
to (Dr. Kevin Joe <[log in to unmask]>).

On Mon, Apr 18, 2022 at 2:17 PM Steven J Depinet <
[log in to unmask]> wrote:

> Ok, never mind, I found it in List Configuration…
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
>
>
>
> > On Apr 18, 2022, at 11:11, Steven J Depinet <
> [log in to unmask]> wrote:
> >
> > 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
> > file. Encrypted, so I can’t modify it without using a Listserv utility,
> if it exists.
> >
> > 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.
> >
> > Steve dePinet Northern Arizona University
> > Systems Programmer, Sr. Box 5100
> > Information Technology Services Flagstaff, Az 86011
> > [log in to unmask] (928) 523-6843
> >
> >
> >
> >
> >> On Apr 18, 2022, at 10:49, Nathan Brindle <[log in to unmask]> wrote:
> >>
> >> The directory /export/home/listserv/notebook/buslib-l does not exist,
> you will have to create it.
> >>
> >> http://lsoft.com/manuals/lsv-faq/415Errorfilemajorentitynotfoundw.html
> >>
> >> Nathan
> >>
> >> -----Original Message-----
> >> From: LISTSERV Site Administrators' Forum <
> [log in to unmask]> On Behalf Of Steven J Depinet
> >> Sent: Monday, April 18, 2022 1:40 PM
> >> To: [log in to unmask]
> >> Subject: Broken list archive after copy from old system
> >>
> >> Greetings,
> >>
> >> 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:
> >>
> >> An error occurred while logging mail to the archives of the BUSLIB-L
> list.
> >> An incomplete copy of the message might be present in the archive
> file. The
> >> list is being held to prevent further occurrences of this error. Please
> take
> >> corrective action and issue a "FREE BUSLIB-L" command when you
> want the
> >> message to be reprocessed.
> >>
> >> Serious error occurred - traceback follows
> >> ------------------------------------------
> >>>>> Error X'00000011' opening file
> /export/home/listserv/notebook/buslib-l/buslib-l.log2204c <<<
> >> -> Severity: Warning
> >> -> Facility: Generic error codes
> >> -> Abstract: File/major entity not found
> >> -> I/O mode: Record write
> >>>>> Error X'00000011' logging message to archives <<<
> >> -> Severity: Warning
> >> -> Facility: Generic error codes
> >> -> Abstract: File/major entity not found
> >>
> >> I tried a reindex and then a free, but the error re-occurred (possibly
> on the 2nd attempt to copy the same post).
> >>
> >> Any ideas on what to try next?
> >>
> >>
> >> Steve dePinet Northern Arizona
> University
> >> Systems Programmer, Sr. Box 5100
> >> Information Technology Services Flagstaff, Az 86011
> >> [log in to unmask] (928) 523-6843
> >>
> >> ############################
> >>
> >> To unsubscribe from the LSTSRV-L list:
> >> write to: mailto:[log in to unmask]
> >> or click the following link:
> >> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> >>
> >> ############################
> >>
> >> To unsubscribe from the LSTSRV-L list:
> >> write to: mailto:[log in to unmask]
> >> or click the following link:
> >> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> >
> >
> > ############################
> >
> > To unsubscribe from the LSTSRV-L list:
> > write to: mailto:[log in to unmask]
> > or click the following link:
> > http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

No abstract is available available for this message. [Read Message ...]

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:

sudo setsebool -P httpd_can_network_connect 1

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.

If you later experience problems with WA writing to the "upload" directory, you may also need to execute

sudo semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/archives/upload'
sudo restorecon -v '/var/www/html/archives/upload'

(change the path to the upload directory if it differs in your installation).

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.

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.

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. 

[More ...]

Thanks 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.

Again, thanks,

Steve dePinet Northern Arizona University
Systems Programmer, Sr. Box 5100
Information Technology Services Flagstaff, Az 86011
[log in to unmask] (928) 523-6843

> On Apr 15, 2022, at 06:05, Nathan Brindle <[log in to unmask]> wrote:
>
> 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:
>
> sudo setsebool -P httpd_can_network_connect 1
>
> 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.
>
> If you later experience problems with WA writing to the "upload" directory, you may also need to execute
>
> sudo semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/archives/upload'
> sudo restorecon -v '/var/www/html/archives/upload'
>
> (change the path to the upload directory if it differs in your installation).
>
> 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.
>
> 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.
>
> 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.
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Steven J Depinet
> Sent: Thursday, April 14, 2022 1:34 PM
> To: [log in to unmask]
> Subject: SELinux (RHEL7) and port 2306 (Listserv V17.0)
>
> Greetings,
>
> 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:
>
> SELinux is preventing wa from name_connect access on the tcp_socket port 2306.
>
> It goes on to suggest:
> If you want to allow wa to connect to network port 2306, Then you need to modify the port type.
>
> Then provides the command:
> 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
>
> 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.
>
> 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?
>
> Thanks,
>
> Steve dePinet Northern Arizona University
> Systems Programmer, Sr. Box 5100
> Information Technology Services Flagstaff, Az 86011
> [log in to unmask] (928) 523-6843
>
>
>
>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Actually I found the answer in an old listserv message:

DEBUG_DMARC_REWRITE
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

I couldn't find where to set it in the GUI but it worked in the site.cfg file.

Krista

On Wed, Apr 13, 2022 at 2:13 PM Krista <[log in to unmask]> wrote:

> We're having problems with O365 refusing routing messages to Junk if
> they're coming from our ListServ server on our Intranet. It looks like it
> would work if p=reject were set for the top domain (of which our server is
> a subdomain) but it's only set on their external DNS records, and not on
> the Internal DNS record, which the ListServ server looks at.
>
> Is it possible to get the server to rewrite the From as if the p=reject
> were set for that specific domain? I know it's usually an automatic
> process but we need to require it manually (I don't think I'd be
> successful in getting them to add the DMARC p=reject to the internal DNS
> record).
>
> Krista Landon
>

The server which talking to eop should be on the spf.

If you listserv directly sending to eop, then the connecting up should be
on spf. Or route via the mailrelay which I believe would be already on spf.

On Mon, 4 Apr, 2022, 10:11 PM Krista, <[log in to unmask]> wrote:

> Is this article still the most current on how to get ListServ to work with
> O365 and not have messages being sent go into Junk?
>
> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
>
> Our ListServ is running on Windows and is on the Intranet of our
> organization, which has switched to using O365 for email. We currently use
> an SMTP relay. Messages that go to external addresses are fine, as the
> ListServ's domain has an SPF record that contains the ESAs, but if a
> message comes From the organization's main domain, from O365 to the
> ListServ, and the subscribers have a mailbox on the org's main domain (in
> O365), the messages takes a direct route to the microsoft production server
> and EOP, so the SPF check fails, and ironically internal mail, going to the
> listserv, then sent back to internal mail, gets tossed into subscriber's
> junk folders.
>
> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just
> going based on what our engineer is telling me.
>
> If anyone has more up to date suggestions on how to work with O365 (cloud)
> from an internal ListServ, please let me know.
>
> Krista Landon
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

The admin tells me:
"As to fix the SPF signature and alignment settings we will need to add all
Microsoft production server IPs ( because this will keep changing ). And
Microsoft will not make that list available to us."

"It is going to multiple MTAs (Message transport agents). In this case it
will start with the SMTP relay server which will forward the message to one
or more of the Hybrid exchange servers before it is routed via a nated IP
to Microsoft production servers where is will be inspected by EOP"

On Mon, Apr 4, 2022 at 1:10 PM Sunil Chauhan <[log in to unmask]> wrote:

> The server which talking to eop should be on the spf.
>
> If you listserv directly sending to eop, then the connecting up should be
> on spf. Or route via the mailrelay which I believe would be already on spf.
>
> On Mon, 4 Apr, 2022, 10:11 PM Krista, <[log in to unmask]> wrote:
>
>> Is this article still the most current on how to get ListServ to work
>> with O365 and not have messages being sent go into Junk?
>>
>> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
>>
>> Our ListServ is running on Windows and is on the Intranet of our
>> organization, which has switched to using O365 for email. We currently use
>> an SMTP relay. Messages that go to external addresses are fine, as the
>> ListServ's domain has an SPF record that contains the ESAs, but if a
>> message comes From the organization's main domain, from O365 to the
>> ListServ, and the subscribers have a mailbox on the org's main domain (in
>> O365), the messages takes a direct route to the microsoft production server
>> and EOP, so the SPF check fails, and ironically internal mail, going to the
>> listserv, then sent back to internal mail, gets tossed into subscriber's
>> junk folders.
>>
>> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just
>> going based on what our engineer is telling me.
>>
>> If anyone has more up to date suggestions on how to work with O365
>> (cloud) from an internal ListServ, please let me know.
>>
>> Krista Landon
>>
>>
>>
>> ------------------------------
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Sends this to your admin?

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

On Mon, Apr 4, 2022 at 1:26 PM Krista <[log in to unmask]> wrote:

> The admin tells me:
> "As to fix the SPF signature and alignment settings we will need to add
> all Microsoft production server IPs ( because this will keep changing ).
> And Microsoft will not make that list available to us."
>
> "It is going to multiple MTAs (Message transport agents). In this case it
> will start with the SMTP relay server which will forward the message to one
> or more of the Hybrid exchange servers before it is routed via a nated IP
> to Microsoft production servers where is will be inspected by EOP"
>
> On Mon, Apr 4, 2022 at 1:10 PM Sunil Chauhan <[log in to unmask]> wrote:
>
>> The server which talking to eop should be on the spf.
>>
>> If you listserv directly sending to eop, then the connecting up should be
>> on spf. Or route via the mailrelay which I believe would be already on spf.
>>
>> On Mon, 4 Apr, 2022, 10:11 PM Krista, <[log in to unmask]> wrote:
>>
>>> Is this article still the most current on how to get ListServ to work
>>> with O365 and not have messages being sent go into Junk?
>>>
>>> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
>>>
>>> Our ListServ is running on Windows and is on the Intranet of our
>>> organization, which has switched to using O365 for email. We currently use
>>> an SMTP relay. Messages that go to external addresses are fine, as the
>>> ListServ's domain has an SPF record that contains the ESAs, but if a
>>> message comes From the organization's main domain, from O365 to the
>>> ListServ, and the subscribers have a mailbox on the org's main domain (in
>>> O365), the messages takes a direct route to the microsoft production server
>>> and EOP, so the SPF check fails, and ironically internal mail, going to the
>>> listserv, then sent back to internal mail, gets tossed into subscriber's
>>> junk folders.
>>>
>>> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just
>>> going based on what our engineer is telling me.
>>>
>>> If anyone has more up to date suggestions on how to work with O365
>>> (cloud) from an internal ListServ, please let me know.
>>>
>>> Krista Landon
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> To unsubscribe from the LSTSRV-L list, click the following link:
>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>>
>>
>> ------------------------------
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> 

[More ...]

I did. The ListServ is on a subdomain. I pointed to include:
spf.protection.outlook.com. He said:
"that is what we have for our (topleveldomain) SPF records, but the IP
records contained in the spf.protection.outlook.com records do not contain
the Microsoft production servers."

It doesn't seem like it should be this difficult...
But maybe this is why Lsoft wrote the article with this as a potential
solution:
" The solution is to use the Microsoft SMTPSVC mailer on the LISTSERV
machine in a slightly different manner than described above and let SMTPSVC
do the necessary authentication so that the email will be accepted by the
Exchange Online server and forwarded on to wherever it needs to go."

Krista Landon

On Mon, Apr 4, 2022 at 1:33 PM Ricardo Stella <[log in to unmask]> wrote:

>
> Sends this to your admin?
>
>
> 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
>
> On Mon, Apr 4, 2022 at 1:26 PM Krista <[log in to unmask]> wrote:
>
>> The admin tells me:
>> "As to fix the SPF signature and alignment settings we will need to add
>> all Microsoft production server IPs ( because this will keep changing ).
>> And Microsoft will not make that list available to us."
>>
>> "It is going to multiple MTAs (Message transport agents). In this case
>> it will start with the SMTP relay server which will forward the message to
>> one or more of the Hybrid exchange servers before it is routed via a nated
>> IP to Microsoft production servers where is will be inspected by EOP"
>>
>> On Mon, Apr 4, 2022 at 1:10 PM Sunil Chauhan <[log in to unmask]> wrote:
>>
>>> The server which talking to eop should be on the spf.
>>>
>>> If you listserv directly sending to eop, then the connecting up should
>>> be on spf. Or route via the mailrelay which I believe would be already on
>>> spf.
>>>
>>> On Mon, 4 Apr, 2022, 10:11 PM Krista, <[log in to unmask]> wrote:
>>>
>>>> Is this article still the most current on how to get ListServ to work
>>>> with O365 and not have messages being sent go into Junk?
>>>>
>>>> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
>>>>
>>>> Our ListServ is running on Windows and is on the Intranet of our
>>>> organization, which has switched to using O365 for email. We currently use
>>>> an SMTP relay. Messages that go to external addresses are fine, as the
>>>> ListServ's domain has an SPF record that contains the ESAs, but if a
>>>> message comes From the organization's main domain, from O365 to the
>>>> ListServ, and the subscribers have a mailbox on the org's main domain (in
>>>> O365), the messages takes a direct route to the microsoft production server
>>>> and EOP, so the SPF check fails, and ironically internal mail, going to the
>>>> listserv, then sent back to internal mail, gets tossed into subscriber's
>>>> junk folders.
>>>>
>>>> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just
>>>> going based on what our engineer is telling me.
>>>>
>>>> If anyone has more up to date suggestions on how to work with O365
>>>> (cloud) from an internal ListServ, please let me know.
>>>>
>>>> Krista Landon
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> To unsubscribe from the LSTSRV-L list, click the following link:
>>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>>>
>>>
>>> ------------------------------
>>>
>>> To unsubscribe from the LSTSRV-L list, click the following link:
>>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>>
>>
>> ------------------------------
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>
>
> --
> °(((=((===°°°(((================================================
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

“…one or more of the Hybrid exchange servers before it is routed via a nated IP to Microsoft production servers…”

This is the IP you need to add to your listserv SPF. You are routing all email for your primary domain through your hybrid exchange servers to get to O365 which is why listserv messages for your domain are showing that address. If your multiple exchange servers are not all NATing to the same address then you’ll need to add each of their external addresses to listserv’s SPF.

Joe

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Krista
Sent: Monday, April 4, 2022 12:47 PM
To: [log in to unmask]
Subject: Re: Using ListServ with O365

I did. The ListServ is on a subdomain. I pointed to include:spf.protection.outlook.com<http://spf.protection.outlook.com>. He said:
"that is what we have for our (topleveldomain) SPF records, but the IP records contained in the spf.protection.outlook.com<http://spf.protection.outlook.com> records do not contain the Microsoft production servers."

It doesn't seem like it should be this difficult...
But maybe this is why Lsoft wrote the article with this as a potential solution:
" The solution is to use the Microsoft SMTPSVC mailer on the LISTSERV machine in a slightly different manner than described above and let SMTPSVC do the necessary authentication so that the email will be accepted by the Exchange Online server and forwarded on to wherever it needs to go."

Krista Landon

On Mon, Apr 4, 2022 at 1:33 PM Ricardo Stella <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Sends this to your admin?

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

On Mon, Apr 4, 2022 at 1:26 PM Krista <[log in to unmask]<mailto:[log in to unmask]>> wrote:
The admin tells me:
"As to fix the SPF signature and alignment settings we will need to add all Microsoft production server IPs ( because this will keep changing ). And Microsoft will not make that list available to us." 

[More ...]

Thank you! I'm running that past the exchange administrator. If it's a
single NAT IP, that would be an easy fix. I believe strongly in Murphy's
law though ;)

On Mon, Apr 4, 2022 at 2:29 PM Irons, Joseph R <[log in to unmask]>
wrote:

> “…one or more of the Hybrid exchange servers before it is routed via a
> nated IP to Microsoft production servers…”
>
>
>
> This is the IP you need to add to your listserv SPF. You are routing all
> email for your primary domain through your hybrid exchange servers to get
> to O365 which is why listserv messages for your domain are showing that
> address. If your multiple exchange servers are not all NATing to the same
> address then you’ll need to add each of their external addresses to
> listserv’s SPF.
>
>
>
> Joe
>
>
>
> *From:* LISTSERV Site Administrators' Forum <[log in to unmask]>
> *On Behalf Of *Krista
> *Sent:* Monday, April 4, 2022 12:47 PM
> *To:* [log in to unmask]
> *Subject:* Re: Using ListServ with O365
>
>
>
> I did. The ListServ is on a subdomain. I pointed to include:
> spf.protection.outlook.com. He said:
> "that is what we have for our (topleveldomain) SPF records, but the IP
> records contained in the spf.protection.outlook.com records do not
> contain the Microsoft production servers."
>
> It doesn't seem like it should be this difficult...
> But maybe this is why Lsoft wrote the article with this as a potential
> solution:
> " The solution is to use the Microsoft SMTPSVC mailer on the LISTSERV
> machine in a slightly different manner than described above and let SMTPSVC
> do the necessary authentication so that the email will be accepted by the
> Exchange Online server and forwarded on to wherever it needs to go."
>
> Krista Landon
>
>
>
> On Mon, Apr 4, 2022 at 1:33 PM Ricardo Stella <[log in to unmask]> wrote:
>
>
>
> Sends this to your admin?
>
>
>
>
> 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
>
>
>
> On Mon, Apr 4, 2022 at 1:26 PM Krista <[log in to unmask]> wrote:
>
> The admin tells me:
> "As to fix the SPF signature and alignment settings we will need to add
> all Microsoft production server IPs ( because this will keep changing ).
> And Microsoft will not make that list available to us."
>
> "It is going to multiple MTAs (Message transport agents). In this case it
> will start with the SMTP relay server which will forward the message to one
> or more of the Hybrid exchange servers before it is routed via a nated IP
> to Microsoft production servers where is will be inspected by EOP"
>
>
>
> On Mon, Apr 4, 2022 at 1:10 PM Sunil Chauhan <[log in to unmask]> wrote:
>
> The server which talking to eop should be on the spf.
>
>
>
> If you listserv directly sending to eop, then the connecting up should be
> on spf. Or route via the mailrelay which I believe would be already on spf.
>
>
>
> On Mon, 4 Apr, 2022, 10:11 PM Krista, <[log in to unmask]> wrote:
>
> Is this article still the most current on how to get ListServ to work with
> O365 and not have messages being sent go into Junk?
>
> https://www.lsoft.com/news/techtipLSV-issue3-2015.asp
>
> Our ListServ is running on Windows and is on the Intranet of our
> organization, which has switched to using O365 for email. We currently use
> an SMTP relay. Messages that go to external addresses are fine, as the
> ListServ's domain has an SPF record that contains the ESAs, but if a
> message comes From the organization's main domain, from O365 to the
> ListServ, and the subscribers have a mailbox on the org's main domain (in
> O365), the messages takes a direct route to the microsoft production server
> and EOP, so the SPF check fails, and ironically internal mail, going to the
> listserv, then sent back to internal mail, gets tossed into subscriber's
> junk folders.
>
> I'm not an exchange server engineer/Office 365 admin/engineer. I'm just
> going based on what our engineer is telling me.
>
>
>
> If anyone has more up to date suggestions on how to work with O365 (cloud)
> from an internal ListServ, please let me know.
>
>
>
> Krista Landon
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
>
> --
>
> °(((*=*((*===°°°*(((*================================================*
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

No abstract is available available for this message. [Read Message ...]

Hi,
You do this under List Management - Subscribers Report.
Subscriber Reports
Click *Customize Report* to add *Acknowledgment*
You can take it from here.

If you have any questions or if I may be of further assistance, please let
me know

Regards,
Nick

[image: photo]
*Nick Abiola-Bisiolu*
Senior Electronic Communications Analyst, Information Technology

Phone: 732.465. 5452 <732.562-5452>| Email: [log in to unmask]
445 Hoes Lane Piscataway, NJ 08854

| © Copyright 2017 IEEE – All rights reserved.

A not-for-profit organization, IEEE is the world's largest technical
professional organization dedicated to advancing technology for the benefit
of humanity
*This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. Any
review, dissemination, copying, printing, or other use of this email by
persons or entities other than the addressee is prohibited. If you have
received this email in error, please contact the sender immediately and
delete the material from any computer.*

On Mon, Mar 14, 2022 at 12:28 PM Darin Pesnell <[log in to unmask]> wrote:

> Good morning,
>
> Is there a way to apply a change for all subscribers to a certain list? I
> have a requirement to enable "ack" for all subscribers to a certain list.
> I can see how to do that for the individual subscriber settings but the
> list owner wants it applied to all subscribers. Thank you for an insight
> into the best way to do this.
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Just use the “Listserv command” option from the web interface and enter:
quiet set LISTNAME ack for *@*
And hit submit.

You can do multiple settings changes this way like:

quiet set LISTNAME ack,subj for *@*

> On Mar 14, 2022, at 12:28 PM, Darin Pesnell <[log in to unmask]> wrote:
>
> 
> Good morning,
>
> Is there a way to apply a change for all subscribers to a certain list? I have a requirement to enable "ack" for all subscribers to a certain list. I can see how to do that for the individual subscriber settings but the list owner wants it applied to all subscribers. Thank you for an insight into the best way to do this.
>
>
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

Be sure you also edit the list header to set the default options, so any
new subscribers who come along later will get this setting.

On 3/14/2022 12:28 PM, Darin Pesnell wrote:
> Good morning,
>
> Is there a way to apply a change for all subscribers to a certain
> list?  I have a requirement to enable "ack" for all subscribers to a
> certain list.   I can see how to do that for the individual subscriber
> settings but the list owner wants it applied to all subscribers. 
> Thank you for an insight into the best way to do this.
>

Thank you ! That’s really helpful.

On Mon, Mar 14, 2022 at 11:18 AM Mark Kaprow <[log in to unmask]> wrote:

> Just use the “Listserv command” option from the web interface and enter:
> quiet set LISTNAME ack for *@*
> And hit submit.
>
> You can do multiple settings changes this way like:
>
> quiet set LISTNAME ack,subj for *@*
>
>
>
>
>
> On Mar 14, 2022, at 12:28 PM, Darin Pesnell <[log in to unmask]> wrote:
>
> 
>
> Good morning,
>
> Is there a way to apply a change for all subscribers to a certain list? I
> have a requirement to enable "ack" for all subscribers to a certain list.
> I can see how to do that for the individual subscriber settings but the
> list owner wants it applied to all subscribers. Thank you for an insight
> into the best way to do this.
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
--
Sent from my iPhone

Have you checked that an open list is not mistakenly subscribed to the list?

On Sun, Mar 6, 2022 at 12:13 PM Shinn Wu <[log in to unmask]> wrote:

> Hello,
>
> We have been using Listserv for more than 20 years on Linux (current
> 17.0). This is the first time I saw it happen. The list configuration is:
>
> .HH ON
>
> Ack= No
> Review= Owners
> Subscription= By owner
> Send= Editor,Hold
> Notify= Yes
> Reply-To= Sender,Respect
> Validate= No
> Notebook= Yes,/u/ssc/listserv/lists,Monthly,Private
> Default-Options= Repro,Subjecthdr
> Misc-Options= KEEP_EXCHANGE_DATA
>
> Owner= (chavez-alias)
> Editor= (chavez-alias)
> .HH OFF
>
> The list has 424 subscribers.
>
>
>
> However, it sent to 455 according to the log:
>
> 4 Mar 2022 11:12:43 Distributing mail ("CHAVEZ-UNDERGRADS") from
> owner-chavez-undergrads@LISTS.SSCNET.UCLA.EDU...
> 4 Mar 2022 11:12:43 Mail posted via SMTP to [log in to unmask]
> ......................................................
> 4 Mar 2022 11:12:43 Mail posted via SMTP to [log in to unmask]
> 4 Mar 2022 11:12:43 Done - 5 outbound files (455 rcpts).
> 4 Mar 2022 11:12:43 Message DISTRIBUTEd to 455 recipients.
>
> It came to my attention after some faculty complained they were not
> undergrads. I checked the log and found about 20 faculties who are *not*
> on the subscribers but showed in the Listserv log.
>
> Any hint will be greatly appreciated.
>
> Thank you,
>
> Shinn
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Were they CC'd/BCC'd on the original message, i.e., before it went through the list? By default, LISTSERV strips any CC and BCC fields, so you would not be able to tell from the distributed message.

Nathan

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Shinn Wu
Sent: Saturday, March 05, 2022 11:36 AM
To: [log in to unmask]
Subject: List Distributions

Hello,

We have been using Listserv for more than 20 years on Linux (current 17.0). This is the first time I saw it happen. The list configuration is:

.HH ON

Ack= No
Review= Owners
Subscription= By owner
Send= Editor,Hold
Notify= Yes
Reply-To= Sender,Respect
Validate= No
Notebook= Yes,/u/ssc/listserv/lists,Monthly,Private
Default-Options= Repro,Subjecthdr
Misc-Options= KEEP_EXCHANGE_DATA

Owner= (chavez-alias)
Editor= (chavez-alias)
.HH OFF

The list has 424 subscribers.

[cid:image001.png@01D831FD.AE09BBB0]

However, it sent to 455 according to the log:

4 Mar 2022 11:12:43 Distributing mail ("CHAVEZ-UNDERGRADS") from owner-chavez-undergrads@LISTS.SSCNET.UCLA.EDU...
4 Mar 2022 11:12:43 Mail posted via SMTP to [log in to unmask]

Thank everyone who kindly replied to my question.

I backtraced the log and found the change I made last Dec. I removed the change and asked the sender to send it again. It was only distributed to 424 undergrads (instead of 455).

Shinn

What was “the change”? It would be nice to know this, in case one of those falls into the same trap.

Hello,

The list had a sub-list before. The puzzle remains: the sub-list only has 8 subscribers. Most of the 'unwanted' subscribers (18) shown in the distribution log did not​ in the CHAVEZ-ALIAS (only one is).

[log in to unmask] (8 Subscribers)

However, the distribution was "normal" after I manually edited 26 affected lists last night. I knew that it would distribute to sub-lists but the first few faculties who received were not in CHAVEZ-ALIAS that cast my doubt if 'sub-lists' was the true reason.

Anyway, thank you again for the very helpful input. Problem partially solved and no one complain.

Shinn

No abstract is available available for this message. [Read Message ...]

I recently had to do that. Here's what I did -

INDEX <listname>
That will get you a list of all the archive files for the list.

Next, using the contents of the message you received with the log file names, send another command that contains the Get command followed by the name of the list, then the first logfile. You can send all the logfiles in one message like this:

GET listname LOG0501
GET listname LOG0502
GET listname LOG0503

Etc.

You'll receive an email back for each log. After you receive a message for each log file, create an Outlook folder and move all the messages into the folder to keep them all together. Then use Outlook Export to export that folder to a pst file and give it to your customer. That's assuming you are using Outlook. If not, that last bit will need to be different depending on your email vendor.

Jan Dye

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Lane, Tammy J.
Sent: Friday, February 11, 2022 12:46 PM
To: [log in to unmask]
Subject: Export the archives from a List

WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
Hello,

Is there a way to export the archives from a list? I have someone that wants the list that she is the owner of deleted but she wants a copy of the archives from the list. I have not found, how to do this. Can anyone help me out? 

[More ...]

Thank you so much. I greatly appreciate it.

Tammy Lane
OCIO Service Desk Team Lead
OCIO Service Desk
Office of the Chief Information Officer
Kapstone Technologies
[log in to unmask]<mailto:[log in to unmask]>
202-633-4000

ServiceNow: How to Submit an IT Request<https://smithsonianprod.servicenowservices.com/si?id=kb_article_view&sysparm_article=KB0011715>
ServiceNow: How to Report an IT Problem/Incident<https://smithsonianprod.servicenowservices.com/si?id=kb_article_view&sysparm_article=KB0011716>
ServiceNow: How to View Existing IT Service Requests and Incidents<https://smithsonianprod.servicenowservices.com/si?id=kb_article_view&sysparm_article=KB0011841>

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Dye, Jan
Sent: Friday, February 11, 2022 3:03 PM
To: [log in to unmask]
Subject: Re: Export the archives from a List

External Email - Exercise Caution
I recently had to do that. Here's what I did -

INDEX <listname>
That will get you a list of all the archive files for the list.

Next, using the contents of the message you received with the log file names, send another command that contains the Get command followed by the name of the list, then the first logfile. You can send all the logfiles in one message like this:

GET listname LOG0501
GET listname LOG0502
GET listname LOG0503

Etc.

You'll receive an email back for each log. After you receive a message for each log file, create an Outlook folder and move all the messages into the folder to keep them all together. Then use Outlook Export to export that folder to a pst file and give it to your customer. That's assuming you are using Outlook. If not, that last bit will need to be different depending on your email vendor.

Jan Dye

From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Lane, Tammy J.
Sent: Friday, February 11, 2022 12:46 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Export the archives from a List

WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
Hello, 

[More ...]

On Fri, 11 Feb 2022 18:46:21 +0000, "Lane, Tammy J."
<[log in to unmask]> wrote:

>Is there a way to export the archives from a list?

You have received 2 fine answers which are essentially the same. This will
work for the List Owner but depending on how old the list is, how active it
was, etc. that could be a lot of work. For example a list that is 20 years
old and averages 5-8 messages per day, will have 240 archive files totaling
over 200MB (based one of my real lists).

Another solution (outside of LISTSERV) is to simply ask the server
administrator to zip up all the LISTNAME.LOGyymm files on disk and send that
zip archive to the List Owner. The files are all simply plain text files so
they will compress a fair amount. This could be a lot easier and faster.

The one problem with raw archive files LISTNAME.LOGYYMM is that mime encoded content will be displayed as 7-bit mime.

If the messages have lots of rich content and attachments then the raw files will be unreadable. Instead, they could remove all the members, make the list CONFIDENTIAL = YES and just allow the list owner to refer to old messages as needed.

> On Feb 11, 2022, at 8:03 PM, Ben Parker <[log in to unmask]> wrote:
>
> On Fri, 11 Feb 2022 18:46:21 +0000, "Lane, Tammy J."
> <[log in to unmask]> wrote:
>
>> Is there a way to export the archives from a list?
>
> You have received 2 fine answers which are essentially the same. This will
> work for the List Owner but depending on how old the list is, how active it
> was, etc. that could be a lot of work. For example a list that is 20 years
> old and averages 5-8 messages per day, will have 240 archive files totaling
> over 200MB (based one of my real lists).
>
> Another solution (outside of LISTSERV) is to simply ask the server
> administrator to zip up all the LISTNAME.LOGyymm files on disk and send that
> zip archive to the List Owner. The files are all simply plain text files so
> they will compress a fair amount. This could be a lot easier and faster.
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

There is an address for that, [log in to unmask] I found in the past that Listserv dumps all the messages out in a single SMTP transaction which may (and probably should) raise objections from your SMTP server. I had to remove all restrictions on SMTP transactions temporarily in order to get the messages to go out.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jan Dye
Sent: Friday, February 11, 2022 11:58 AM
To: [log in to unmask]
Subject: [LSTSRV-L] How to contact all list owners

Hello -
Is there a way as site administrator to send a message to all list owners? I seem to remember some way to do this, but can't find this documented. I'd like to let all list owners know about a planned outage.

Thank you!

Thanks for your reply!

I assume that has to be sent from one of the postmaster addresses in site configuration?

J

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Kenny, Melissa S.
Sent: Friday, February 11, 2022 11:13 AM
To: [log in to unmask]
Subject: Re: How to contact all list owners

WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.

There is an address for that, [log in to unmask] I found in the past that Listserv dumps all the messages out in a single SMTP transaction which may (and probably should) raise objections from your SMTP server. I had to remove all restrictions on SMTP transactions temporarily in order to get the messages to go out.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jan Dye
Sent: Friday, February 11, 2022 11:58 AM
To: [log in to unmask]
Subject: [LSTSRV-L] How to contact all list owners

Hello -
Is there a way as site administrator to send a message to all list owners? I seem to remember some way to do this, but can't find this documented. I'd like to let all list owners know about a planned outage.

Thank you!

Site Manager's Manual, 25.3.2 The ALL-REQUEST Alias

http://lsoft.com/manuals/16.0/htmlhelp/site%20managers/OtherFeaturesFunctions.html#2335134

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Dye, Jan
Sent: Friday, February 11, 2022 12:35 PM
To: [log in to unmask]
Subject: Re: How to contact all list owners

Thanks for your reply!

I assume that has to be sent from one of the postmaster addresses in site configuration?

J

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Kenny, Melissa S.
Sent: Friday, February 11, 2022 11:13 AM
To: [log in to unmask]
Subject: Re: How to contact all list owners

WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.

There is an address for that, [log in to unmask] I found in the past that Listserv dumps all the messages out in a single SMTP transaction which may (and probably should) raise objections from your SMTP server. I had to remove all restrictions on SMTP transactions temporarily in order to get the messages to go out.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jan Dye
Sent: Friday, February 11, 2022 11:58 AM
To: [log in to unmask]
Subject: [LSTSRV-L] How to contact all list owners

Hello -
Is there a way as site administrator to send a message to all list owners? I seem to remember some way to do this, but can't find this documented. I'd like to let all list owners know about a planned outage.

Thank you!

Nathan,

Thanks for the link - that helps!
J

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Nathan Brindle
Sent: Friday, February 11, 2022 11:38 AM
To: [log in to unmask]
Subject: Re: How to contact all list owners

Site Manager's Manual, 25.3.2 The ALL-REQUEST Alias

https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flsoft.com%2Fmanuals%2F16.0%2Fhtmlhelp%2Fsite%2520managers%2FOtherFeaturesFunctions.html%232335134&amp;data=04%7C01%7Cdyeja%40umsystem.edu%7C6ef2b3259a334db4853308d9ed853243%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637801979038952559%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=eqspadjHh3XvXmPa2Co226PG8kWFFjY4P%2FgepyfqI1Q%3D&amp;reserved=0

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Dye, Jan
Sent: Friday, February 11, 2022 12:35 PM
To: [log in to unmask]
Subject: Re: How to contact all list owners

Thanks for your reply!

I assume that has to be sent from one of the postmaster addresses in site configuration?

J

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Kenny, Melissa S.
Sent: Friday, February 11, 2022 11:13 AM
To: [log in to unmask]
Subject: Re: How to contact all list owners

WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.

There is an address for that, [log in to unmask] I found in the past that Listserv dumps all the messages out in a single SMTP transaction which may (and probably should) raise objections from your SMTP server. I had to remove all restrictions on SMTP transactions temporarily in order to get the messages to go out.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Jan Dye
Sent: Friday, February 11, 2022 11:58 AM
To: [log in to unmask]
Subject: [LSTSRV-L] How to contact all list owners

Hello -
Is there a way as site administrator to send a message to all list owners? I seem to remember some way to do this, but can't find this documented. I'd like to let all list owners know about a planned outage. 

[More ...]

Hi Melissa,

I read your response and want to know what was your SMTP application
(Sendmail or Postfix) and what variable did you change to allow the message
to go out?

If you have any questions or if I may be of further assistance, please let
me know

Regards,
Nick

[image: photo]
*Nick Abiola-Bisiolu*

On Fri, Feb 11, 2022 at 12:33 PM Kenny, Melissa S. <
[log in to unmask]> wrote:

> There is an address for that, [log in to unmask] I found in the
> past that Listserv dumps all the messages out in a single SMTP transaction
> which may (and probably should) raise objections from your SMTP server. I
> had to remove all restrictions on SMTP transactions temporarily in order to
> get the messages to go out.
>
> Melissa Kenny
>
> Web Administrator
> Harvard Medical School IT
>
> 401 Park Drive
> Suite 504 West
> Boston, MA 02215
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]>
> On Behalf Of Jan Dye
> Sent: Friday, February 11, 2022 11:58 AM
> To: [log in to unmask]
> Subject: [LSTSRV-L] How to contact all list owners
>
> Hello -
> Is there a way as site administrator to send a message to all list owners?
> I seem to remember some way to do this, but can't find this documented.
> I'd like to let all list owners know about a planned outage.
>
> Thank you!
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Nick,

We use an IronPort appliance to do the SMTP sending and I had to edit the rules on there temporarily to send out the message.

Melissa

From: ✉ Nick Abiola-Bisiolu <[log in to unmask]>
Sent: Tuesday, February 22, 2022 2:04 PM
To: LISTSERV Site Administrators' Forum <[log in to unmask]>; Kenny, Melissa S. <[log in to unmask]>
Subject: Re: How to contact all list owners

Hi Melissa,

I read your response and want to know what was your SMTP application (Sendmail or Postfix) and what variable did you change to allow the message to go out?

If you have any questions or if I may be of further assistance, please let me know

Regards,
Nick

[photo]
Nick Abiola-Bisiolu

On Fri, Feb 11, 2022 at 12:33 PM Kenny, Melissa S. <[log in to unmask]<mailto:[log in to unmask]>> wrote:
There is an address for that, [log in to unmask] I found in the past that Listserv dumps all the messages out in a single SMTP transaction which may (and probably should) raise objections from your SMTP server. I had to remove all restrictions on SMTP transactions temporarily in order to get the messages to go out.

Melissa Kenny

Web Administrator
Harvard Medical School IT

401 Park Drive
Suite 504 West
Boston, MA 02215

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Jan Dye
Sent: Friday, February 11, 2022 11:58 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [LSTSRV-L] How to contact all list owners

Hello -
Is there a way as site administrator to send a message to all list owners? I seem to remember some way to do this, but can't find this documented. I'd like to let all list owners know about a planned outage.

Thank you!

OK, thanks for the update.

Regards,
Nick

On Tue, Feb 22, 2022 at 2:13 PM Kenny, Melissa S. <
[log in to unmask]> wrote:

> Nick,
>
>
>
> We use an IronPort appliance to do the SMTP sending and I had to edit the
> rules on there temporarily to send out the message.
>
>
>
> Melissa
>
>
>
> *From:* ✉ Nick Abiola-Bisiolu <[log in to unmask]>
> *Sent:* Tuesday, February 22, 2022 2:04 PM
> *To:* LISTSERV Site Administrators' Forum <[log in to unmask]>;
> Kenny, Melissa S. <[log in to unmask]>
> *Subject:* Re: How to contact all list owners
>
>
>
> Hi Melissa,
>
>
>
> I read your response and want to know what was your SMTP application
> (Sendmail or Postfix) and what variable did you change to allow the message
> to go out?
>
>
>
>
>
>
>
> If you have any questions or if I may be of further assistance, please let
> me know
>
> Regards,
>
> Nick
>
>
>
> [image: photo]
>
> *Nick Abiola-Bisiolu*
>
>
>
>
>
>
>
> On Fri, Feb 11, 2022 at 12:33 PM Kenny, Melissa S. <
> [log in to unmask]> wrote:
>
> There is an address for that, [log in to unmask] I found in the
> past that Listserv dumps all the messages out in a single SMTP transaction
> which may (and probably should) raise objections from your SMTP server. I
> had to remove all restrictions on SMTP transactions temporarily in order to
> get the messages to go out.
>
> Melissa Kenny
>
> Web Administrator
> Harvard Medical School IT
>
> 401 Park Drive
> Suite 504 West
> Boston, MA 02215
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]>
> On Behalf Of Jan Dye
> Sent: Friday, February 11, 2022 11:58 AM
> To: [log in to unmask]
> Subject: [LSTSRV-L] How to contact all list owners
>
> Hello -
> Is there a way as site administrator to send a message to all list owners?
> I seem to remember some way to do this, but can't find this documented.
> I'd like to let all list owners know about a planned outage.
>
> Thank you!
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__peach.ease.lsoft.com_scripts_wa-2DPEACH.exe-3FSUBED1-3DLSTSRV-2DL-26A-3D1&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=pD1lZJp6AWAigCq-w3nmcaqA_JVXPNb9AkRG3TWgKGk&m=BxLyJO5mZ2-hlowBUV_PV6OvW8zZk2CvGcCSQpxy9pCvx9ZrP2alos812-j0sV_t&s=djAqFSYfe_uz2K9f2td7b-QebnF76E3pP-wTCp4r75I&e=>
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__peach.ease.lsoft.com_scripts_wa-2DPEACH.exe-3FSUBED1-3DLSTSRV-2DL-26A-3D1&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=pD1lZJp6AWAigCq-w3nmcaqA_JVXPNb9AkRG3TWgKGk&m=BxLyJO5mZ2-hlowBUV_PV6OvW8zZk2CvGcCSQpxy9pCvx9ZrP2alos812-j0sV_t&s=djAqFSYfe_uz2K9f2td7b-QebnF76E3pP-wTCp4r75I&e=>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

I think it’s the other way around, when a site has dmarc with p=reject listserv does the rewrite (listserv knows this via dns lookup) and if you reply to that address then listserv is supposed to forward the reply to the correct sender.

> On Jan 17, 2022, at 2:27 PM, Peter M. Weiss <[log in to unmask]> wrote:
>
>  When LISTSERV distributes an email from a user who's site doesn't support DMARC, it rewrites that address e.g.,
>
> <[log in to unmask]>
>
> Here at PSU, that bounces.
>
> How does LISTSERV "know" to generate that kind of address: a realtime lookup of the sender's address or does it maintain a static list of such domains?
>
> --
>
> Pete
> Sr. Systems Configurator, emeritus
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

On Jan 17, 2022, at 2:27 PM, Peter M. Weiss <[log in to unmask]> wrote:

> How does LISTSERV "know" to generate that kind of address: a realtime lookup of the sender's address or does it maintain a static list of such domains?

When LISTSERV processes mail for a mailing list, it looks to see if the domain of the sender has a DMARC record has a ‘p=reject’ or ‘p=quarantine’ policy. If it does, then it rewrites the address.

LISTSERV doesn’t cache this information anywhere — it does a fresh lookup every time it distributes a message.

Additional information can be found here:

http://www.lsoft.com/manuals/17.0/advancedtopics/133HowdoesLISTSERVcomplywithDMAR.html <http://www.lsoft.com/manuals/17.0/advancedtopics/133HowdoesLISTSERVcomplywithDMAR.html>

Thanks,
jwgh

Hi Darin,

I assume that this info is contained in the list's bottom banner. If so you
can modify the banner in List Management and selecting Top and Bottom
Banners in the Template category. Modify both the Bottom_Banner and the
Bottom_Banner_HTML

Glenn
[image: UMSIT:SDS Logo]
Glenn R. Eichel
*SSA*
*UMSIT - Service Delivery and Support*
*Lecturer*
*UMaine Department of Sociology*
207-581-4631
201-H Fernald Hall
Orono, Maine 04469
[log in to unmask]

On Tue, Jan 4, 2022 at 9:59 AM Darin Pesnell <[log in to unmask]> wrote:

> Good morning all,
>
> I have a request to remove the link to the web archive from a listserv I
> run. I need the archive to still exist, but the the customer would like
> the link removed from emails. Does anyone know how to do this?
>
> Thank you,
> Darin
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

That worked perfectly. Thank you, Glenn!

On Tue, Jan 4, 2022 at 10:24 AM Glenn Eichel <[log in to unmask]> wrote:

> Hi Darin,
>
> I assume that this info is contained in the list's bottom banner. If so
> you can modify the banner in List Management and selecting Top and Bottom
> Banners in the Template category. Modify both the Bottom_Banner and the
> Bottom_Banner_HTML
>
> Glenn
> [image: UMSIT:SDS Logo]
> Glenn R. Eichel
> *SSA*
> *UMSIT - Service Delivery and Support*
> *Lecturer*
> *UMaine Department of Sociology*
> 207-581-4631
> 201-H Fernald Hall
> Orono, Maine 04469
> [log in to unmask]
>
>
> On Tue, Jan 4, 2022 at 9:59 AM Darin Pesnell <[log in to unmask]> wrote:
>
>> Good morning all,
>>
>> I have a request to remove the link to the web archive from a listserv I
>> run. I need the archive to still exist, but the the customer would like
>> the link removed from emails. Does anyone know how to do this?
>>
>> Thank you,
>> Darin
>>
>>
>> ------------------------------
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

No abstract is available available for this message. [Read Message ...]

Hi Krista,

We used to have the same problem when we used Listserv 16.5 with confirmations unless turned HTTPS to HTTP.

The problem disappeared after we upgraded to 17.0 this year.

Best,

Shinn

On Dec 16, 2021, at 11:06 AM, Krista <[log in to unmask]> wrote:

> I followed the instructions I found here: https://www.lsoft.com/manuals/lsv-faq/443SecuringtheLISTSERVwebinterfa.html <https://www.lsoft.com/manuals/lsv-faq/443SecuringtheLISTSERVwebinterfa.html> to redirect all traffic from HTTP to HTTPS on my ListServ 16.5 installation. Everything worked except for Confirmation URLs, which threw a 500 error until I turned off the redirect rule.
>
> Anyone have ideas on why that's happening?
>
> Krista Landon

Were the confirmation links to http or https? What was the exact error you got when clicking on the links?

Thanks,
jwgh

Once I updated site.cfg and global skin templates the links were https. If
I remember correctly it was simply 500 Internal server error (definitely
500 error).
So long as that rule existed, the confirm wouldn't work with http or https.

Krista

On Thu, Dec 16, 2021 at 11:48 AM Jacob Haller <[log in to unmask]>
wrote:

> On Dec 16, 2021, at 11:06 AM, Krista <[log in to unmask]> wrote:
>
> I followed the instructions I found here:
> https://www.lsoft.com/manuals/lsv-faq/443SecuringtheLISTSERVwebinterfa.html
> to redirect all traffic from HTTP to HTTPS on my ListServ 16.5
> installation. Everything worked except for Confirmation URLs, which threw
> a 500 error until I turned off the redirect rule.
>
> Anyone have ideas on why that's happening?
>
> Krista Landon
>
>
> Were the confirmation links to http or https? What was the exact error you
> got when clicking on the links?
>
> Thanks,
> jwgh
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

LISTSERV itself is not affected. LISTSERV does not use Java and does not use Log4J.

With regard to Maestro, Development says:

(1) Versions of Maestro previous to 10.0 don't include Log4J, and therefore are unaffected by any Log4j vulnerabilities.

(2) Maestro 10.x does use Log4j with a version of the library that is vulnerable to CVE-2021-44228.

(3) Maestro 10.x doesn't actively use the Log4j functions that are subject to the vulnerability (it logs user agents using a different method), so we believe that, in its default configuration, Maestro 10.x is not affected by the vulnerability.

(4) However, to be absolutely certain that Maestro is not at risk, we have released a new Maestro update (10.0-4) which includes an updated, fixed version of Log4j in which the vulnerability is fixed.

F-Secure's anti-virus products (Windows Server Security and Linux Security) are not affected, only their Policy Manager which we do not supply to our customers.

Nathan

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Adam Arthur
Sent: Tuesday, December 14, 2021 4:45 PM
To: [log in to unmask]
Subject: Log4j Vulnerability Check

Hello Everyone,

I am currently looking into what all might be impacted by the log4j vulnerability. I know that LISTSERV uses F-Secure Anti-Virus and that other products of F-Secure have reported having issues with log4j. Does anyone know if LISTSERV or F-Secure Anti-Virus has the log4j vulnerability? Also, if there is an issue which will need to be patched, which versions could be impacted? If it is still an unknown, then I understand, but just was curious. Thank you for your help! Have a great day! 

[More ...]

We are Running ListServ V17. Received a response back from Support today that ListServ is unaffected.

Don't know if LSoft's posted anything yet on their website like I've seen other software developers do. Hint. Hint.

Kevin E. Zeitz
Systems Engineer

Technology Services Group
Carilion Clinic
451 Kimball Avenue
Roanoke, VA 24016
Email: [log in to unmask]<mailto:[log in to unmask]>
Phone: 540.224.4164 I Fax: 540.857.5455 I Mobile: 540.529.5969

> I am installing a fresh 17.x Listserv on RHEL and I have it mostly
> working. One issue though is that it the listserv is not setting the
> from address, but instead leaving it blank. I am trying to use Sendgrid
> as my SMTP server and they require this field to map to an approved
> domain, which it is not. Can anyone guide me on how to resolve this?

In my experience, LISTSERV usually just sent bounces that way. But
Sendgrid is breaking most of the rules by rejecting such mail.

De

RFC2505 (spam prevention), section 2, recommendation 6a:

MUST NOT refuse "MAIL From: <>".

RFC821 (SMTP), section 3.7:

One way to prevent loops in error reporting is to specify
a null reverse-path in the MAIL command of a notification
message. When such a message is relayed it is permissible
to leave the reverse-path null. A MAIL command with a null
reverse-path appears as follows:

MAIL FROM:<>

RFC2476 (message submission), section 3.2:

Note that a null return path, that is, MAIL FROM:<>, is
permitted and MUST be accepted. (MUAs need to generate null
return-path messages for a variety of reasons, including
disposition notifications.)

RFC1904 (DSN), section 2:

The envelope sender address of the DSN SHOULD be chosen to
ensure that no delivery status reports will be issued in
response to the DSN itself, and MUST be chosen so that DSNs
will not generate mail loops. Whenever an SMTP transaction
is used to send a DSN, the MAIL FROM command MUST use a NULL
return address, i.e. "MAIL FROM:<>".

RFC1891 (DSN), section 7.1:

The DSN sender address (in the SMTP MAIL command) MUST be a
null reverse-path ("<>"), as required by section 5.3.3 of [9].
The DSN recipient address (in the RCPT command) is copied from
the MAIL command which accompanied the message for which the
DSN is being issued. When transmitting a DSN via SMTP, the RET
parameter MUST NOT be used. The NOTIFY parameter MAY be used,
but its value MUST be NEVER. The ENVID parameter (with a newly
generated envelope-id) and/or ORCPT parameter MAY be used. 

[More ...]

We also have a FAQ for this.

http://lsoft.com/manuals/lsv-faq/416CanMAILFROMonadminmailbechang.html

The blank MAIL FROM is used for administrative messages from LISTSERV that should be dropped on the floor rather than returned to sender if they bounce for any reason. The point is to prevent a mailing loop starting up.

Blank MAIL FROM is *not* used for list postings, which have a return path of owner-something@NODE, where "something" can be a listname, or a listname and a token (i.e., for address probes).

As an anti-spam measure, blocking MAIL FROM:<> is worse than useless because it actively blocks legitimate mail that people have requested to have sent to them (like command confirmation requests).

Nathan

-----Original Message-----
From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Dennis Boone
Sent: Monday, December 13, 2021 4:09 PM
To: [log in to unmask]
Subject: Re: Blank Mail From

> I am installing a fresh 17.x Listserv on RHEL and I have it mostly
> working. One issue though is that it the listserv is not setting the
> from address, but instead leaving it blank. I am trying to use Sendgrid
> as my SMTP server and they require this field to map to an approved
> domain, which it is not. Can anyone guide me on how to resolve this?

In my experience, LISTSERV usually just sent bounces that way. But
Sendgrid is breaking most of the rules by rejecting such mail.

De

RFC2505 (spam prevention), section 2, recommendation 6a:

MUST NOT refuse "MAIL From: <>".

RFC821 (SMTP), section 3.7:

One way to prevent loops in error reporting is to specify
a null reverse-path in the MAIL command of a notification
message. When such a message is relayed it is permissible
to leave the reverse-path null. A MAIL command with a null
reverse-path appears as follows: 

[More ...]

Thanks for this feedback. It's frustrating sendgrid is not honoring this.
Does anyone know of an alternative to sendgrid that works well with
listserv?

On Mon, Dec 13, 2021 at 4:55 PM Nathan Brindle <[log in to unmask]> wrote:

> We also have a FAQ for this.
>
> http://lsoft.com/manuals/lsv-faq/416CanMAILFROMonadminmailbechang.html
>
> The blank MAIL FROM is used for administrative messages from LISTSERV that
> should be dropped on the floor rather than returned to sender if they
> bounce for any reason. The point is to prevent a mailing loop starting up.
>
> Blank MAIL FROM is *not* used for list postings, which have a return path
> of owner-something@NODE, where "something" can be a listname, or a
> listname and a token (i.e., for address probes).
>
> As an anti-spam measure, blocking MAIL FROM:<> is worse than useless
> because it actively blocks legitimate mail that people have requested to
> have sent to them (like command confirmation requests).
>
> Nathan
>
> -----Original Message-----
> From: LISTSERV Site Administrators' Forum <[log in to unmask]>
> On Behalf Of Dennis Boone
> Sent: Monday, December 13, 2021 4:09 PM
> To: [log in to unmask]
> Subject: Re: Blank Mail From
>
> > I am installing a fresh 17.x Listserv on RHEL and I have it mostly
> > working. One issue though is that it the listserv is not setting the
> > from address, but instead leaving it blank. I am trying to use Sendgrid
> > as my SMTP server and they require this field to map to an approved
> > domain, which it is not. Can anyone guide me on how to resolve this?
>
> In my experience, LISTSERV usually just sent bounces that way. But
> Sendgrid is breaking most of the rules by rejecting such mail.
>
> De
>
>
> RFC2505 (spam prevention), section 2, recommendation 6a:
>
> MUST NOT refuse "MAIL From: <>".
>
> RFC821 (SMTP), section 3.7:
>
> One way to prevent loops in error reporting is to specify
> a null reverse-path in the MAIL command of a notification
> message. When such a message is relayed it is permissible
> to leave the reverse-path null. A MAIL command with a null
> reverse-path appears as follows:
>
> MAIL FROM:<>
>
> RFC2476 (message submission), section 3.2:
>
> Note that a null return path, that is, MAIL FROM:<>, is
> permitted and MUST be accepted. (MUAs need to generate null
> return-path messages for a variety of reasons, including
> disposition notifications.)
>
> RFC1904 (DSN), section 2:
>
> The envelope sender address of the DSN SHOULD be chosen to
> ensure that no delivery status reports will be issued in
> response to the DSN itself, and MUST be chosen so that DSNs
> will not generate mail loops. Whenever an SMTP transaction
> is used to send a DSN, the MAIL FROM command MUST use a NULL
> return address, i.e. "MAIL FROM:<>".
>
> RFC1891 (DSN), section 7.1:
>
> The DSN sender address (in the SMTP MAIL command) MUST be a
> null reverse-path ("<>"), as required by section 5.3.3 of [9].
> The DSN recipient address (in the RCPT command) is copied from
> the MAIL command which accompanied the message for which the
> DSN is being issued. When transmitting a DSN via SMTP, the RET
> parameter MUST NOT be used. The NOTIFY parameter MAY be used,
> but its value MUST be NEVER. The ENVID parameter (with a newly
> generated envelope-id) and/or ORCPT parameter MAY be used.
>
> RFC1123 (requirements for internet hosts), section 5.2.9:
>
> The syntax shown in RFC-821 for the MAIL FROM: command omits
> the case of an empty path: "MAIL FROM: <>" (see RFC-821
> Page 15). An empty reverse path MUST be supported.
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Assuming that your email clients and servers are using TLS the password updates are being end-to-end encrypted by the mail system. Note that listserv does not send password changes, it only receives them. However, anyone able to log in to the listserv user account can see password updates.

> On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask]> wrote:
>
> My company's IT security folks are concerned that ListServ 16.5 may send password changes "in the clear" through unencrypted email, or that users could send passwords change requests, via email, to the server (not encrypted).
>
> We're using the ListServ on Windows. Does this ever happen, and if so is it possible for any password changes / requests to be initiated through the web interface only, and that it won't accept users trying to change PW via a mail command, and/or won't send passwords unencrypted via email?
>
> Krista Landon
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

I tried the command REP PW XXXXX and REP password XXXXX and even REP XXXXX
and all said "unknown command". I must be using the wrong command or wrong
syntax.
So it is possible for a user to initiate the change by sending the command,
with the password, in the email, correct? Is there any way to not allow
that and to require them to go to the website to initiate that change?

Krista

On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask]>
wrote:

> Assuming that your email clients and servers are using TLS the password
> updates are being end-to-end encrypted by the mail system. Note that
> listserv does not send password changes, it only receives them. However,
> anyone able to log in to the listserv user account can see password updates.
>
> On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask]> wrote:
>
> My company's IT security folks are concerned that ListServ 16.5 may send
> password changes "in the clear" through unencrypted email, or that users
> could send passwords change requests, via email, to the server (not
> encrypted).
>
> We're using the ListServ on Windows. Does this ever happen, and if so is
> it possible for any password changes / requests to be initiated through the
> web interface only, and that it won't accept users trying to change PW via
> a mail command, and/or won't send passwords unencrypted via email?
>
> Krista Landon
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

The command is PW REP.

And you cannot disable the email functions.

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Krista
Sent: Monday, December 13, 2021 12:34 PM
To: [log in to unmask]
Subject: Re: Passwords (do they get sent unencrypted)?

I tried the command REP PW XXXXX and REP password XXXXX and even REP XXXXX and all said "unknown command". I must be using the wrong command or wrong syntax.
So it is possible for a user to initiate the change by sending the command, with the password, in the email, correct? Is there any way to not allow that and to require them to go to the website to initiate that change?

Krista

On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Assuming that your email clients and servers are using TLS the password updates are being end-to-end encrypted by the mail system. Note that listserv does not send password changes, it only receives them. However, anyone able to log in to the listserv user account can see password updates.

On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask]<mailto:[log in to unmask]>> wrote:

My company's IT security folks are concerned that ListServ 16.5 may send password changes "in the clear" through unencrypted email, or that users could send passwords change requests, via email, to the server (not encrypted).

We're using the ListServ on Windows. Does this ever happen, and if so is it possible for any password changes / requests to be initiated through the web interface only, and that it won't accept users trying to change PW via a mail command, and/or won't send passwords unencrypted via email? 

[More ...]

The command is just PW, not REP PW, and you only enter the new one. I don’t know of a way to prevent users from updating their password, but perhaps someone else does.

> On Dec 13, 2021, at 12:33 PM, Krista <[log in to unmask]> wrote:
>
> I tried the command REP PW XXXXX and REP password XXXXX and even REP XXXXX and all said "unknown command". I must be using the wrong command or wrong syntax.
> So it is possible for a user to initiate the change by sending the command, with the password, in the email, correct? Is there any way to not allow that and to require them to go to the website to initiate that change?
>
> Krista
>
> On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask] <mailto:[log in to unmask]>> wrote:
> Assuming that your email clients and servers are using TLS the password updates are being end-to-end encrypted by the mail system. Note that listserv does not send password changes, it only receives them. However, anyone able to log in to the listserv user account can see password updates.
>
>> On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>>
>> My company's IT security folks are concerned that ListServ 16.5 may send password changes "in the clear" through unencrypted email, or that users could send passwords change requests, via email, to the server (not encrypted).
>>
>> We're using the ListServ on Windows. Does this ever happen, and if so is it possible for any password changes / requests to be initiated through the web interface only, and that it won't accept users trying to change PW via a mail command, and/or won't send passwords unencrypted via email?
>>
>> Krista Landon
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> 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>
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

Your IT can disable non-TLS inbound email. That way the entire message, including the password, will be encrypted. This is an easy setting on the mail server; just disable the unencrypted email port. They should do that anyway, because I’m sure there is a huge amount of email both coming and going that includes company-proprietary content.

Larry

> On Dec 13, 2021, at 12:33 PM, Krista <[log in to unmask]> wrote:
>
> I tried the command REP PW XXXXX and REP password XXXXX and even REP XXXXX and all said "unknown command". I must be using the wrong command or wrong syntax.
> So it is possible for a user to initiate the change by sending the command, with the password, in the email, correct? Is there any way to not allow that and to require them to go to the website to initiate that change?
>
> Krista
>
> On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask] <mailto:[log in to unmask]>> wrote:
> Assuming that your email clients and servers are using TLS the password updates are being end-to-end encrypted by the mail system. Note that listserv does not send password changes, it only receives them. However, anyone able to log in to the listserv user account can see password updates.
>
>> On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>>
>> My company's IT security folks are concerned that ListServ 16.5 may send password changes "in the clear" through unencrypted email, or that users could send passwords change requests, via email, to the server (not encrypted).
>>
>> We're using the ListServ on Windows. Does this ever happen, and if so is it possible for any password changes / requests to be initiated through the web interface only, and that it won't accept users trying to change PW via a mail command, and/or won't send passwords unencrypted via email?
>>
>> Krista Landon
>>
>> To unsubscribe from the LSTSRV-L list, click the following link:
>> 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>
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

You probably don't want to do that, because it will also reject non-restricted list mail from non-TLS hosts. Not everyone uses TLS at this point. It's just a fact of life. And that's what opportunistic TLS is for.

For more information about SMTP TLS and LISTSERV, see http://lsoft.com/manuals/lsv-faq/447SMTPTLSandLISTSERV.html

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Lawrence Finch
Sent: Monday, December 13, 2021 12:47 PM
To: [log in to unmask]
Subject: Re: Passwords (do they get sent unencrypted)?

Your IT can disable non-TLS inbound email. That way the entire message, including the password, will be encrypted. This is an easy setting on the mail server; just disable the unencrypted email port. They should do that anyway, because I’m sure there is a huge amount of email both coming and going that includes company-proprietary content.

Larry

On Dec 13, 2021, at 12:33 PM, Krista <[log in to unmask]<mailto:[log in to unmask]>> wrote:

I tried the command REP PW XXXXX and REP password XXXXX and even REP XXXXX and all said "unknown command". I must be using the wrong command or wrong syntax.
So it is possible for a user to initiate the change by sending the command, with the password, in the email, correct? Is there any way to not allow that and to require them to go to the website to initiate that change?

Krista

On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Assuming that your email clients and servers are using TLS the password updates are being end-to-end encrypted by the mail system. Note that listserv does not send password changes, it only receives them. However, anyone able to log in to the listserv user account can see password updates. 

[More ...]

Thank you both. This is great information.
We may want to do this as all email that goes to our ListServ at this point
is from internal network email accounts only (though we have some external
subscribers, who are manually maintained).

I'll talk to the security folks and see just how much they really want this
locked down.

Krista

On Mon, Dec 13, 2021 at 1:07 PM Nathan Brindle <[log in to unmask]> wrote:

> You probably don't want to do that, because it will also reject
> non-restricted list mail from non-TLS hosts. Not everyone uses TLS at this
> point. It's just a fact of life. And that's what opportunistic TLS is for.
>
>
>
> For more information about SMTP TLS and LISTSERV, see
> http://lsoft.com/manuals/lsv-faq/447SMTPTLSandLISTSERV.html
>
>
>
> *From:* LISTSERV Site Administrators' Forum <[log in to unmask]>
> *On Behalf Of *Lawrence Finch
> *Sent:* Monday, December 13, 2021 12:47 PM
> *To:* [log in to unmask]
> *Subject:* Re: Passwords (do they get sent unencrypted)?
>
>
>
> Your IT can disable non-TLS inbound email. That way the entire message,
> including the password, will be encrypted. This is an easy setting on the
> mail server; just disable the unencrypted email port. They should do that
> anyway, because I’m sure there is a huge amount of email both coming and
> going that includes company-proprietary content.
>
>
>
> Larry
>
>
>
> On Dec 13, 2021, at 12:33 PM, Krista <[log in to unmask]> wrote:
>
>
>
> I tried the command REP PW XXXXX and REP password XXXXX and even REP
> XXXXX and all said "unknown command". I must be using the wrong command or
> wrong syntax.
>
> So it is possible for a user to initiate the change by sending the
> command, with the password, in the email, correct? Is there any way to not
> allow that and to require them to go to the website to initiate that change?
>
> Krista
>
>
>
> On Mon, Dec 13, 2021 at 11:55 AM Lawrence Finch <[log in to unmask]>
> wrote:
>
> Assuming that your email clients and servers are using TLS the password
> updates are being end-to-end encrypted by the mail system. Note that
> listserv does not send password changes, it only receives them. However,
> anyone able to log in to the listserv user account can see password updates.
>
>
>
> On Dec 13, 2021, at 11:33 AM, Krista <[log in to unmask]> wrote:
>
>
>
> My company's IT security folks are concerned that ListServ 16.5 may send
> password changes "in the clear" through unencrypted email, or that users
> could send passwords change requests, via email, to the server (not
> encrypted).
>
>
>
> We're using the ListServ on Windows. Does this ever happen, and if so is
> it possible for any password changes / requests to be initiated through the
> web interface only, and that it won't accept users trying to change PW via
> a mail command, and/or won't send passwords unencrypted via email?
>
>
>
> Krista Landon
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
>
>
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>
> ------------------------------
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
>

Since a specific mailing list is affected by this, my guess is that the listowner customized one or more of the web templates for the mailing list, in a way that is not compatible with LISTSERV 17.0.

If you go under ‘List Management’ to ‘Web Templates’ for this mailing list, select ‘All Templates’ as the template category, check the ‘Only Display Modified Templates’ option, and click on ’Select’, then you should see a list of customized templates at the bottom of the page. You can cause a template to revert to the default version by clicking on it, then clicking the ‘Revert’ button on the next page.

-jwgh

> On Dec 8, 2021, at 7:19 PM, Steven J Depinet <[log in to unmask]> wrote:
>
> Greetings,
>
> I recently upgraded to Listserv V17.0, and have had a few issues with the Web Interface, specifically with Subscriber Reports and Subscriber Management. The Subscriber Management issue is for a specific list, when the Owner or myself (the Listserv Admin) try to go to the Subscriber Management for that list, we get:
>
> Error - template TEXT-GLOBAL not found
>
> A configuration error was detected in the CGI script; the TEXT-GLOBAL template could not be found.
> Error - template TEXT-ACTMGR not found
>
> A configuration error was detected in the CGI script; the TEXT-ACTMGR template could not be found.
> Error - template LAYOUT-GLOBAL not found
>
> A configuration error was detected in the CGI script; the LAYOUT-GLOBAL template could not be found.
>
>
> Did I miss something in the upgrade, or are there templates that I need to download or create?
>
> Thanks,
>
> Steven J Depinet Systems Administrator, Sr.
> [log in to unmask] <mailto:[log in to unmask]>
> Information Technology Services
> (928) 523-6843Northern Arizona University
>
>
>
>
>
> To unsubscribe from the LSTSRV-L list, click the following link:
> 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>

Jacob,

MANY thanks for the direct. I was able to find the offending Template, and identified those 3 missing templates. I may need to go back to the release notes to see if they have been replaced or renamed, I do see some similarly named templates. So even though I know nothing about Listserv Web Templates, I believe that I can help the List Owner determine the best course of action based on what you’ve said.

Steven J Depinet Systems Administrator, Sr.
[log in to unmask]<mailto:[log in to unmask]> Information Technology Services
(928) 523-6843Northern Arizona University

On Dec 8, 2021, at 9:40 PM, Jacob Haller <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Since a specific mailing list is affected by this, my guess is that the listowner customized one or more of the web templates for the mailing list, in a way that is not compatible with LISTSERV 17.0.

If you go under ‘List Management’ to ‘Web Templates’ for this mailing list, select ‘All Templates’ as the template category, check the ‘Only Display Modified Templates’ option, and click on ’Select’, then you should see a list of customized templates at the bottom of the page. You can cause a template to revert to the default version by clicking on it, then clicking the ‘Revert’ button on the next page.

-jwgh

On Dec 8, 2021, at 7:19 PM, Steven J Depinet <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Greetings,

I recently upgraded to Listserv V17.0, and have had a few issues with the Web Interface, specifically with Subscriber Reports and Subscriber Management. The Subscriber Management issue is for a specific list, when the Owner or myself (the Listserv Admin) try to go to the Subscriber Management for that list, we get: 

[More ...]

Not having the issue that you describe. Just implemented ListServ V17 on a brand new 2019 Windows server.

[cid:a06f7abc-780e-46ec-901a-868452c9d593]

Kevin E. Zeitz
Systems Engineer

Technology Services Group
Carilion Clinic
451 Kimball Avenue
Roanoke, VA 24016
Email: [log in to unmask]<mailto:[log in to unmask]>
Phone: 540.224.4164 I Fax: 540.857.5455 I Mobile: 540.529.5969

I had that problem and if I remember correctly, it turned out to be a folder permissions issue.

Krista Landon

Thanks for the responses with this - not quite there yet but making progress,

regards

From: LISTSERV Site Administrators' Forum <[log in to unmask]> On Behalf Of Landon, Krista J
Sent: Thursday, 30 September 2021 9:39 PM
To: [log in to unmask]
Subject: Re: Listserv v17\ IIS 10 configuration issue

You don't often get email from [log in to unmask]<mailto:[log in to unmask]>. Learn why this is important<http://aka.ms/LearnAboutSenderIdentification>

[External Email] This email was sent from outside the organisation - be cautious, particularly with links and attachments.
I had that problem and if I remember correctly, it turned out to be a folder permissions issue.

Krista Landon

On Sep 29, 2021, at 7:27 PM, Steven J Depinet <[log in to unmask]> wrote:

> Greetings,
>
> We’re running Listserv V16.0/V16.5 on RedHat 6 (RHEL6), which is scheduled for upgrade to Listserv V17.0, and RHEL7.
>
> I have a list on Listserv that is Moderated, with Moderator=All,addr1,addr2,addr3, and Send= Editor,Hold,Confirm. The moderators are the same as the Editors. A couple of times recently, they got an attempt to post, from outside the University, and each Moderator received the Notification that there was a message to be moderated, but when they go to the List Moderation Web Page, there is no message to be confirmed or denied.
>
> First question is: How long do messages remain viable to be Released or Denied? The manual says that they time out, but I have been unable to find where this limit is specified (or set).

One week. This period of time can be increased but not decreased — see http://www.lsoft.com/manuals/17.0/listkwd/kConfirmDelay.html for details.

> Second, Why would a message not be listed, even though still viable? A message was waiting for Moderation, but not visible in the List Moderation page, andaccidentally released by a click on the link in the message that a Moderator received. The person who clicked has full Listserv Administration permissions, but did not realize that the click would release the message, they thought it would take them to the Moderation page (they had received a copy of the request for release from one of the Moderators).

If a message isn’t listed on the moderation page, that typically would mean one the following. 

[More ...]

Jacob & Bill,

Thanks for the replies. I personally am not the Moderator of that list, and so when I go to the “List Moderation” page, do not see the post, but I do get the “Search Options:” with “All Moderated Lists”, and when I check that and hit “refresh”, get the “All Moderators” Checkbox. And, when I check that box (“All Moderators”), and hit “Refresh”, I see the message that seemed to disappear. And am able to discard that message.

However, the Moderator, who claims to be logged into Listserv with the email address that is listed as a Moderator in the List Header, not only does not see the message, he also does not have the “Search Options:” . Either in “Basic Mode”, or in “Expert Mode”. I did not have him try Tutorial Mode, as I have the “Search Options:” in either Basic or Expert Mode. So, How do I get that feature for the List Moderator? Or, is it limited to Admins?

Steven J Depinet Systems Administrator, Sr.
[log in to unmask]<mailto:[log in to unmask]> Information Technology Services
(928) 523-6843Northern Arizona University

On Sep 30, 2021, at 8:09 AM, Jacob Haller <[log in to unmask]<mailto:[log in to unmask]>> wrote:

On Sep 29, 2021, at 7:27 PM, Steven J Depinet <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Greetings,

We’re running Listserv V16.0/V16.5 on RedHat 6 (RHEL6), which is scheduled for upgrade to Listserv V17.0, and RHEL7.

I have a list on Listserv that is Moderated, with Moderator=All,addr1,addr2,addr3, and Send= Editor,Hold,Confirm. The moderators are the same as the Editors. A couple of times recently, they got an attempt to post, from outside the University, and each Moderator received the Notification that there was a message to be moderated, but when they go to the List Moderation Web Page, there is no message to be confirmed or denied. 

[More ...]

On Sep 30, 2021, at 2:46 PM, Steven J Depinet <[log in to unmask]> wrote:

> Jacob & Bill,
>
> Thanks for the replies. I personally am not the Moderator of that list, and so when I go to the “List Moderation” page, do not see the post, but I do get the “Search Options:” with “All Moderated Lists”, and when I check that and hit “refresh”, get the “All Moderators” Checkbox. And, when I check that box (“All Moderators”), and hit “Refresh”, I see the message that seemed to disappear. And am able to discard that message.
>
> However, the Moderator, who claims to be logged into Listserv with the email address that is listed as a Moderator in the List Header, not only does not see the message, he also does not have the “Search Options:” . Either in “Basic Mode”, or in “Expert Mode”. I did not have him try Tutorial Mode, as I have the “Search Options:” in either Basic or Expert Mode. So, How do I get that feature for the List Moderator? Or, is it limited to Admins?

If the message was sent to them for moderation, and has not yet been approved or rejected, then it should show up on the moderation page when they logged in — so I recommend making extra sure that the email address in the ‘Moderator=‘ setting matches exactly the one that they are using when they are logging into LISTSERV’s web interface. If someone has two similar but distinct email addresses, then this sort of thing can be easy to overlook. 

[More ...]

Thanks again for your attention, especially, Jacob,

Could that “difference” in email addresses go so far as to including case sensitivity?

Ie: In the list header, the Moderator= All,[log in to unmask]<mailto:[log in to unmask]>,[log in to unmask]<mailto:[log in to unmask]>, etc. is specified with the first letter of his name capitalized, and the Listserv log shows the confirmation request being sent to [log in to unmask]<mailto:[log in to unmask]>.
However, when he logged into the Web Interface, he signed in as: [log in to unmask]<mailto:[log in to unmask]>, which is also reflected in the Listserv log. So his X-LOGIN was all lowercase, but the Moderator keyword uses capital letters for the first letter of his first name and the first letter of his last hame. I’ve confirmed that Listserv doesn’t care about case sensitivity while logging in, but does it matter when comparing to the Moderator keyword?

That case difference is the only one that I can find… When I login, as [log in to unmask]<mailto:[log in to unmask]>, I seem to get the same treatment as I do when I login as [log in to unmask]<mailto:[log in to unmask]>, as I would expect… But the log does show the difference.

I still don’t understand why he doesn’t get the “Search Options”...

Steven J Depinet Systems Administrator, Sr.
[log in to unmask]<mailto:[log in to unmask]> Information Technology Services
(928) 523-6843Northern Arizona University

On Sep 30, 2021, at 4:39 PM, Jacob Haller <[log in to unmask]<mailto:[log in to unmask]>> wrote:

On Sep 30, 2021, at 2:46 PM, Steven J Depinet <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Jacob & Bill,

Thanks for the replies. I personally am not the Moderator of that list, and so when I go to the “List Moderation” page, do not see the post, but I do get the “Search Options:” with “All Moderated Lists”, and when I check that and hit “refresh”, get the “All Moderators” Checkbox. And, when I check that box (“All Moderators”), and hit “Refresh”, I see the message that seemed to disappear. And am able to discard that message. 

[More ...]

On Sep 30, 2021, at 8:38 PM, Steven J Depinet <[log in to unmask]> wrote:

> Thanks again for your attention, especially, Jacob,
>
> Could that “difference” in email addresses go so far as to including case sensitivity?
>
> Ie: In the list header, the Moderator= All,[log in to unmask] <mailto:[log in to unmask]>,[log in to unmask] <mailto:[log in to unmask]>, etc. is specified with the first letter of his name capitalized, and the Listserv log shows the confirmation request being sent to [log in to unmask] <mailto:[log in to unmask]>.
> However, when he logged into the Web Interface, he signed in as: [log in to unmask] <mailto:[log in to unmask]>, which is also reflected in the Listserv log. So his X-LOGIN was all lowercase, but the Moderator keyword uses capital letters for the first letter of his first name and the first letter of his last hame. I’ve confirmed that Listserv doesn’t care about case sensitivity while logging in, but does it matter when comparing to the Moderator keyword?

In some circumstances, LISTSERV does pay attention to the case of an email address’s local part (that is, the part before the @), as the relevant standards do consider email addresses to potentially be distinct even if they only differ by case. (The domain part of the email address is required to be treated case insensitively, though.)

With that said, I wouldn’t expect LISTSERV to care about the case of a logged-in email address, in terms of determining what rights that address has.

With that said, I think it’s worth trying out changing the ‘Moderator=‘ setting so that the email address’s case matches what they’re using when they log in, to see if that fixes the problem. If it does, then great — and, if not, then you’ve at least eliminated that as a possible factor. They might have to log out and back in after you make the change. 

[More ...]

Jacob,

Thanks for that info and suggestion, I was planning on trying that. Not that it matters past this evening (I’m upgrading to V17.0 tonight after business hours), but the “Search Options:” is the header above "All Moderated Lists”, and (after clicking on that, and hitting “Refresh”), “All Moderators”."

Steven J Depinet Systems Administrator, Sr.
[log in to unmask]<mailto:[log in to unmask]> Information Technology Services
(928) 523-6843Northern Arizona University

On Oct 1, 2021, at 8:10 AM, Jacob Haller <[log in to unmask]<mailto:[log in to unmask]>> wrote:

On Sep 30, 2021, at 8:38 PM, Steven J Depinet <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Thanks again for your attention, especially, Jacob,

Could that “difference” in email addresses go so far as to including case sensitivity?

Ie: In the list header, the Moderator= All,[log in to unmask]<mailto:[log in to unmask]>,[log in to unmask]<mailto:[log in to unmask]>, etc. is specified with the first letter of his name capitalized, and the Listserv log shows the confirmation request being sent to [log in to unmask]<mailto:[log in to unmask]>.
However, when he logged into the Web Interface, he signed in as: [log in to unmask]<mailto:[log in to unmask]>, which is also reflected in the Listserv log. So his X-LOGIN was all lowercase, but the Moderator keyword uses capital letters for the first letter of his first name and the first letter of his last hame. I’ve confirmed that Listserv doesn’t care about case sensitivity while logging in, but does it matter when comparing to the Moderator keyword?

In some circumstances, LISTSERV does pay attention to the case of an email address’s local part (that is, the part before the @), as the relevant standards do consider email addresses to potentially be distinct even if they only differ by case. (The domain part of the email address is required to be treated case insensitively, though.) 

[More ...]