On Sat, 19 Jun 2021, at 17:04, Paul Gilmartin wrote: > On Sat, 19 Jun 2021 16:23:05 +0100, Jeremy Nicoll wrote: > > > >> Can it [EXTERNAL] be suppressed? > > > >Only if the listserv has configurable Subject editing, I expect ... > >or if it can be forced to reinstate the original subject in every > >reply it sends out. And that would be a problem when the > >discussions go off-topic and people edit the Subject: usefully. > > > It shouldn't be LISTSERV's responsibility,
Of course not, but at least all the mails the listserv is processing do get processed by the listserv, so it has the opportunity. > but the originating client's. I doubt it's anyone's client that's the issue. I would think it's more likely to be happening at some organisation's incoming mail server as mails for that company's users are delivered to it. If that's the case, the chance of anyone persuading whoever runs their mail infrastructure to remove the (presumably thought useful) warning that a mail arrived from somewhere outside the organisation ... is probably nil. And it shouldn't make unconventional modifications > to standard headers. Better to add something such as: > X-Sourrce: EXTERNAL But that would be no use to a user then displaying that email. I expect the whole point is for them to be reminded that such mails are more likely to contain dodgy links / attachments. > Or, the client's MUA could flag the message in the local display > triggered by content found in Received: headers. Maybe whichever organisation(s) do this find it simpler just to alter the subject ... so that it doesn't matter what client a user uses after that? -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
