Hi Bogdan, Our understanding is that the change is actually a fix and reversing it would cause problems for an increasingly large percentage of email users. The problem is that if a sender's email client/server signs the message (increasingly common with DKIP) and then the list server edits the subject line to add the "[discuss-gnuradio] " prefix then the signature is invalid and some popular mail servers will penalize the message when it evaluates it as being spam. Some servers simply reject the message silently.
All discuss-gnuradio emails do correctly have the list-id header in the metadata so it is easy to filter them into a folder or add a label. Since there is a standards compliant way of identifying the discuss-gnuradio messages it's unlikely that we'll change the server setting back to adding the prefix. If the behavior of email clients/servers change or a best-practices guidance comes out with a way of retaining the prefix we'll move to the most compliant behavior. Regards, Derek On 18/11/2019 09:37, Bogdan Diaconescu wrote: > Hi Markus, I know it might take some effort to fix the issue and if it helps > I will just say that missing the preamble is really annoying as many of us > are subscribed to other email groups with missing preamble. That creates a > really confusing situations. > > Bogdan > >> On 17 Nov 2019, at 20:54, Müller, Marcus (CEL) <muel...@kit.edu> wrote: >> >
