17 February 2015

O2 MMS Settings on Jolla Phone

I have an O2 pay monthly SIM and a Jolla phone (JP-1301) running Sailfish OS. I needed to reinstall MMS settings so sent 'ACTIVE' to 2020 as they advise and was greeted with a return text message stating: "Unfortunately we had problems dealing with your requset for settings. Please contact Customer Service". Now, I've dealt with customer service enough times to know how this would pan out: "Yeah, it says here your device doesn't have MMS capabilities so there's no settings for it" being a likely outcome. So I poked through some other devices and tried a few variations of the settings I found. The following worked for me:

Go to: Settings > System > Mobile network > MMS access point

And enter the following settings:

Connection Name: O2 MMS postpay
Access point name: mobile.o2.co.uk

Username: o2web
Password: password

Proxy address:
Proxy port: 8080

MMS message centre
MMS message centre address: http://mmsc.mms.o2.co.uk:8002

11 March 2014

Fixing XMPP problem after updating Flamingo IM

I've just updated the Flamingo app and found it couldn't connect to my custom XMPP server, despite having the details correct. Turns out, it failed to connect because I have a 'self signed' SSL certificate. Would have been nice to have an error message! Anyway, getting around this is trivial. Open a new Terminal window and enter:
defaults write com.nonatomic.Flamingo AllowSelfSignedCertificates -bool true
I restarted Flamingo and was able to connect straight away. Obviously, you have now an issue where Flamingo will connect to any server with a self-signed certificate, so only do this if you're aware of the risk. This post originally appeared on SimonCoopey.net: http://coopey.me/p-AUy

3 December 2013

Debian / Ubuntu Postfix Error: Diagnostic-Code: X-Postfix; unknown user:

I've just set up a new Debian/Ubuntu server, and had a problem with Postfix rejecting mail.  Mails were getting returned to sender with the error:

Diagnostic-Code: X-Postfix; unknown user: "admin"

From the command line, I opened the Postfix config file:

vi /etc/postfix/main.cf

Then I found the line:

mydestination = example.com, localhost, localhost.localdomain

(where example.com was the server address) and changed it to:

mydestination = localhost, localhost.localdomain

I saved the file (:wq) and restarted Postfix:

service postfix retstart

Emails started arriving! I believe that the original format confuses Postfix- instead of trying to find and deliver to the local mailboxes, it tries to forward them on to example.com perhaps?

24 June 2013

Uninstall Copy (copy.com) in Mac OS X (10.8)

I tried 'Copy' (or click this link for +5GB free), and while the generous storage quota was appealing and the service worked fine generally, I didn't like the Mac OS X client.
It prompted me to log in on every start up, a big hassle when you use super-long randomly generated passwords. On the other hand, Box and Dropbox both work away in the background without needing any assistance.
Also, it put an unexpected and unwanted extra menu option on the right-click menu which I was not too happy about.

First, exit Copy from the menubar; Then delete the application from the Applications folder.

Then, to get rid of the extras Copy installs, run these commands in Terminal:

sudo rm -rf "/Library/Application Support/Copy Agent"


rm -rf "~/Library/Application Support/Copy Agent"


7 May 2013

Removing hard-coded social share buttons on Adelle theme

An acquaintance of mine, Rachael Phillips, has a blog and uses the nice Adelle theme from Bluchic.  Bluchic don't offer support for the theme (fair enough, as it's given away for free), and the WordPress forums were little help with a small problem Rachael had with the theme.
She has added a social sharing plugin, but the Adelle theme has its own social sharing buttons hard-coded in to the theme. So there is some duplicity in post footers:

I thought that the 'Tweet' and 'Like' buttons would be quite easy to get rid of, by adding "display: none;" to relevant classes in the style.css file. This worked for the Tweet button, but the 'Like' button stubbornly remained. In the end, I opted to edit the relevant files directly as this seemed like the quickest  option.

To remove the hard-coded social buttons you need to edit the following files:

In each of these files, look for the footer:

    <footer class="post-footer">
      <ul class="post-info-meta">
          <a href="<?php echo esc_url('https://twitter.com/share'); ?>" class="twitter-share-button" data-url="<?php the_permalink() ?>" data-count="horizontal">Tweet</a><script type="text/javascript" src="//platform.twitter.com/widgets.js"></script>
          <div class="fb-like" data-href="<?php the_permalink() ?>" data-send="false" data-layout="button_count" data-width="100" data-show-faces="false"></div>
        <li class="post-info-comment"><div class="post-comment"><?php comments_popup_link( __('0 comment','adelle-theme'), __('1 Comment','adelle-theme'), __('% Comments','adelle-theme') ); ?></div></li>
    </footer><!-- .post-footer -->

You want to find the following lines...

          <a href="<?php echo esc_url('https://twitter.com/share'); ?>" class="twitter-share-button" data-url="<?php the_permalink() ?>" data-count="horizontal">Tweet</a><script type="text/javascript" src="//platform.twitter.com/widgets.js"></script>
          <div class="fb-like" data-href="<?php the_permalink() ?>" data-send="false" data-layout="button_count" data-width="100" data-show-faces="false"></div>

...and simply remove them.

Save each file, and upload into the /adelle/ folder, replacing the existing files.

If you don't want to edit files, or are worried about editing the files yourself, you can download them here: http://simoncoopey.dropmark.com/120396

29 April 2013

Diverting visitors from a specific IP address to another website

I don't like certain companies or people looking me up. UK company A4e is one I most definitely don't want to be associated with, and I do not fancy them looking up my CV website- but I found visitor records suggesting that someone at the company has.  Obviously, this is a public page and doesn't contain much in the way of personal information- its purpose is to help people who have worked with me track me down, or people who get an email from me on a professional level look up more about me. What it is not for is the likes of A4e to data-mine and use my information for any of their purposes. So I set out to block any repeat visits, with a redirect to a page that says why.

This seems to be quite easy to accomplish with .htaccess.  To block someone from a specific IP address add the following to a .htaccess file: (or append it to an existing one, taking care not to delete important existing rules)

RewriteEngine On 
RewriteCond %{REMOTE_ADDR} ^195\.171\.111\.196
RewriteRule .* http://goaway.coopey.me [R,L] 

If you wanted to block a whole range of IP addresses use '.$' e.g. to block the range 195.171.111.* use the following for line two:

RewriteCond %{REMOTE_ADDR} ^195\.171\.111\.$ 

If you wanted to block a subsection, use the following format: (this will block to

RewriteCond %{REMOTE_ADDR} ^195\.171\.111\.(1[6-9]|2[0-9]|3[0-2])$

The IP address in this example seems to be A4e's fixed IP from their head office in Sheffield. The page goaway.coopey.me is hosted at Tumblr, and says 'Access Denied' with a short explanation why.

Remember, this will only work on visitors from a specific IP (or range of IPs). If you block a range, you may be blocking more people than you attended, and if you block someone who uses a dynamic IP address (their ISP changes this each time they connect to the internet) then they will not be permanently redirected- and the people who are subsequently assigned the IP will have to access!

19 September 2012

Check CentOS Version

Ever go to install a package, but can’t remember which specific version of CentOS you’re running? This often happens to me, and helpfully I can never remember the command. So for as much my benefit as yours, this is what you do:


cat /etc/redhat-release

which will return your version number, eg:

CentOS release 5.8 (Final)


The command:

cat /etc/centos-release

works in CentOS 6.

Changing root password in CentOS

If you want to change the default root password in CentOS, it’s one simple command: (assuming you’re logged in as root)


You’ll have to enter your new password twice:

Changing password for user root.
New UNIX password: 
Retype new UNIX password:

If they match, you’ll get the message:

passwd: all authentication tokens updated successfully.

All done!

If you need help generating a random and secure password, try passwordsite.co.uk

via Simon Coopey » Development http://simoncoopey.com/2012/changing-root-password-in-centos/#utm_source=feed&utm_medium=feed&utm_campaign=feed

28 April 2012

Moving home...

Well not home, but this blog.

The content has been merged in with my main blog at SimonCoopey.com

Some of the content seemed better suited kept separate. So I kept the short 'tidbits' here, and moved the longer posts there.

16 April 2012

Edit BuddyPress Admin Bar - Log In

A site I've been working on is using a WordPress multisite install, with BuddyPress.  As a multisite install, the idea is users will be able to create their own blog, which works fine.  However, say a user who is not logged in, visits one of the sub-blogs and clicks the 'Log In' button on the BuddyPress admin bar, they're redirected to the main blog home page. Not optimal behaviour for me.
There was no option to edit this in the BuddyPress admin menu, no plugin to alter this, and trying to search for a solution turned up results that either asked how to fix it, or were about a slightly different problem (e.g. disabling the BuddyPress admin bar and creating one's own).

I have created a plugin to fix this- 'BuddyPress Adminbar Log In Fix' or 'BP-adminbar-c' for short.

To fix the log in behaviour of the button is not too difficult, we create a function for the button, active only when the user is not logged in:

function custom_adminbar_li_button() {
if (!is_user_logged_in()) {
echo '<li><a href="/wp-login.php/">Log In</a></li>';

Then, we create a function to remove the original log in button, and replace it with our new button, appending it to the WordPress footer which calls the BuddyPress admin bar:

function remv_bp_adminbar_li(){

remove_action('bp_adminbar_menus', 'bp_adminbar_login_menu', 2);
add_action('bp_adminbar_menus', 'custom_adminbar_li_button', 2);

This plug in is available on GitHub: http://coopey.me/3xci7