[PANTUGGeneral] Collegeville, PA FiOS now blocking outgoing port 25

[JP Vossen]

I *think*... I did not fully test it, but as of last night/early this
morning, I was unable to connect to my hosted server on port 25. The
server was up and fine, sIMAP & SSH worked fine, and port 25 to that
server worked from elsewhere (Comcast in NJ, among others).

The solution is easy enough, if slightly tedious:

1) On the server, vi /etc/postfix/master.cf and uncomment the
"submission" line, then restart postfix.
1.1) Make sure 'submission' is defined in /etc/services:
grep '^submission' /etc/services

2) Change all the client configs to use port 587 in the GUI
(workstations) or the Nullmailler config (servers), e.g.:
sudo sh -c "echo 'mail.example.com smtp --port=587' \ >
/etc/nullmailer/remotes" && cat /etc/nullmailer/remotes
--or--
vi etc/postfix/main.cf # for internal postfix hub
relayhost = mail.example.com:587

I'm not sure messing with /etc/postfix/master.cf is the *best* solution,
since that will now collide with future package updates. It wasn't
obvious how to do that in main.cf, and this was quick & dirty & worked.
OTOH, that's what this says to do too:
https://help.ubuntu.com/community/Postfix#Using%20Port%20587%20for%20Secure%20Submission

Later,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP |:::======| http://bashcookbook.com/
My Account, My Opinions |=========| http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
_______________________________________________
PANTUGGeneral mailing list: PANTUG...@lists.pantug.org
To remove your address or change your delivery options see:
http://lists.pantug.org/mailman/listinfo/pantuggeneral
For the searchable archives see:
http://groups.google.com/group/pantug/

[David Dows]

Yeah, did you get a notice from FiOS that they were going to do this? I
found out about it on Wednesday or Thursday, when none of my systems
could send email.

They claimed to have sent notice a while ago. My Vz email forwards to my
real address & I don't have anything from them.

Switching all of my email clients to 587 worked for several accounts
with usa.net, 1&1 and others on several different systems.

[JP Vossen]

> JP Vossen wrote:
>> I *think*... I did not fully test it, but as of last night/early this
>> morning, I was unable to connect to my hosted server on port 25. The
>> server was up and fine, sIMAP & SSH worked fine, and port 25 to that
>> server worked from elsewhere (Comcast in NJ, among others).

...

David Dows wrote:
> Yeah, did you get a notice from FiOS that they were going to do this? I
> found out about it on Wednesday or Thursday, when none of my systems
> could send email.
>
> They claimed to have sent notice a while ago. My Vz email forwards to my
> real address & I don't have anything from them.
>
> Switching all of my email clients to 587 worked for several accounts
> with usa.net, 1&1 and others on several different systems.

A few people pointed something like that out on the PLUG list too.

Yes, it turns out I did get a notice, but the subject was "Important
Changes to your Verizon FiOS Email Account" so I filed and ignore it
**since I don't use that.** Idiots. All they needed to do was use a
useful subject line, like "Important Changes to Verizon FiOS Email
settings". Date was 04/27/2010 02:13 PM.

Sigh,