SSE

Would SSE come under this forum?

As they appear to be using Daisy Wholesale, then yes. This is where you would post about them.

Cheers.

No worries.

I was looking into them today and came across that little bit of info.

Anyone use SSe for their broadband?

Do they block port 25?

In reply to a post by hk11:

Do they block port 25?

I would doubt it, as its a port for SMTP email.

No real reason to block it as standard.

EDIT : Well, there 'might' be a reason. To stop bulk emails. But, tbh its a bit of a lame reason. Can you not use a different port to send your email? I assume you ask as you cannot send emails on your SSE connection.

Your email provider will likely have another port for SMTP, possibly 465 or 587.

Edited by deleted (Tue 26-May-15 10:13:31)

I'm currently with EE and they block port 25, as do AOL. I think this is becoming more common with ISPs now, which is fine if they have an option to remove the block.

Was just checking if SSE have a policy, as I don't want to have to mess around redirecting mail as I have to now.

Ah, I have no idea.

Im not on SSE, im with Virgin, I will see if I can find out however.

LOL : That's why I was asking if anyone was with them.

Thanks.

Port 25 is unsecured. I've never yet found an email host that doesn't have a secured (SSL/TLS) SMTP port. You don't have any additional actions to take at your end.

Similarly with POP3/IMAP. There will be a secure port instead of the unsecured one I expect you are using. I gather you have your own mail server, so why use port 25?

It would help if you clarified the question.

Are you asking about outgoing TCP port 25 blocking, incoming TCP port 25 blocking or both?


Some ISPs block outgoing TCP port 25 to force e-mail to go via a smarthost (to which you typically connect on TCP port 587, authenticating either by your IP address or with ISP issued credentials). This is done to help prevent spamming, including malware sending e-mail direct to mail exchangers.

I was asking about incomming and outgoing, but would be interested in *any* port restrictions that the ISP is imposing

TIA
.

Just to add to my previous post, Tsohost for example provide IMAP on 993 and SMTP on 465. No ISP blocks those so far as I know.

Port 25 is the default port used to transport or communicate email across the Internet using the SMTP protocol.

I'm currently using different ports, but it involves using another server and I'd prefer to keep things simple.

Thanks.

Not familiar with that one. Will continue to use a different port if I need to, but like I said would prefer to keep things simple.

It's not complicated from the user point of view. Just select the host's port. If you are running your own server then I don't know what is involved in presenting such ports to the rest of the world.

In reply to a post by hk11:

I'm currently with EE and they block port 25, as do AOL. I think this is becoming more common with ISPs now, which is fine if they have an option to remove the block.

Was just checking if SSE have a policy, as I don't want to have to mess around redirecting mail as I have to now.

Just my two penny worth on this. It rather depends on what you are using as your reply address. If it is the email address provided by the ISP and you were physically connected to their network, then outgoing emails via port 25 will probably work just fine. Port 26 may also be available.

However I sort of gain the impression that you have your own domain name and it might therefore be more beneficial to use the SMTP facilities provided by that service.

Lastly wherever possible consider using IMAP rather the POP3.

And as a footnote, before signing up with SSE read carefully all the comments on this website to determine if you wish to tie yourself into SSE for your broadband service for quite a while.

Thanks Trolley.

Yes, own domain and own email server, but do use fetchmail to collect some old ISP mail, so for example freeserve address works OK on my current EE connection as it is really Orange.

I don't use domain name suppliers service, POP or IMAP (other than on the above old accounts). It's direct connection SMTP via exim.

Didn't realise there was any time tie-in, other than the normal contract, but will check SSE's website: cheers.

Edit: You say "this website". I did a search but couldn't find anything else on SSE, other than my two posts.

Edited by hk11 (Tue 26-May-15 20:06:53)

Having had a good look through their T&Cs, I can find no reference to blocking Port 25 for EMail.

Seems your good to go.

Thanks.

Just got to get my MAC from EE now. They said 5 days, but as usual .......

In looking for any ISP's port blocking policy you should search for their 'TRAFFIC MANAGEMENT KEY FACTS INDICATOR (KFI)'. It's a voluntary code but most ISPs have 1.

Looks like SSE don't belong .

Edited by XRaySpeX (Wed 27-May-15 14:49:34)

Could that be because they are a reseller?

Could be. Had a look at Daisy, if that's who they resell. Could not find any KPI, but found these 2 relevant contradictory statements in Broadband Acceptable Use Policy:

Sharing internet access on a private network and running personal SMTP mail servers
Some methods of sharing internet access or applications expose your external internet connection to other internet users, and enable them to send unsolicited bulk emails via your computer (known as spam).

As Daisy do not block any ports it is vital that you configure your network securely, you are fully responsible for security in your own network and failure to secure it properly will result in your disconnection from Daisy services.

Setting up your mail server (open relay)
If you choose to run an SMTP email server on a private network on your premises you must ensure that it is configured correctly, so as to only accept mail from your private domain. Daisy will block access (TCP port 25), to your SMTP email server from outside of your domain to prevent it from being exploited for the purpose of sending unsolicited emails

Yes, clear as mud there.

It makes sense for ISPs to block port 25, but there should be an option to unblock if required and if it can be shown to be secure.

In reply to a post by hk11:

I'm currently with EE and they block port 25, as do AOL.

Both EE & AOL do have an Authenticated SMTP on port 587.

Believe EE only brought it in for their mobile users, who are on a diff network from the BB network, whose users can use the standard unauthenticated port 25 SMTP that is blocked to the mobile networks. It wasn't there 2-3 years ago.

Ah, yes. Daisy...

SSE do use Daisy Wholesale as far as I can tell. (Still doing some investigation on that side, lol.)

So, Port 25 WILL be blocked.

According to above post "Daisy do not block any ports"

!

On TTB with Xilo, first hop is daisy port 25 open.

Don't think it is out that is the problem, but inbound according to XraySpex.

Hi,

I stumbled across this thread while looking for an smtp solution for my father who has SSE. He says SSE had told him they do not have have an smtp server he can use.

Thanks to this thread and azrael316 in particular but also the OP for bringing it up, I have searched for a daisy smtp server and found https://daisygroup.com/resource-centre/can-tell-dais... authored by a daisy employee which stated on 27/9/13 that " The SMTP server address is as follows: smtp.daisybb.co.uk "

I have told my father but he has not let me know if it worked or not and I know it was not strictly the OP's question but I am posting here in case it helps anyone else.

Edited by ren7 (Tue 08-Sep-15 01:24:58)

Im with them, although speeds started off very slow on ultra fast fibre, my download speed showed at 57, but on testmynet it was only 1.3mbs , it has now gone up to 57mbs, I dont know if several calls of complaint have made this happen or what, but for £24.50pm for line and BB, im quite happy. Oh I removed netintelligence and speeds went up,

Cheers for that.

I'm still unsure about commiting for longer than a 12 month contract though.