i suppose i could just ask the help desk in the am, but i'm sure others will also want to know:
what are the I-Go Everywhere pop3, smtp servers?
ic
what are the I-Go Everywhere pop3, smtp servers?
ic
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Have you ever been to an airshow?
POP3 & SMTP servers?
- Thread starter ic
- Start date
anakin
Well-Known Member
POP3 and other bundled ISP services will become available sometime during the course of the softlaunch. For the meantime, one can use smtp.wbs.co.za to relay mail from iBurst connections.
<hr noshade size="1"><center><i><font size="1">
My views are mine, and mine alone.<br /></i></font id="size1"></center>
<hr noshade size="1"><center><i><font size="1">
My views are mine, and mine alone.<br /></i></font id="size1"></center>
Kaptain Khaos
Active Member
or uunet.co.za as they are there upstream provider
<b>in chaos all things are harmonious</b>
<i>Tower 82 14% Signal 512k package </i>
<b>in chaos all things are harmonious</b>
<i>Tower 82 14% Signal 512k package </i>
I'm confussed, please someone knock some sense into me...
I don't understand why i haven't needed to change my smtp server settings (since ditching my isdn dialup isp and using iBurst).
I was expecting outlook2k to complain that smtp.%previsp%.co.za was unreachable, but it never did, and everything just got sent (and yes emails were delivered without any bouncing).
I was expecting smtp.%previsp%.co.za to be behind a firewall and unreachable from iBurst.
So here's the weird thing, according to the headers in several (if not all) emails i've sent since i've been on iBurst, it says that the email was received (sent) by smtp.%previsp%.co.za, so how'd it do that?
To confuse things even more, i've just tried ping'ing and tracert for smtp.%previsp%.co.za and i get 100% packet loss, request timed out.
The only thing that makes sense to me, is that %previsp%.co.za will let smtp traffic bound for port 25 thru from the net, but surely it should only be allowed though via their dial-up network and not iBurst?
If you think knowing what %previsp% is will help solve my mystery, email me & i will reveal the sucker for the apparent junk mailer's paradise it appears to be.
I don't understand why i haven't needed to change my smtp server settings (since ditching my isdn dialup isp and using iBurst).
I was expecting outlook2k to complain that smtp.%previsp%.co.za was unreachable, but it never did, and everything just got sent (and yes emails were delivered without any bouncing).
I was expecting smtp.%previsp%.co.za to be behind a firewall and unreachable from iBurst.
So here's the weird thing, according to the headers in several (if not all) emails i've sent since i've been on iBurst, it says that the email was received (sent) by smtp.%previsp%.co.za, so how'd it do that?
To confuse things even more, i've just tried ping'ing and tracert for smtp.%previsp%.co.za and i get 100% packet loss, request timed out.
The only thing that makes sense to me, is that %previsp%.co.za will let smtp traffic bound for port 25 thru from the net, but surely it should only be allowed though via their dial-up network and not iBurst?
If you think knowing what %previsp% is will help solve my mystery, email me & i will reveal the sucker for the apparent junk mailer's paradise it appears to be.
Well open, perhaps not, there is still a username and password, so smtp.%previsp%.co.za has basic user authentication, but that doesn't stop joe spammer from trying to crack their way in, and send those anoying emails about v1agra etc etc etc...
This lapse in security ties in with what I've been seeing now for months in my firewall logs, blocking lots of attempts from both non-%previsp% as well as %previsp% ip addresses to scan the usual windows ports 137, 445 etc, plus from time to time apparently random port numbers being scanned always by non-%previsp%.
I complained to %previsp% and was told that I had to pay them to look at their logs & confirm what I was saying, so I left it, it just ended up slowing down my connection with all the extra traffic. I figured they'd eventually block some obvious port scanning traffic from outside their own ip address range, but they never did.
This lapse in security ties in with what I've been seeing now for months in my firewall logs, blocking lots of attempts from both non-%previsp% as well as %previsp% ip addresses to scan the usual windows ports 137, 445 etc, plus from time to time apparently random port numbers being scanned always by non-%previsp%.
I complained to %previsp% and was told that I had to pay them to look at their logs & confirm what I was saying, so I left it, it just ended up slowing down my connection with all the extra traffic. I figured they'd eventually block some obvious port scanning traffic from outside their own ip address range, but they never did.