Hi,
Yahoo! have made a change to their DMARC settings in a way that is
incompatible with how Internet mailing lists tend to operate. As a
result it is likely that members of this list (5 of you) with a
Yahoo! email account will start to cause email delivery issues for
others subscribers.
As this is not something that we can easily fix, and represents a
failure to understand how the Internet works on Yahoo!'s part, I
have had to moderate those 5 members. My best suggestion is for
those affected to change email address if you wish to continue
posting to this and other mailing lists.
Sorry about that.
The technical issue is that Yahoo! now requires that all email with
a Yahoo! email address as its From: address to have originated on
Yahoo!'s network.
Mailing lists relay mail on behalf of users, using their own
envelope sender address in order to catch bounces, but keeping the
original's From: address. As a result they send email that appears
to be from an individual, but originates elsewhere.
Yahoo!'s current DMARC settings cause sites that use DMARC to reject
such emails. Unfortunately this is not just limited to Yahoo!. It
includes Gmail, Hotmail, Comcast and other large email providers. So
if a Yahoo! user sends an email to this list, multiple subscribers
will reject it. This will go to bounce processing and ultimately may
start kicking people off the list.
Some more info:
http://www.ietf.org/mail-archive/web/ietf/current/msg87153.htmlhttp://www.theregister.co.uk/2014/04/08/yahoo_breaks_every_mailing_list_in_…http://www.computerworld.com/s/article/9247512/Yahoo_email_anti_spoofing_po…
Once you've changed address you can re-subscribe from here:
https://lists.bitfolk.com/mailman/listinfo/users
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
> I'd be interested to hear any (even two word) reviews of their sofas…
Provides seating. — Andy Davidson
Greetings
Anyone else who have gotten the cold hand from Google while connecting
by way of Bitfolk's IPv6 range?
I have recently started using my Bitfolk VPS as a VPN, and while
connecting through it I'm not allowed to login to Google Apps.
I can access the https://accounts.google.com/ login page, but I soon as
I enter my credentials I end up at
https://accounts.google.com/RestrictedCountry, which then points me to
the https://support.google.com/a/answer/2891389 help page.
This problem goes away if I force IPv4.
The unwelcome IPv6 address being 2001:ba8:1f1:c10::1000.
The much more welcome IPv4 address being 85.119.83.127.
// Andreas
When installing a new kernel (CentOS in this case) I've always done a full
shutdown and boot from the console following the advice on the Customer
Information page. However, this time I accidentally did a "shutdown -r" but
it did actually pick up the new kernel.
Have improvements in Xen made the advice redundandant?
Thanks,
Mike
Hi,
I've seen a bunch of scans for this exploit across my hosts, and
have already heard of some hosts compromised by it:
http://seclists.org/fulldisclosure/2014/Apr/240
So if you run Nagios NRPE, please make sure to:
- Firewall it off appropriately
- Use its config options for restricting who can talk to it
- Disable client specification of command arguments if possible
- Upgrade to a fixed version
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hello,
If you've been reading tech news in the last 24 hours then you're
probably aware of "heartbleed", but if not then you will want to
have a read of:
http://heartbleed.com/
and take appropriate action.
If you trust this site you can use it to check if your HTTPS server
is vulnerable or not:
http://filippo.io/Heartbleed/
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
636 - ldaps (caught me out at work)
Cheers,
Alun.
--
Sorry for any typos - sent from my phone
Andy Smith <andy(a)bitfolk.com> wrote:
>On Thu, Apr 10, 2014 at 06:31:42PM +0000, Andy Smith wrote:
>> We're going to do some scans of our IPv4 space to look for services
>> vulnerable to the OpenSSL "heartbleed" vulnerability, so we can open
>> tickets with customers about it¹.
>
>The first round of these tickets has now been created, so if you
>didn't get one that means:
>
>- Congratulations, you weren't vulnerable! Or;
>- We missed something, or;
>- Our email (from support(a)bitfolk.com) went into your spam folder
>
>At the moment we are only checking ports: 25, 443, 465, 587, 993,
>995, 8443. Can you think of any others that are likely to have SSL
>services on?
>
>I'll save further discussion for the users list from now on.
>
>Cheers,
>Andy
>
>--
>http://bitfolk.com/ -- No-nonsense VPS hosting
>
>_______________________________________________
>announce mailing list
>announce(a)lists.bitfolk.com
>https://lists.bitfolk.com/mailman/listinfo/announce
>
>_______________________________________________
>users mailing list
>users(a)lists.bitfolk.com
>https://lists.bitfolk.com/mailman/listinfo/users
On 11 April 2014 09:00, <users-request(a)lists.bitfolk.com> wrote:
> We're going to do some scans of our IPv4 space to look for services vulnerable to the OpenSSL "heartbleed" vulnerability, so we can open tickets with customers about it?
http://www.theregister.co.uk/2014/04/11/heartbleed_health_checking_services…
I hope nobody calls the police :) Just in case I confirm my explicit permission.
Steve
