Andy, do you run a mail relay/smarthost for customers?
I've got nullmailer running on one of my VPS, and it looks like I
configured it with a bitfolk.com smarthost, but it doesn't dig/accept SMTP
(so I'm guessing it either used to exist and doesn't any more, or it never
existed and I just made some shit up)
Kind regards
Murray Crane
I am running debian 9 on my vps. Filesystem is ext3.
I have cron jobs which drop database dumps into a dropbox folder.
In addition I have created some shared folders so that non techies can
upload material.
However Dropbox are dropping support for ext3 this will be broken soon.
What's my best option here.
Migrate the entire VPS to ext4?
Create a new (ext4) partition?
Something else.
I note from
https://debian-administration.org/article/643/Migrating_a_live_system_from_…
that it is possible to switch from ext3 to ext4 without any conversion by
simply editing the fstab and rebooting.
Does anyone know if that will suffice for Dropbox's new requirements? I
suspect not. :(
Neil Wallace.
I currently relay email for a customer who has a Hetzner server [1].
We had problems sending email as we share an IP address block
with habitual spammers (OSLT - much argument on the mail operator's
mailing list - basically, live next to noisy neighbours, you might
find yourself with an ASBO).
So I relay his mail (obvs., not an *open* relay!).
I used verifier.port25.com and got a fail on the reverse IP
lookup, as they use IPv6.
Bitfolk.com says:
"For IPv6 we can delegate the IPv6 reverse zones to your nameservers. We
can also provide up to three secondary nameservers for you."
and the domain is registered and has DNS provided by 123-reg. Which
doesn't seem to know about IPv6.
Do I have any other options apart from using a different DNS provider?
Or moving the domain away from 123-reg?
[1] Only place I know of where you can get 12TB of disk for "not
too much". We need lots of disk!
Hi,
Has anyone else been seeing (what appears to be) DDOS attempts against
their VPS's?
I've been getting quite a lot of messages like this in my logs over the
past few days:
Sep 30 05:02:06 scruffy kernel: [2103474.700870] TCP: drop open request
from 45.195.133.8/51353
Sep 30 05:02:07 scruffy kernel: [2103476.223611] TCP: drop open request
from 149.56.180.255/25006
Sep 30 05:02:08 scruffy kernel: [2103476.704225] TCP: drop open request
from 45.195.133.8/7947
Sep 30 05:02:08 scruffy kernel: [2103476.713872] TCP: drop open request
from 149.56.180.255/31127
Any ideas also on the best way to block? (I was reading about SYN
cookies, but not sure if this is a good idea or not).
cheers,
Matt.
