Apr 3 2008, 01:13 AM
QUOTE(husagi @ Mar 31 2008, 11:19 AM)
Yes, good policy. But someone left his/her brains at home or in the trash.
Their announcement states that "Streamyx customers with dynamic IP addresses, who have their own mail server will not be able to send out-going e-mails", but engineer's implemention was "block everything with source AND destination port =25, unless IP address resolves to smtp.streamyx.com / smtp.tm.net.my". Ceh. Seems to me, their policy makers did not clearly define "outbound SMTP" -- whether that means only traffic whose source port =25, or, traffic whose source OR destination port =25. The annoucement should've been more precise.
To date, I can still send out-going emails from my home email server at port 25 (default SMTP) and receive new in-coming emails to my home email server at port 110 (default POP3) by using dynamic IP address. And, I register my dynamic IP address with a dynamic domain name. So, I don't have to refer to my current dynamic IP address in my email client settings. I am using Streamyx account and I don't abuse it. The important thing is to check the port forwarding of your router to make sure it allows port 25 and port 110. And, your email server should be able to deny open relays to port 25.Their announcement states that "Streamyx customers with dynamic IP addresses, who have their own mail server will not be able to send out-going e-mails", but engineer's implemention was "block everything with source AND destination port =25, unless IP address resolves to smtp.streamyx.com / smtp.tm.net.my". Ceh. Seems to me, their policy makers did not clearly define "outbound SMTP" -- whether that means only traffic whose source port =25, or, traffic whose source OR destination port =25. The annoucement should've been more precise.
This post has been edited by eclectice: Apr 3 2008, 01:29 AM
Quote
0.0148sec
0.62
6 queries
GZIP Disabled