However, it does not work from ISPs that block outbound port 25 connections, which is why port 587 is recommended for this purpose.
Anyone seeing port 587 blocked is probably behind a corporate firewall that is blocking everything bar port 80 maybe, and should respect that company's policy of not allowing outbound mail from their network.
The company policy might be as simple as not allowing any direct outgoing connections (including port 80). In which case you might be allowed to use their SMTP server to send email and/or their proxy for HTTP from isolated segment of network. I've seen this at several places I visited in the past (although, at most places rules were very liberal, allowing all direct outgoing connections).
The traveling third party is, by definition, a roaming user. Not *your* roaming user, but a roaming user nonetheless. It's up to that user's organization to provide them with usable email connectivity.
Not really. It's up to the ISP to provide connecting user with usable email connectivity. User's original organization / company / network / whatever that provides SMTP AUTH is an nice and usable extra feature, not a requirement.
-- Aleksandar Milivojevic <amilivojevic@xxxxxx> Pollard Banknote Limited Systems Administrator 1499 Buffalo Place Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7
