I used to use Port 587 on my RaQ4i to get around Port 25 being blocked by my
ISP. It worked with POP before SMTP just fine. On my BQ though, I still
use Port 587 to bypass the Port 25 blocking. I do it because I want to send
my email out of my server, but I have to have my ISP's domain name
configured under the "Relay for..." section of the email configuration,
though. If not, I get halted by the server because my IP address is in
Sorbs.net's blacklisted zone for dynamic IP addresses.
Because of that, your roaming users are going to have difficulty providing
you with who THEIR relaying ISP is going to be if they are in different
hotels when they want to access. This hotel might use Qwest while this
other hotel might use AT&T. And you don't want to turn it into an open
relay system.
What about the users using Webmail on your server? That way they don't need
to know who their hosting ISP is on any given night. They just log into to
webmail, read and respond, and the messages will still be waiting for them
to download the next time they are in the office.
-----Original Message-----
From: User Ernie [mailto:ernie (at mark) info.eis.net.au]
Sent: Wednesday, May 10, 2006 12:09 AM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:05117] Can I enable port 587 smtp for roaming users?
Can I enable port 587 message submission for roaming users under BQ?
I have a bunch of users that have been using POP before smtp to relay but
they are encountering port 25 blocks in a lot of hotels they stay at so they
can't send anyway. It was suggested that RFC 2476 message submission on port
587 might be an answer but I don't know how to enable that.
Any ideas?
- Ernie.