1. Enable POP in Gmail. Don’t forget to click Save Changes when you’re done.
2. Configure your client to match the settings below:

Incoming Mail (POP3) Server – requires SSL:	pop.gmail.com Use SSL: Yes Port: 995
Outgoing Mail (SMTP) Server – requires TLS:	smtp.gmail.com (use authentication) Use Authentication: Yes Use STARTTLS: Yes (some clients call this SSL) Gmail SMTP Port: 465 or 587
Account Name:	your full email address (including @gmail.com or @your_domain.com)
Email Address:	your email address (username@gmail.com or username@your_domain.com)
Password:	your Gmail password

Unless you’re using recent mode to download mail to multiple clients, make sure you’ve opted not to leave messages on the server. Your Gmail settings determine whether or not messages stay on the server, so this setting in your client won’t affect how Gmail handles your mail.

Please note that if your client does not support SMTP authentication, you won’t be able to send mail through your client using your Gmail address.

Also, if you’re having trouble sending mail but you’ve confirmed that encyrption is active for SMTP in your mail client, try to configure your SMTP server on a different port: 465 or 587.

Aaaaw, the old mobo <3

I upgraded recently to the M2N-SLI-Deluxe ;)

Your broadband username, which you should use when connecting to the Internet is in one of the following formats:

yourname.orangehome.co.uk@fs
yourname.wanadoo.co.uk@fs
yourname.freeserve.co.uk@fs
yourname.fsnet.co.uk@fs
yourname.fsbusiness.co.uk@fs
yourname.fslife.co.uk@fs
yourname.fsworld.co.uk@fs

Your Dial Up and Email Username will be in one of the following formats:

yourname.orangehome.co.uk
yourname.wanadoo.co.uk
yourname.freeserve.co.uk
yourname.fsnet.co.uk
yourname.fsbusiness.co.uk
yourname.fslife.co.uk
yourname.fsworld.co.uk

You chose the ‘yourname’ segment when you registered with Orange, Wanadoo or Freeserve.

Please note:
@fs should not be used in email or webspace settings

Your email address is your choice of name, followed by the ‘@’ sign and your email username, eg mail@yourname.orangehome.co.uk

You can use as many email addresses before the ‘@’ sign as you like, eg:

bob@yourname.orangehome.co.uk, elisabeth@yourname.orangehome.co.uk and paul@yourname.orangehome.co.uk.

For details of valid email addresses, see choosing your orange email address.

Access Your Email Online

You can access your email here: http://email.orange.co.uk

Advanced Orange Home settings

Server settings
The address of the Orange POP mail server is: pop.orangehome.co.uk
The address of the Orange SMTP mail server is: smtp.orangehome.co.uk
Do not use secure password authentication to access mail

IP address
Your IP address is allocated dynamically via DHCP- you do not need to set this. We are unable to offer a static IP address.

DNS
Note:
DNS settings should be set to ‘automatically obtain’ – there are only rare instances where Orange settings should be used. For information, the first set of Orange DNS settings are for IPStream customers, the second set for LLU.

Domain name service is dynamic.

If connecting to a router, and need DNS settings for home networking, use the IP address or your router, i.e. * 192.168.1.1

If Orange domain name server (DNS) addresses are required, you should use:

195.92.195.94 and 195.92.195.95

Or, if you experience problems with the above, use:

193.36.79.101 and 193.36.79.100

Dial Up FTP and HTTP Proxy Settings

Address:http://www-cache.orangehome.co.uk:8080
Port Number: 8080

Router settings
If you choose to use an Ethernet modem / router, the correct connection settings are:

Encapsulation:
PPP over ATM

Multiplexing method:
VC-Based

Virtual circuit:
VPI=0
VCI=38

Modulation:
Multi mode

Authentication:
CHAP
MTU (Maximum Transmission Unit)

In case of problems with a third party router, change MTU to 1492 (Livebox default setting)

Dial-up numbers
If your computer is connected to the Internet, you can get your dial-up number (and connection settings) from our account retrieval pages:

https://www.orange.co.uk/signup/reclaim/ar10.cfm

If your computer isn’t connected to the Internet, you can use an Orange CD to set-up your computer. If you have already registered, select the Retrieve Account tab and follow the links to Retrieve Your Account.

Site Builder/ FTP My Site

The address of your website can take the form:

http://mysite.orange-members.co.uk/sitename or http://sitename.mysite.orange-members.co.uk/

If you use FTP My Site the FTP server address is sitebuilder.orange.co.uk

Your username takes the form:

name@yourname.orangehome.co.uk|sitename
name@yourname.wanadoo.co.uk|sitename
name@yourname.freeserve.co.uk|sitename
name@yourname.fsnet.co.uk|sitename
name@yourname.fsbusiness.co.uk|sitename
name@yourname.fslife.co.uk|sitename
name@yourname.fsworld.co.uk|sitename

Your Password is the one you chose when registering with the My Site service.

You can register for Site Builder/ FTP My Site by visiting http://www.orange.co.uk/communicate/sitebuilder/

Note:
These details were taken directly from the Orangehome support website cached by Google. This page has been added here as an archive because the page is currently no longer available or has moved somewhere else on the Orangehome support site, which I cannot find. I/We take no responsibility of any kind for the way in which this information is used.

Other Orange Home Related Posts:
E-mail Service Problem

How could I have not been alerted to this earlier you may well ask; well the fact that my internet connection that runs through the same line did not have a problem with it kind of masked the problem for me. I mean, I’m not an engineer, not a telecommunications engineer anyway, and I have never worked for BT services ever, so, how would I know? Using the phone? I don’t, I only use it to receive calls.

Were they stealing my money?

I call BT support and ask them politely, all the while quietly fuming inside, what the problem is with my line. For the last month I have neither been able to receive nor make phone calls from my line for which I am paying you guys at BT. They test the line (whilst I wait on hold, hoping not to lose them as this is the third time that I have had to call!!) and come back to me informing me that the line has a fault. Really?

BT organise to have the line repaired and my calls redirected to my mobile number. They also tell me that they will refund me the cost of the line for every day AFTER the ALLOCATED repair date. Ok, not too bad though, allegedly the line will be repaired tomorrow.

What about all the calls and potential business I missed?
Tough, apparently BT keep no such record.

What about some compensation on the cost of the BT line rental for that period that I could not use the line for calls?
Tough, BT will only compensate you AFTER you report a fault and AFTER the date they allocate to fix your line.

Are you telling me it is ok to keep stealing until you get cought? Only give back what you are taking AFTER you are receiving a complaint about it?
(no response, just another “I’m terribly sorry, but…”)

What about the cost of the calls to BT to have the fault fixed (seeing as it is a freephone number, from landlines)?
Tough, you are told at the start of the call that it is chargeable and if you want to make the call for free, apparently I should have visited a neighbour!

What about the fact that, as BT proudly display on their bills, they won the ‘Company of the Year Award’?
Well, actually I didn’t ask this, I merely stated that it appeared to be a joke from my perspective.

Company of the Year?
BT, I seriously hope not. All this the day AFTER I was promised a call-back because their system was down. I guess she forgot.

This is so WE do not forget. Clever policies do not make for good business-customer relationships, only bitter ones. It is not stealing after all, my mistake, it is ‘Company Policy’.
Take care, and be warned.

UPDATE:

Are they deliberately wasting my time?

They only went and redirected the landline to the wrong mobile number! So, guess what, I’m calling AGAIN to have them rectify yet another problem caused by BT. Another tailback, an automated ringback is on offer telling me that they will callback within 45 minutes… Let’s see how they do this time.

Callback within 5 minutes direct from india and the redirect has been updated. Apparently. I’ll check in 30 minutes once BT’s super-computers update. It’s a bit like waiting for Google to come and spider your site again to list your new content, except, as soon as Google knows the content is there, it is added… hmmm… Not so super I guess.

Before saying anything else, avoid Orange Home Broadband service like the plague if you use either Microsoft Outlook or Windows Vista.

Having spent the last 3 hours on the phone with OrangeHome (0870 010 2462), with 5 different Technical representatives, 1 hour with my techie (Web Host) and untold combinations in the effort to get my mail to send from Outlook on the Windows Vista platform, I have finally given up. It seems to be a lost cause.

Not only is my outgoing mail being blocked at Orange (built on Wanadoo), but they insist that the problem lies with everyone else. Interesting seeing as my set-up was working absolutely fine on Outlook from my laptop running XP (Service Pack 2) until I switched to Orange Broadband – ‘Unlimited’ (yes, you may now laugh. I am.)

So, No mail from either my Vista Desktop or my XP laptop; in fact the only way that I can send any mail at all is using WebMail or the mail account provided to me by OrangeHome. It would only be fair to say that the e-mail account Orange provied me with will send mail from Outlook Express though. Unfortunately the only way that I can send e-mail through my 12 other accounts is now via a web browser at my host’s WebMail service.

It goes without saying that I will be switching ASAP.

Be warned, Orange Broadband, ‘unlimited’ has provided in my opinion, not only the worst internet service ever in the UK, but also the worst customer service I have ever experienced.

ClaraNet, here I come ;)

UPDATE:

I urge everyone to write to the Orange CEO at the following email address: Olaf.Swantee@orange.co.uk

Also, if you are lucky enough to have a flexible email service provider (ie you have your own website domain and are hosting a website with a company) you may be able to get the mail through using another SMTP port such as 587 (as opposed to the standard port 25) as it is port 25 that Orangehome blocks.

htaccess files must be uploaded as ASCII mode, not BINARY. You may need to CHMOD the htaccess file to 644 or (RW-R–R–). This makes the file usable by the server, but prevents it from being read by a browser, which can seriously compromise your security. htaccess files affect the directory they are placed in and all sub-directories, that is an htaccess file located in your root directory (yoursite.com) would affect yoursite.com/content, yoursite.com/content/contents, etc. It is important to note that this can be prevented (if, for example, you did not want certain htaccess commands to affect a specific directory) by placing a new htaccess file within the directory you don’t want affected with certain changes, and removing the specific command(s) from the new htaccess file that you do not want affecting this directory. In short, the nearest htaccess file to the current directory is treated as the htaccess file. If the nearest htaccess file is your global htaccess located in your root, then it affects every single directory in your entire site.

Before you go off and plant htaccess everywhere, read through this and make sure you don’t do anything redundant, since it is possible to cause an infinite loop of redirects or errors if you place something weird in the htaccess.

You will probably want to create an error document for codes 404 and 500, at the least 404 since this would give you a chance to handle requests for pages not found. 500 would help you out with internal server errors in any scripts you have running. You may also want to consider ErrorDocuments for 401 – Authorization Required (as in when somebody tries to enter a protected area of your site without the proper credentials), 403 – Forbidden (as in when a file with permissions not allowing it to be accessed by the user is requested) and 400 – Bad Request, which is one of those generic kind of errors that people get to by doing some weird stuff with your URL or scripts.

In order to specify your own customized error documents, you simply need to add the following command, on one line, within your htaccess file:

ErrorDocument code /directory/filename.ext or ErrorDocument 404 /errors/notfound.html

This would cause any error code resulting in 404 to be forward to yoursite.com/errors/notfound.html
Likewise with: ErrorDocument 500 /errors/internalerror.html

You can name the pages anything you want (I’d recommend something that would prevent you from forgetting what the page is being used for), and you can place the error pages anywhere you want within your site, so long as they are web-accessible (through a URL). The initial slash in the directory location represents the root directory of your site, that being where your default page for your first-level domain is located. I typically prefer to keep them in a separate directory for maintenance purposes and in order to better control spiders indexing them through a ROBOTS.TXT file, but it is entirely up to you.

If you were to use an error document handler for each of the error codes I mentioned, the htaccess file would look like the following (note each command is on its own line):

ErrorDocument 400 /errors/badrequest.html
ErrorDocument 401 /errors/authreqd.html
ErrorDocument 403 /errors/forbid.html
ErrorDocument 404 /errors/notfound.html
ErrorDocument 500 /errors/serverr.html

You can specify a full URL rather than a virtual URL in the ErrorDocument string (http://yoursite.com/errors/notfound.html vs. /errors/notfound.html). But this is not the preferred method by the server’s happiness standards.

You can also specify HTML, believe it or not!

ErrorDocument 401 "<body  bgcolor=#ffffff>
You have to actually <b>BE</b>
a member to view this page!

The only time I use that HTML option is if I am feeling particularly saucy, since you can have so much more control over the error pages when used in conjunction with xSSI or CGI or both. Also note that the ErrorDocument starts with a ” just before the HTML starts, but does not end with one…it shouldn’t end with one and if you do use that option, keep it that way. And again, that should all be on one line, no naughty word wrapping!

Blocking Users by IP

Add the following –changing the IPs to suit your needs–each command on one line:

order allow,deny
deny from 123.45.6.7
deny from 012.34.5.  allow from all

You can deny access based upon IP address or an IP block. The above blocks access to the site from 123.45.6.7, and from any sub domain under the IP block 012.34.5. (012.34.5.1, 012.34.5.2, 012.34.5.3, etc.) I have yet to find a useful application of this, maybe if there is a site scraping your content you can block them, who knows.

Block traffic from a single referrer

RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} badsite.com [NC]
RewriteRule .* - [F]

Block traffic from multiple referrers

RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} badsite.com [NC,OR]
RewriteCond %{HTTP_REFERER} anotherbadsite.com
RewriteRule .* - [F]

In the “single referrer” case above, “badsite\.com” is the domain you wish to block. Note the backslash proceeding the period (“.”) to actually donate a period, as in Regular Expressions, a period donates any character, which is not what we want. The flag “[NC]” is added to the end of the domain to make it case insensitive, so whether the domain is “badsite.com”, “Badsite.com” etc, however bad it gets, it gets blocked. Finally, the last line in the .htaccess file specifies that the action to take when a match is found is to fail the request, meaning the referrer traffic will hit a 403 Forbidden error. The only difference between blocking a single referrer and multiple referrers is the modified [NC, OR] flag in the later case to every domain but the last.

The definition of a “bad bot” varies depending on who you ask, but most would agree they are the spiders that do a lot more harm than good on your site (ie: an email harvester). A site ripper on the other hand are offline browsing programs that a surfer may unleash on your site to crawl and download every one of its pages for offline viewing. In both cases, both your site’s bandwidth and resource usage are jacked up as a result, sometimes to the point of crashing your server. Bad bots typically ignore the wishes of your robots.txt file, so you’ll want to ban them using means such as .htaccess. The trick is to identify a bad bot.

Below is a useful code block you can insert into.htaccess file for blocking a lot of the known bad bots and site rippers currently out there.

RewriteEngine On RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [OR]
RewriteCond %{HTTP_USER_AGENT} ^Bot mailto:craftbot@yahoo.com [OR]
RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [OR]
RewriteCond %{HTTP_USER_AGENT} ^Custo [OR]
RewriteCond %{HTTP_USER_AGENT} ^DISCo [OR]
RewriteCond %{HTTP_USER_AGENT} ^Download Demon [OR]
RewriteCond %{HTTP_USER_AGENT} ^eCatch [OR]
RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [OR]
RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR]
RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR]
RewriteCond %{HTTP_USER_AGENT} ^Express WebPictures [OR]
RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR]
RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [OR]
RewriteCond %{HTTP_USER_AGENT} ^FlashGet [OR]
RewriteCond %{HTTP_USER_AGENT} ^GetRight [OR]
RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [OR]
RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [OR]
RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [OR]
RewriteCond %{HTTP_USER_AGENT} ^GrabNet [OR]
RewriteCond %{HTTP_USER_AGENT} ^Grafula [OR]
RewriteCond %{HTTP_USER_AGENT} ^HMView [OR]
RewriteCond %{HTTP_USER_AGENT} HTTrack [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^Image Stripper [OR]
RewriteCond %{HTTP_USER_AGENT} ^Image Sucker [OR]
RewriteCond %{HTTP_USER_AGENT} Indy Library [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^InterGET [OR]
RewriteCond %{HTTP_USER_AGENT} ^Internet Ninja [OR]
RewriteCond %{HTTP_USER_AGENT} ^JetCar [OR]
RewriteCond %{HTTP_USER_AGENT} ^JOC Web Spider [OR]
RewriteCond %{HTTP_USER_AGENT} ^larbin [OR]
RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Mass Downloader [OR]
RewriteCond %{HTTP_USER_AGENT} ^MIDown tool [OR]
RewriteCond %{HTTP_USER_AGENT} ^Mister PiX [OR]
RewriteCond %{HTTP_USER_AGENT} ^Navroad [OR]
RewriteCond %{HTTP_USER_AGENT} ^NearSite [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetAnts [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetSpider [OR]
RewriteCond %{HTTP_USER_AGENT} ^Net Vampire [OR]
RewriteCond %{HTTP_USER_AGENT} ^NetZIP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Octopus [OR]
RewriteCond %{HTTP_USER_AGENT} ^Offline Explorer [OR]
RewriteCond %{HTTP_USER_AGENT} ^Offline Navigator [OR]
RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [OR]
RewriteCond %{HTTP_USER_AGENT} ^Papa Foto [OR]
RewriteCond %{HTTP_USER_AGENT} ^pavuk [OR]
RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [OR]
RewriteCond %{HTTP_USER_AGENT} ^RealDownload [OR]
RewriteCond %{HTTP_USER_AGENT} ^ReGet [OR]
RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [OR]
RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [OR]
RewriteCond %{HTTP_USER_AGENT} ^SuperBot [OR]
RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Surfbot [OR]
RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [OR]
RewriteCond %{HTTP_USER_AGENT} ^Teleport Pro [OR]
RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [OR]
RewriteCond %{HTTP_USER_AGENT} ^Web Image Collector [OR]
RewriteCond %{HTTP_USER_AGENT} ^Web Sucker [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebAuto [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebCopier [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebFetch [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebGo IS [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebReaper [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebSauger [OR]
RewriteCond %{HTTP_USER_AGENT} ^Website eXtractor [OR]
RewriteCond %{HTTP_USER_AGENT} ^Website Quester [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebStripper [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [OR]
RewriteCond %{HTTP_USER_AGENT} ^WebZIP [OR]
RewriteCond %{HTTP_USER_AGENT} ^Wget [OR]
RewriteCond %{HTTP_USER_AGENT} ^Widow [OR]
RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [OR]
RewriteCond %{HTTP_USER_AGENT} ^Xaldon WebSpider [OR]
RewriteCond %{HTTP_USER_AGENT} ^Zeus
RewriteRule ^.* - [F,L]

Bots that are listed above will all receive a 403 Forbidden error when trying to view your site. The amount of bandwidth savings and decrease in server resource usage as a result may be significant in many cases.

Redirects

htaccess uses redirect to look for any request for a specific page (or a non-specific location, though this can cause infinite loops) and if it finds that request, it forwards it to a new page you have specified:

Redirect /olddirectory/oldfile.html http://yoursite.com/newdirectory/newfile.html

Note that there are 3 parts to that, which should all be on one line : the Redirect command, the location of the file/directory you want redirected relative to the root of your site (/olddirectory/oldfile.html = yoursite.com/olddirectory/oldfile.html) and the full URL of the location you want that request sent to. Each of the 3 is separated by a single space, but all on one line. You can also redirect an entire directory by simple using Redirect /olddirectory http://yoursite.com/newdirectory/

Disallowing Hotlinking

Using .htaccess, you can disallow hot linking on your server, so those attempting to link to an image or CSS file on your site, for example, is either blocked (failed request, such as a broken image) or served a different content (ie: an image of an angry man) . Note that mod_rewrite needs to be enabled on your server in order for this aspect of .htaccess to work. Inquire your web host regarding this.

With all the pieces in place, here’s how to disable hot linking of certain file types on your site, in the case below, images, JavaScript (js) and CSS (css) files on your site. Simply add the below code to your .htaccess file, and upload the file either to your root directory, or a particular subdirectory to localize the effect to just one section of your site:

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www.)?mydomain.com/.*$ [NC]
RewriteRule .(gif|jpg|js|css)$ - [F]

Be sure to replace “mydomain.com” with your own. The above code creates a failed request when hot linking of the specified file types occurs. In the case of images, a broken image is shown instead.

Serving alternate content when hot linking is detected

You can set up your .htaccess file to actually serve up different content when hot linking occurs. This is more commonly done with images, such as serving up an Angry Man image in place of the hot linked one. The code for this is:

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www.)?mydomain.com/.*$ [NC]
RewriteRule .(gif|jpg)$ http://www.mydomain.com/angryman.gif [R,L]

Same deal- replace mydomain.com with your own, plus angryman.gif.

Preventing Directory Listings

Typically a server is setup to prevent directory listing, but sometimes they are not. If not, become self-sufficient and fix it yourself:

IndexIgnore *

The * is a wildcard that matches all files, so if you stick that line into an htaccess file in your images directory, nothing in that directory will be allowed to be listed.

On the other hand, what if you did want the directory contents to be listed, but only if they were HTML pages and not images? Simple says I:

IndexIgnore *.gif *.jpg

This would return a list of all files not ending in .jpg or .gif, but would still list .txt, .html, etc.

And conversely, if your server is setup to prevent directory listing, but you want to list the directories by default, you could simply throw this into an htaccess file the directory you want displayed:

Options +Indexes

If you do use this option, be very careful that you do not put any unintentional or compromising files in this directory. And if you guessed it by the plus sign before Indexes, you can throw in a minus sign (Options -Indexes) to prevent directory listing entirely–this is typical of most server setups and is usually configured elsewhere in the apache server, but can be overridden through htaccess.

If you really want to be tricky, using the +Indexes option, you can include a default description for the directory listing that is displayed when you use it by placing a file called HEADER in the same directory. The contents of this file will be printed out before the list of directory contents is listed. You can also specify a footer, though it is called README, by placing it in the same directory as the HEADER. The README file is printed out after the directory listing is printed.

1 & 1 Web Hosting Sucks
1 & 1 Hosting provider sucks
1 & 1 Hosting Sucks
1&1 Internet Web Hosting Sucks
1&1.com sucks
1&1 Control Panel Sucks
1&1 Internet Inc FAQ SUCKS
1&1 Hosting Reviews
Reviews of 1&1

1and1 Web Hosting Sucks
1and1 Hosting provider sucks
1and1 Hosting Sucks
1and1 Internet Web Hosting Sucks
1and1.com sucks
1and1 Control Panel Sucks
1and1 Internet Inc FAQ SUCKS
Reviews of 1and1
1and1 Hosting Reviews
1and1.com sucks

If you have a scraper please feel free to reproduce this post in it’s entirety and if you need help building one so you can republish this post let me know I’ll help in any way I can. Scraped from GrayWolf

I have wanted to start writing a blog for absolutely ages but keep getting snowed under with other endeavours. So it’s a late start and I’m really not one to go into many personal details anyway. I hate talking about myself. This blog is less about me and more about my travels and discoveries in my related fields. Perhaps, when I’ve actually written some posts… It will become a decent resource for information. Perhaps I’ll even put in extra-extra time to do some design work for my own blog one day!