----- Forwarded message from "sunebeck ." <sunebeck@gmail.com> -----
Date: Fri, 12 Jan 2018 09:20:03 +0100
From: "sunebeck ." <sunebeck@gmail.com>
Subject: Fwd: Delivery Status Notification (Delay)
To: Ben Green <ben@bristolwireless.net>
Hi Ben!
Just FYI the Linux-Vserver mailing list still refuses mail from Gmail.
Do you know who's the administrator of it?
I'd remove SORBS from the list, it's anyway a questionable DNSBL.
Sune
attached mail follows:
Hi Ben!
Just FYI the Linux-Vserver mailing list still refuses mail from Gmail.
Do you know who's the administrator of it?
I'd remove SORBS from the list, it's anyway a questionable DNSBL.
Sune
---------- Forwarded message ----------
From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
Date: Thu, Jan 11, 2018 at 6:54 AM
Subject: Delivery Status Notification (Delay)
To: sunebeck@gmail.com
[image: Error Icon]
Delivery incomplete
There was a temporary problem delivering your message to
*vserver@list.linux-vserver.org*. Gmail will retry for 20 more hours.
You'll be notified if the delivery fails permanently.
LEARN MORE <http://www.sorbs.net/lookup.shtml?209.85.215.41>
[image: Warning] This link will take you to a third-party site
The response was:
451 Currently Sending Spam See: http://www.sorbs.net/lookup.
shtml?209.85.215.41
Final-Recipient: rfc822; vserver@list.linux-vserver.org
Action: delayed
Status: 4.0.0
Remote-MTA: dns; list.linux-vserver.org. (213.145.232.38, the server for the
domain list.linux-vserver.org.)
Diagnostic-Code: smtp; 451 Currently Sending Spam See:
http://www.sorbs.net/lookup.shtml?209.85.215.41
Last-Attempt-Date: Wed, 10 Jan 2018 21:54:06 -0800 (PST)
Will-Retry-Until: Thu, 11 Jan 2018 18:45:56 -0800 (PST)
---------- Forwarded message ----------
From: "sunebeck ." <sunebeck@gmail.com>
To: vserver@list.linux-vserver.org
Cc:
Bcc:
Date: Tue, 9 Jan 2018 03:45:26 +0100
Subject: Meltdown/Spectre and Linux-Vserver
Hi Mailing List,
I suppose Vserver users are as exposed as any other Debian user in regards
to the recent Meltdown/Spectre vulnerabilities.
Did anyone try and apply the Vserver patch to one of the already-updated
Debian kernels?
Here's Debian's status page for the issue:
<https://security-tracker.debian.org/tracker/CVE-2017-5754>
Sune
