Hello all,
Wondering if any of you have experience with this.
I have two domains, wiggly.org (A) and alertferret.com (B).
A has been registered since 1994.
B was registered very recently, within 6 months.
I run email for both of these domains on the same server,
otter.wiggly.org using Exim.
I have the exact same MX and SPF records for both domains;
@ 3600 IN MX 10 mail.wiggly.org.
@ 3600 IN SPF "v=spf1 mx -all"
@ 3600 IN TXT "v=spf1 mx -all"
Sending email from domain A to gmail/hotmail appears in the main inbox.
Sending email from domain B end up in the spam folder for both.
Now, I am wondering why this would be seeing as there has been
practically no email from domain B and therefore I find it unlikely that
the domain itself has been flagged.
All I can see is that domain A is a lot older but I have only recently
added SPF and have never really had problems with my emails from domain
A being consumed by spam folders.
Checking a couple of blacklist checkers I cannot find my domain or my MX
on any of them.
Does anyone have an idea as to why domain B would be getting caught in
spam traps whilst A does not?
I have had someone suggest using mandrill or other external hosted
solution but quite frankly if the mail is being blocked because it is
being sent from domain B then that surely wouldn't give me any improvement?
Any help, ideas, thoughts or further resources would be greatly appreciated.
Regards,
Nigel
Hi,
As is now customary, we should do Christmas drinks in London in
December. If you'd be up for that please help pick a date:
http://doodle.com/pikxiyyyknydnaay
Everyone welcome, partners too.
I'll give it about a week and then I'll try to book a table on the
most popular date at The Phoenix:
http://www.phoenixcavendishsquare.co.uk/
If that doesn't work out then I'll try places we've tried before
(The Cask, De Hems, The Horse).
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
Google are shutting down their Checkout payment platform as of 20th
November 2013, so BitFolk will stop accepting payments that way
around 12th November.
As you may be aware if you are following the other list¹, credit card
payments are now available.
I suggest that refugees from Google Checkout pay by this means in
future, and it would be great if everyone else paying by anything
other than Direct Debit would consider it also.
The initial implementation requires you to input card details every
time and I do understand that is a major usability downside, so we
will improve that as soon as we can to have storage and continuous
authority as *options*.
The credit card payments are going through https://stripe.com/ with
the card details being passed between your browser and Stripe using
JavaScript. All BitFolk gets is a unique token that we use with
Stripe to kick off the payment, so we're not seeing or storing your
card details at any point.
Here's some more info about payment methods that are supported:
https://tools.bitfolk.com/wiki/Payment_methods
Cheers,
Andy
¹ http://lists.bitfolk.com/lurker/message/20131021.081408.6fc996c8.en.html
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi All,
I just noticed (and was perturbed by) the fact that, under Debian 7, the number of failures since last login is unavailable at the login.
The default under Debian 5.0 seems to have been set to report the number of failures since last login (if there were any).
Something has changed in the login procedure since Debian 5.0
The contents of /etc/login.defs seem identical from 5.0 to 7, and I am perplexed because I would like to restore the behaviour at login of Debian 5.0
Any/all suggestions are welcome, as usual.
Cheers
Hi,
A while ago a customer who successfully installed Gentoo on their
VPS emailed me a guide on how they did it. I hastily pasted it into
a wiki article with light reformatting, resulting in this:
https://tools.bitfolk.com/wiki/Installing_Gentoo
Earlier I had a go at following it but unfortunately I failed pretty
much immediately, so in my opinion it could do with some work.
I possibly could work out where I went wrong by reading the Gentoo
handbook, but if I cannot follow the guide then I don't think that
someone with less Linux experience than me can follow the guide
either, thus making the guide not very useful.
Also I don't have a lot of personal interest in researching how to
install Gentoo. :-)
Rather than solely hassling the person who originally contributed: I
know there are some Gentoo fans out there, so if you feel you could
improve the guide in any way please do so by editing it. All
customers can edit the wiki by logging in with their usual BitFolk
credentials.
Other guides I have successfully followed in the past despite having
very little interest in or knowledge of the finished product include:
https://tools.bitfolk.com/wiki/Installing_Arch_Linuxhttps://tools.bitfolk.com/wiki/Installing_Slackware
so that'd be the sort of level to aim for - not that those can't be
improved too! :)
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
> The optimum programming team size is 1.
Has Jurassic Park taught us nothing? — pfilandr
Hi All,
this is just a heads-up notice.
Recently, I have been stalked by a user at ovh.net . They seem to be well-financed and persistent.
I was surprised to find that, by default, the log file /var/log/sulog is disabled Debian 5.0 and Debian 7.
This behaviour is dis/activated in /etc/login.defs
su log files are handy to check for intruders, and I am surprised that Debian (and possibly others) have not seen fit to enable a default /var/log/sulog
Of course, most of you already know this, but this note was designed in case one of you was heretofore unaware.
Cheers
Hi,
Previously it was noted that kernels compressed with XZ are not
supported:
http://lists.bitfolk.com/lurker/message/20130523.110244.f70b2d77.en.html
As far as I am ware this only affected people trying to run Debian
jessie (testing) since that was the only distribution I know of that
switched to XZ for kernel compression.
I have now added support for XZ compression and it has been tested a
little by myself and a few other customers, so it should now be
working. If you are doing a dist-upgrade from wheezy then it may
still be wise to keep the wheezy kernel around in case of problems.
Also Debian jessie seems to work now as a net install; previously it
was missing a netboot Xen installer and the XZ kernel support also.
Please bear in mind that Debian jessie is an unreleased testing
branch and may break at any time for reasons beyond our control. I
would be interested to know if it is broken at any time, but can't
promise speedy fix.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi All,
I just discovered an unwanted sendmail listener at 63.141.225.90 on my bitfolk vps machine by doing a
% ps aux
I still don't know how I was compromised.
At any rate, it seems my sendmail config file is deficient.
I've grepped through the /etc directory for the offensive address to no avail.
When my email client opens, it tells me "Folder is open by another process, access is read-only".
This concerns me, because there are no visible other processes.
This is what caused me to look at 'ps aux', and discover the unwanted listener.
I believe this situation can be fixed, only I know not how.
Any advice will be gratefully received.
Cheers
