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,
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
I have just done an upgrade of Debian Squeeze to Wheezy on my VPS using
the net install option. Everything seems to have gone well (cross
everything, touch wood etc). Before doing the reinstall I read all the wiki
articles and so on. I don't know much about kernels, but all the wiki notes
talk about using the -bigmem flavour, though the installer installed -pae
flavour. Everything seems to be working OK. Have I just been reading old
instructions? Or should I be looking to install a different one?
Keith
--
Keith Williams
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
My site (ilovephilosophy.com) was down this morning, and I suspect that my
registrar has fouled something up. I suspect this because nothing is wrong
in Nagios, the site loads normally using the IP, and today was the day my
registration would have expired had I not paid to renew it last week...
Running tracert returns "Unable to resolve target system name
ilovephilosophy.com"
Running nslookup returns "*** UnKnown can't find ilovephilosophy.com:
Non-existent domain"
Is there anything else I can do to test my suspicion, or does any of this
confirm it? I know it isn't just me or my network, because my users around
the world are reporting the same trouble. I've as yet been unable to reach
anyone at my registrar, and in the meantime I'm hoping to rule out any
other possibilities.
Thanks,
Mike
Hi,
If you currently pay by Direct Debit authorization then you are
probably aware that we use GoCardless for this. If you don't then
the rest of this email is probably not of interest to you.
The way it works right now is that you create an account with
GoCardless by giving them your bank details, and that sets up a
Direct Debit instruction between your bank and them. Then, you
authorize BitFolk's payment plan which asks GoCardless to allow up
to a certain amount during a certain time period. GoCardless
enforces the limits of that plan.
That works fine, but the problem comes when you order an upgrade
that makes your plan more expensive. At the moment we need to cancel
your payment plan and ask you to authorize a new one. It's not a big
deal but it is perhaps not the best user experience. When you pay
other companies by Direct Debit they get to take whatever they want,
so you're not asked to re-authorize when, for example, your council
tax or gas bill goes up.
GoCardless have had a feature request open for a long time that asks
them to implement a way for users to authorize a new limit (or
perhaps for the customer to indicate that they're not bothered).
They have now closed this request and advise that if merchants want
to charge varying amounts then the merchant should ask the customer
to authorize a limit that is higher than any payment that would ever
be normally requested, e.g. £5,000 per month.
The question that immediately sprung to mind here was, "isn't my
customer going to be a bit disturbed by being asked to authorize a
payment plan that allows up to £5k to be taken out of their bank
account?"
Their answer to this was to add an option so that payment plans
don't have visible (to the customer) limits any more.
As I say, that is generally how Direct Debits work: you authorize
the instruction and you're trusting the organisation to only take
when they are actually owed. If they screw up and take too much, you
can dispute it with your bank and it immediately gets reversed.
There isn't normally a middle man verifying payment requests.
If this was how GoCardless had worked from the beginning then I
wouldn't have an issue, but the fact is that everyone currently with
a Direct Debit authorization to BitFolk knows they have a limit on
it that (barring GoCardless making a mistake) only allows the exact
amount to be taken.
Would you have a problem with that limit being removed? I'd be
interested to get feedback from those currently using Direct Debit
to pay. Feel free to let me know off-list if you prefer.
It's been nearly a year of using GoCardless and there haven't been
any issues of taking too much money. I would be comfortable with
setting all future authorizations to have no limit on them, as I
think the improvement to user experience of just being able to order
an upgrade is worth it. If there is a massive outcry I won't do it
though. I may also consider making it an option (defaulting to no
limit), though there is a danger of confusing people with too many
options.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
This email is mostly relevant to people who currently pay by Google
Checkout, or who really hate PayPal. If that doesn't apply to you
then you can safely ignore it.
- Google Checkout goes bye-bye
Google are shutting down their Checkout payment service on November
20th, so anyone who currently pays BitFolk by that means is going to
have to switch to something else from then on. I'm kind of glad
really because GC had the highest transaction fees of any payment
method, but I kept it around because it was the only choice for some
people.
In addition, PayPal have been getting increasingly hostile towards
customers who use them to pay by credit card without having a PayPal
account and I've now had several instances where this has proven
impossible for the customers concerned. So, something new needed.
- Stripe for credit card payments
I'm currently working on integrating http://stripe.com for credit
card payments, and the initial minimal implementation is nearly
ready. That will just allow one-off payment of invoices using a
card whose details you supply on the spot.
I could do with some testers for this. If you've got (or shortly
will have) an invoice ready to pay, you don't currently pay by
PayPal subscription or recurring Direct Debit, and you're willing to
give it a go, could you let me know off-list please?
I need to get the initial version ready before GC shuts down, but
after that I will improve the implementation to have more useful
features like saving credit card details¹ and continuous authority
(ability for BitFolk to charge your card when it needs to, without
your action).
Those who currently pay by Google Checkout and don't like any of the
other existing payment methods are going to need to pay by this
method from 20th November.
Since Stripe's transaction fees (2.4% + £0.20) are less than
PayPal's (3.4% + £0.20) I would prefer it if everyone moved to
either Direct Debit (1%) or Stripe, but whatever works for you.
Cheers,
Andy
¹ Stripe handles all the card details without passing any of them to
us; it does it in Javascript in your browser between you and them
and never lets any of the secure card data reach us, so it does
not require our side to be rated for storing or handling any of
that data.
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hello,
Since I am both lazy and stupid:-
Is there a way to exclude e-mails received from certain (external)
senders from the spamd check?
Am using the BitFolk spamd service from my Debian vps, and it works
really fine with just one exception. Every time I get an e-mail from
DPD about a scheduled delivery, it is marked as spam by the spamd
service. And since I am not checking the spam account every day I
don't see this until it is too late.
Is the a prefered way to "whitelist" the e-mail sender
yourdelivery(a)dpd.co.uk somewhow? So those emails are never sent to
spamassasin and filtered out as spam?
In /etc/mail/spamassassin/spamc.conf?
Or /etc/postfix/master.cf?
Or is the only method to change the shell script communicating with
spamd: /usr/local/bin/spamchk.sh? That is a quick fix, but it is
not a clean solution IMHO...
Thanks,
__
/ony
OpenCart also has a Google Authenticator plugin. The Google Authenticator
is available for Android, Blackberry, and iOS. This will make the admin
login like the login at your bank, where you have to enter a few numbers
either sent on sms message, or generated by some small device. Unless there
is a critical flaw in OpenCart people will not be able to login to admin
without access to your phone as well.
http://www.opencart.com/index.php?route=extension/extension/info&extension_…
--
My PGP is available at: http://downgoat.net/contact/
Hey there
A couple of quick questions if I may;
I'd like to use Filezilla to manage upload of new files to my server. I
need to set up an ftp server on my VPS, therefore. Which do you use? Any
recommendations?
I got round to upgrading to Wheezy earlier. All went well but when I
restarted apache2 the restart failed with the message that it couldn't find
httpd.conf. I commented out the appropriate line in apache2.conf and all is
well. A search (using find) yielded no sign of httpd.conf so I guess I did
the right thing, but I'd just like to confirm that there is indeed no
httpd.conf in my VPS.
Thanks for any help
Barry
