Quoting golinux@??? (golinux@???):
> This email does not address the content of this email but rather
> something very strange that came through in the header:
>
> https://dev1galaxy.org/files/cruft.png
>
> This started with the above email from Steve.
I'll retain for a while that verbatim message from Steve Litt, in case
you and I need to discuss it. E.g, I could put the full headers as seen
here into Pastebin. To be clear, as received here, Steve's mail and all
the others recently (received from Dng) look just fine as received here.
Locally on linuxmafia.com, all the mail from my Devuan mailing list
subscriptions arrive at my SMTP daemon (Exim4), get handed off to
Procmail as Local Delivery Agent, and get appended to mbox file
/home/rick/inboxes/lists . And the contents (including recently arrived
mails including Steve's) look correct and properly formatted both when
viewed using a terminal pager such as /usr/bin/less or when viewed using
my preferred Mail User Agent (mail client), mutt.
I notice that your own headers include:
User-Agent: Dyne.org Webmail
This raises the probably unwelcome and very annoying possibility that
the program referenced had a parsing problem on one or more recently
arrived pieces of mail.
If you can get the attention of someone who has local administrative
access (at the shell) on the dyne.org host, he/she could take a look at
whatever mailbox file this 'Dyne.org Webmail' program relies on for your
mail -- to see if there's any obvious corruption in the file as stored
locally (your Inbox folder, I mean). Maybe it's an mbox file (or a
Maildir directory tree). Either of those is pretty easy to expunge file
corruption from.
But also, something is confusing me, here:
> Here's the complete header. Problem is under "Precedence: list":
> Return-Path: <dng-bounces@???>
> Delivered-To: golinux@???
[big snip]
> Precedence: list
> List-Id: "The first mailinglist after debianfork.org"
> <dng.lists.dyne.org>
> List-Unsubscribe:
> <https://mailinglists.dyne.org/cgi-bin/mailman/options/dng>,
> <mailto:dng-request@lists.dyne.org?subject=unsubscribe>
> List-Archive:
> <https://mailinglists.dyne.org/cgi-bin/mailman/private/dng/>
> List-Post: <mailto:dng@lists.dyne.org>
> List-Help: <mailto:dng-request@lists.dyne.org?subject=help>
> List-Subscribe:
> <https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng>,
> <mailto:dng-request@lists.dyne.org?subject=subscribe>
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
> Errors-To: dng-bounces@???
> Sender: "Dng" <dng-bounces@???>
Um... nothing there looks corrupted in any way, to my eyes.
If 'Dyne.org Webmail' cannot parse that correctly, then IMO it has a
big (parsing) problem. That's a bog-standard set of headers.
::
Re: [DNG] I wrote IBM
:%0A>%20%0A>%20>%20This%20email%20does%20not%20address%20the%20content%20of%20this%20email%20but%20rather%0A>%20>%20something%20very%20strange%20that%20came%20through%20in%20the%20header:%0A>%20>%20%0A>%20>%20https://dev1galaxy.org/files/cruft.png%0A>%20>%20%0A>%20>%20This%20started%20with%20the%20above%20email%20from%20Steve.%0A>%20%0A>%20I'll%20retain%20for%20a%20while%20that%20verbatim%20message%20from%20Steve%20Litt,%20in%20case%0A>%20you%20and%20I%20need%20to%20discuss%20it.%20%20E.g,%20I%20could%20put%20the%20full%20headers%20as%20seen%0A>%20here%20into%20Pastebin.%20%20To%20be%20clear,%20as%20received%20here,%20Steve's%20mail%20and%20all%0A>%20the%20others%20recently%20(received%20from%20Dng)%20look%20just%20fine%20as%20received%20here.%0A>%20%0A>%20Locally%20on%20linuxmafia.com,%20all%20the%20mail%20from%20my%20Devuan%20mailing%20list%0A>%20subscriptions%20arrive%20at%20my%20SMTP%20daemon%20(Exim4),%20get%20handed%20off%20to%0A>%20Procmail%20as%20Local%20Delivery%20Agent,%20and%20get%20appended%20to%20mbox%20file%0A>%20/home/rick/inboxes/lists%20.%20%20And%20the%20contents%20(including%20recently%20arrived%0A>%20mails%20including%20Steve's)%20look%20correct%20and%20properly%20formatted%20both%20when%0A>%20viewed%20using%20a%20terminal%20pager%20such%20as%20/usr/bin/less%20or%20when%20viewed%20using%0A>%20my%20preferred%20Mail%20User%20Agent%20(mail%20client),%20mutt.%0A>%20%0A>%20I%20notice%20that%20your%20own%20headers%20include:%0A>%20%0A>%20User-Agent:%20Dyne.org%20Webmail%0A>%20%0A>%20This%20raises%20the%20probably%20unwelcome%20and%20very%20annoying%20possibility%20that%0A>%20the%20program%20referenced%20had%20a%20parsing%20problem%20on%20one%20or%20more%20recently%0A>%20arrived%20pieces%20of%20mail.%0A>%20%0A>%20If%20you%20can%20get%20the%20attention%20of%20someone%20who%20has%20local%20administrative%0A>%20access%20(at%20the%20shell)%20on%20the%20dyne.org%20host,%20he/she%20could%20take%20a%20look%20at%0A>%20whatever%20mailbox%20file%20this%20'Dyne.org%20Webmail'%20program%20relies%20on%20for%20your%0A>%20mail%20--%20to%20see%20if%20there's%20any%20obvious%20corruption%20in%20the%20file%20as%20stored%0A>%20locally%20(your%20Inbox%20folder,%20I%20mean).%20%20Maybe%20it's%20an%20mbox%20file%20(or%20a%0A>%20Maildir%20directory%20tree).%20%20Either%20of%20those%20is%20pretty%20easy%20to%20expunge%20file%0A>%20corruption%20from.%0A>%20%0A>%20%0A>%20But%20also,%20something%20is%20confusing%20me,%20here:%0A>%20%0A>%20>%20Here's%20the%20complete%20header.%20%20Problem%20is%20under%20%22Precedence:%20list%22:%0A>%20%0A>%20>%20Return-Path:%20<dng-bounces@???>%0A>%20>%20Delivered-To:%20golinux@???%0A>%20%5Bbig%20snip%5D%0A>%20%0A>%20%0A>%20Um...%20nothing%20there%20looks%20corrupted%20in%20any%20way,%20to%20my%20eyes.%0A>%20If%20'Dyne.org%20Webmail'%20cannot%20parse%20that%20correctly,%20then%20IMO%20it%20has%20a%0A>%20big%20(parsing)%20problem.%20%20That's%20a%20bog-standard%20set%20of%20headers.%0A>%20%0A>%20%0A>%20 "Nachricht beantworten")
