Beware moving to Sky if you have your own domain

If you have your own domain and use a desktop email client such as Thunderbird, then you will not be able to send emails using your own domain name (eg [email protected])

Sky smtp servers will not allow this.

You sure?

Tried using ssl options on your outgoing mail?

I am quoting from Sky t/s

In reply to a post by ukwiz:

I am quoting from Sky t/s

Where?

Are you using port 25 for SMTP? Most ISPs do block that, but most mail hosters provide an alternative port.

In reply to a post by ukwiz:

If you have your own domain and use a desktop email client such as Thunderbird, then you will not be able to send emails using your own domain name (eg [email protected])

Sky smtp servers will not allow this.

Entirely incorrect.

Sky even have a support page advising how to set up a third party address: http://help.sky.com/email/composing-emails/send-an-e...

It's a Yahoo issue.

You need to add your sending address in Sky Yahoo webmail. You will then receive an email to that address for verification.

http://help.sky.com/email/problems-with-sky-yahoo-ma...

That article is about sending from Sky Webmail. OP wants to send from mail client over SMTP.

supremetwo's link is more appropriate.

In reply to a post by XRaySpeX:

That article is about sending from Sky Webmail. OP wants to send from mail client over SMTP.

supremetwo's link is more appropriate.

The steps outlined in both our links is identical. Although my link only mentions webmail, it's equally applicable to SMTP.

I have just moved for BE to Sky and have my own domain.

In fact multiple domains for my self, wife and a committee I am a member off.

I have had no issues with sending emails using SSL and an alternative port to port 25 given to me by my domain provider.

In reply to a post by Archetype486:

I have had no issues with sending emails using SSL and an alternative port to port 25 given to me by my domain provider.

Anyone who has an SMTP server from their third party email provider might as well use that rather than take the steps in these posts. Port 25 will work on Sky too, it's not blocked.

Some people take the cheaper option to domain hosting + email hosting which is domain hosting + email forwarding. Domain providers will typically not provide use of an SMTP server for these cheaper options so ISP SMTP servers are required.

Edited by Oliver341 (Fri 14-Feb-14 15:17:04)

I would agree with you

* If sending another domain's email to SKY's SMTP server then you need to use the link you provided to tell sky you are legitimate and let the emails through
* If sending another domain's email direct to that domains SMTP server, then you do not need to do anything. I use this option.

In reply to a post by ukwiz:

If you have your own domain and use a desktop email client such as Thunderbird, then you will not be able to send emails using your own domain name (eg [email protected])

You should always try to use the sending server (SMTP) from the same place the incoming mail comes from. By having incoming mail from your domain host, and your sending from your ISP it makes it very hard to identify legitimate versus spam email.

All companies that host email domains have an SMTP server - but some companies host email domains by simply forwarding, these are the ones to avoid.

Also I've moved from O2 to Sky, and still use smtp.o2.co.uk for my outgoing server with no issues

Entirely incorrect.

I don't think so. I have never used my @sky.com email address, and as such Yahoo. I have several accounts with Which.net. I am unable to use the which smtp mail server. Sky inform me relaying is not allowed. If it wasn't for skyusermail I would be unable to use my which accounts.

Or is there an alternative available?

In reply to a post by wingco1:

Entirely incorrect.

I don't think so. I have never used my @sky.com email address, and as such Yahoo.

The Sky Yahoo SMTP server is there for you if you want it.

Where can i find the settings?

In reply to a post by wingco1:

Where can i find the settings?

pop.tools.sky.com
Port 995
[email protected]

Outgoing
smtp.tools.sky.com
Port 465

SSL/TLS
normal password authentication

http://help.sky.com/email/set-up-sky-yahoo-mail/get-...

Edited by deleted (Sat 15-Feb-14 18:41:22)

http://help.sky.com/email/set-up-sky-yahoo-mail/get-...

Obviously if you are using it with a third party pop3 server, the outgoing email & password will have to be set different to your incoming email & password. All clients support this.

Edited by Oliver341 (Sat 15-Feb-14 18:41:14)

Also, Sky do not block your usage of the Which.net SMTP server; Which.net choose to block usage of their SMTP server to anyone not currently connected to their dial-up internet service because it is an unauthenticated SMTP service.

Thanks.

I could happily use the which.net smtp without any problems until I moved to Sky broadband. I still use the which.net pop server to download my mail. If I try to use the which.net smtp it was Sky who were telling me that 'relaying was not allowed'.

Thanks to your pointer I've managed to set up my mail accounts to use the sky yahoo smtp servers. Thanks for that.

My two penny worth on this subject of using your own domain name in an email client, such as Outlook, where your ISP is Sky and my comments relate to a domestic environment.

You will probably be using a hosted service for your emails which means that you will be sharing a server with many other domains but all will have the same IP address.

Now you could use the same address for both POP3 [or IMAP] and SMTP and instructions of the setup credentials to use will be supplied by the hosting provider. Bingo, everything will work meaning the basic premise of the OP is incorrect. However the reputation of the server may be poor which will see your emails rejected even if correctly addressed.

IMHO it is far better to use the SMTP of your ISP as the server reputation will nearly always be clean. If you want to use that method you will have to authenticating yourself to the SMTP server with a user name and password and select a particular port. Additionally you may have to use an encrypted connection. On top of all that you may have to register your domain name with your ISP. Getting all the facts together is not easy but an internet search is your friend here.

Even so when you stray away from your home ISP connection your email client credentials might still not work due to imposed restrictions on that network. At that point your get out of jail card is using webmail.

In reply to a post by trolleybus:

Now you could use the same address for both POP3 [or IMAP] and SMTP and instructions of the setup credentials to use will be supplied by the hosting provider. Bingo, everything will work meaning the basic premise of the OP is incorrect. However the reputation of the server may be poor which will see your emails rejected even if correctly addressed.

This is where you should publish an SPF record for your domain giving the IP of the hosting provider SMTP. This is how you define your 'trust' of the server the mail comes from. The hosting provider's sending server won't have a reputation as such, especially without an SPF record.

The ISP server almost certainly has an SPF record, but SPF records are attached to domains, not IP addresses.

Please tell me how I go about taking on board your suggestion.

In reply to a post by trolleybus:

Please tell me how I go about taking on board your suggestion.

Your domain host needs to let you edit your own DNS entries. Then this page will help you create the right information, and you plug that information into the DNS entry. Each domain / web host is different on the DNS stuff.

http://www.spfwizard.net/

You must have something odd in your settings because I have no problem using non-Sky SMTP servers with my Sky account.

I can only assume things have changed. Sky would not allow use of smtp servers other than their own. That is why skyuser set up a free smtp server for sky users.

In reply to a post by wingco1:

I can only assume things have changed. Sky would not allow use of smtp servers other than their own. That is why skyuser set up a free smtp server for sky users.

Sky never blocked third party SMTP servers.

The reason Skyuser set up their SMTP server was because Sky Google added a "Sender" header to outgoing mails meaning Outlook clients showed an ugly "sent on behalf of" message. The same is still true for standard Gmail sending mail from third party addresses.

The "on behalf of" is just down to how some mail clients react to a Reply-To header.

In reply to a post by BatBoy:

The "on behalf of" is just down to how some mail clients react to a Reply-To header.

It's the Sender header which triggers this message.

smtp.o2.co.uk never let you use your own domain name on outgoing smtp, which was why they put in relay.o2.co.uk.

In reply to a post by ukwiz:

smtp.o2.co.uk never let you use your own domain name on outgoing smtp

It did, the "From" address could be anything you wanted as long as the outgoing authentication email/pass was set correctly.

Of course most people incorrectly had outgoing auth set to "use same settings as incoming" in their clients and assumed smtp.o2.co.uk couldn't be used with third party addresses so it was easier for O2 to hand out an unauthenticated smtp server than babysit users through the correct setup for smtp.o2.co.uk.

FYI, this is not just an issue with sending emails via SMTP. Two of my users have had to migrate away from using our Dreamhost hosted email because they can't even READ email via IMAP. We know this is Sky blocking at the network level as (a) it says 'destination unreachable' in Console (b) on our phones, if we switch from wifi to 3G it works and (c) if we use a VPN it works also.

I can understand Sky trying to enforce use of its own SMTP servers to make sure that they aren't seen as a source of spam, but blocking IMAP is something I've never heard of.

What ports are you using? Not seen any issues with IMAP when encryption options are on.

I have my own domain name, hosted from a friend who runs a mail server and website for me and others, and I use that as my smtp server rather than btinternet.com or my company server (which has similar limitations).

Been doing this for about 15 years with no problems...

In reply to a post by keith969:

I have my own domain name, hosted from a friend who runs a mail server and website for me and others, and I use that as my smtp server rather than btinternet.com or my company server (which has similar limitations).

mail.btinternet.com will send mail from any email address as long as outgoing authentication is set correctly with BT credentials. These days you don't even have to authenticate add-on email addresses in advance.

True, but using your own domain smpt server has its advanges. I don't use my btinternet.com - why should I when I have my own?

In reply to a post by keith969:

True, but using your own domain smpt server has its advanges. I don't use my btinternet.com - why should I when I have my own?

Up to you. But the information might be of use to other people, especially if they are using free email forwarding from a domain provider without an SMTP server.

In reply to a post by Oliver341:

Up to you. But the information might be of use to other people, especially if they are using free email forwarding from a domain provider without an SMTP server.

That is exactly the situation I was referring to.

In reply to a post by Oliver341:

In reply to a post by keith969:

True, but using your own domain smpt server has its advanges. I don't use my btinternet.com - why should I when I have my own?

Up to you. But the information might be of use to other people, especially if they are using free email forwarding from a domain provider without an SMTP server.

There is less and less of this these days, as if you don't have an SPF / DomainKeys record, many businesses and big ISPs (e.g. AOL, Hotmail/outlook, Gmail) will tag your message as spam. Its a lot easier to do spam management if the domain publishes the servers it sends through. Yes it breaks the flexibility of SMTP but the spammers did that first

www.authsmtp.com is another option - costs though.

In reply to a post by jchamier:

There is less and less of this these days, as if you don't have an SPF / DomainKeys record, many businesses and big ISPs (e.g. AOL, Hotmail/outlook, Gmail) will tag your message as spam.

No problem. For their txt record the domain owners merely need to use this, which will authorise BT's SMTP servers for their domain:

v=spf1 ip4:65.20.0.0/24 include:bt.com include:_spf.mail.yahoo.com ~all

In reply to a post by ukwiz:

That is exactly the situation I was referring to.

Indeed. BT's SMTP with authentication server allows third party from addresses, just like O2's smtp.o2.co.uk did (which I explained 18 months ago).

Edited by Oliver341 (Fri 28-Aug-15 19:05:36)

In reply to a post by Oliver341:

No problem. For their txt record the domain owners merely need to use this, which will authorise BT's SMTP servers for their domain:

Yes they need to do it. In which case why not use the preconfigured one? Seriously how many domain email hosts don't provide authenticated smtp these days, has to be some really cheap vendors.

In reply to a post by jchamier:

Seriously how many domain email hosts don't provide authenticated smtp these days, has to be some really cheap vendors.

A lot of domain hosts throw in email forwarding for free with the domain hosting fees, e.g. 123-reg. They don't include the use of an SMTP server. In that case the customer can forward to their ISP mailbox and set their client to send from their domain name instead of their ISP address.

It's a cheap solution I agree and not one I'd choose, but setting the correct SPF record makes it workable.

Same here, no problems with IMAP.

There was a bit of a problem when Sky moved their email from Google to Yahoo because Yahoo didn't/doesn't support IMAP unless you were already using IMAP when the transition occurred.

In reply to a post by simon194:

Yahoo didn't/doesn't support IMAP unless you were already using IMAP when the transition occurred

Yahoo has supported IMAP for many years for all their customers, transitioned or otherwise: https://help.yahoo.com/kb/SLN4075.html

Of course when using Sky it's advisable to use the Sky hostnames instead: http://help.sky.com/articles/get-emails-on-other-cli...

Obviously if the customer was using POP when the transition occurred they would have had to alter their client settings if they wanted IMAP instead, and some people used Gmail hostnames instead of Sky ones meaning the transition to Yahoo's POP/IMAP servers would have failed for them until they switched to Sky hostnames.