Hi all,
I am trying (and so far failing miserably) to set my VPS up to handle
mail. It only has to forward mail for about 5 domains.
google is rejecting everything, and I don't understand why.
According to this page https://support.google.com/a/answer/81126 I must
authenticate with EITHER spf or DKIM.
According to https://easydmarc.com/tools/spf-lookup?domain=ianhobson.com
the spf is set up correctly, and it has been for well over the TTL of 1
hour.
However when I send hobson42(a)gmail.com a message, from
ian(a)ianhobson.com, I get the following log entries...
2025-02-22T12:14:14.865917+00:00 ianhobson postfix/cleanup[4869]:
D306590480: message-id=<20250222121414.D306590480(a)ianhobson.com>
2025-02-22T12:14:14.868393+00:00 ianhobson postfix/qmgr[4763]:
D306590480: from=<>, size=3366, nrcpt=1 (queue active)
2025-02-22T12:14:14.870663+00:00 ianhobson postfix/bounce[4872]:
533129047F: sender non-delivery notification: D306590480
2025-02-22T12:14:14.870988+00:00 ianhobson postfix/qmgr[4763]:
533129047F: removed
2025-02-22T12:14:15.257167+00:00 ianhobson postfix/smtp[4871]:
D306590480: to=<hobson42(a)gmail.com>, orig_to=<ian(a)ianhobson.com>,
relay=gmail-smtp-in.l.google.com[64.233.184.27]:25, delay=0.39,
delays=0/0/0.08/0.3, dsn=5.7.26, status=bounced (host
gmail-smtp-in.l.google.com[64.233.184.27] said: 550-5.7.26 Your email
has been blocked because the sender is unauthenticated. 550-5.7.26 Gmail
requires all senders to authenticate with either SPF or DKIM. 550-5.7.26
550-5.7.26 Authentication results: 550-5.7.26 DKIM = did not pass
550-5.7.26 SPF [] with ip: [85.119.82.117] = did not pass 550-5.7.26
550-5.7.26 For instructions on setting up authentication, go to 550
5.7.26 https://support.google.com/mail/answer/81126#authentication
ffacd0b85a97d-38f25a3ee76si17083121f8f.811 - gsmtp (in reply to end of
DATA command))
2025-02-22T12:14:15.259036+00:00 ianhobson postfix/qmgr[4763]:
D306590480: removed
If I read this correctly, spf authentication failed.
The spf entry is TXT, NAME=@ DATA="v=spf1 ~all" no quotes.
Anyone got any idea what might be happening?
Regards
Ian
--
Ian Hobson
Tel (+66) 626 544 695
Hi,
Stripe have been in touch to let us know that they plan to automatically
convert us to their "Adaptive Pricing" plan from 18 March.
https://support.stripe.com/questions/adaptive-pricing
From what I can tell this means they will guess what your local currency
is and charge you in that rather than GBP, and you will pay (them) 4%
extra for that.
The FAQ page above does say that it will be optional at the point of
sale:
Example:
If the mid-market exchange rate is $1 = €1, and a US merchant sells
a $100 item to a German customer, the exchange rate applied will
include a 4% conversion fee ($1 = €1.04). In this case, the customer
will be presented with the option to pay $100 or €104. Regardless of
the customer’s currency selection, the merchant will receive $100.
(€104 / 1.04), less applicable Stripe processing fees.
I do not yet know how that interacts with the majority of our payments,
which are automated and you give consent for at the time that the card
is added. Perhaps they will ask at that point, or perhaps this will not
be applied to such charges. I have to check into that more.
But what are your thoughts?
I feel like 4% is a bad deal for almost everyone, in that almost
everyone who cares about what non-local payments cost them is able to
get a card that charges them less than 4% — and in many cases nothing
extra.
However, perhaps there are people with a worse deal.
The option is apparently presented to the buyer, but I still don't like
that it's opt out for the buyer also.
We can opt out but then no one gets the choice.
I worry that those who don't care will not feel anything while those
who do care will be disappointed that the bad deal has to be opted out
of and may even feel like this is some sort of scam, thinking that
BitFolk would get the 4%. If that is the case this would be lose/lose
for us and we should opt out.
What are your thoughts?
Is there actually anyone who ends up paying 4% or more to pay in GBP on
their card?
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
A customer running multiple Ubuntu 24.04 VPSes has reported problems
with a recent grub package update which gives this error:
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
and then fails to complete the update, leaving dpkg in an unhappy state.
This is the first report we have seen of this. I am about to try to
replicate it. Is anyone else experiencing it?
I have a working theory that grub has become more strict and when it is
instal;led on a disk with a GPT (rather than a legacy MBR) it wants to
see an actual partition of code type EF02 "BIOS boot partition" rather
than simply the 4MiB of empty space we have been leaving at the start of
your xvda disk.
If that theory is correct then:
- It may be tricky to fix for existing VPSes
- It's an unfortunate change to introduce during an LTS release (i.e.
this worked when 24.04 was released)
But for now if you are affected I would just like you to get in touch
with me off-list.
While this is irritating and possibly awkward to fix, I don't think it
will end up as a critical issue as we don't actually need grub installed
to boot your VPS, only a grub.cfg that looks correct. It's just that the
easiest way to get that is to properly install grub.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
It was pointed out to us that the HTTPS checks on our monitoring system
were only checking for a valid TLS certificate, not for a success code
from the URL. e.g. serving a completely secure 503 error page would
result in an "OK" check result.
This morning at around 09:55 we fixed that so that the HTTPS checks are
really checking the status code of the URL supplied. This has caused a
few new alerts to start being sent to people.
By fixing that, TLS certificate validity is now NOT being checked. We
will shortly add an additional check for this. You don't have to do
anything.
HTTPS and many other checks through our monitoring system are available
free upon request.
https://tools.bitfolk.com/wiki/Monitoring
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
At approximately 00:03Z we start receiving alerts of various services
not responding and it was determined that host talisker was having some
problems with its storage.
There were lots of errors being spewed into the kernel log from the SAS
controller's driver mostly of a timeout variety, and none of the drives
attached to it were responding. A number of its MD RAID arrays fell
apart as a result and IO errors would have been seen inside your virtual
machines.
I did try a few things around resetting the controller but nothing
worked so at around 00:35 I had to forcibly kill all running VPSes and
reboot the host, which happened at about 00:29.
The host talisker booted without incident and all its RAID arrays synced
up. By around 00:39 all customer VPSes should have booted, and all those
we have monitoring for did show as up by then.
Due to abruptly losing access to storage, some data in memory will have
been lost, but hopefully apps are aware of that. I do not think any
reads or writes were corrupted so I don't think there should be any
filesystem corruption. If you are seeing any problems and your VPS is
actually on talisker than you should first have a look at your Xen
Shell consoles.
Apologies for the disruption. We will keep an eye on talisker to gain
some assurance that this was a one-off event.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
