Don't forget since you're essentially sending the email from one of your servers to another you can use any port you want on your home side...inbound 25 blocked? No prob use 10025 on your transport_map or any unblocked port you want.
On June 10, 2019 12:14:39 AM UTC, "Ronald F. Guilmette" <r...@tristatelogic.com> wrote: > >In message <40a97779-669c-e145-e3ec-fc82c9290...@pccc.com>, >"Kevin A. McGrail" <kmcgr...@pccc.com> wrote: > >>On 6/9/2019 6:18 PM, Ronald F. Guilmette wrote: >>> One part that I'm sure that I -do not- understand is why you >suggeted an >>> alternative port number. Can you explain? >> >>Almost every residential ISP will block ports like 25 and 80 so you >>can't run servers on the connections... > >I'm not too sure about that. > >*Outbound* port 25, yes. Lots of providers of end-luser lines do block >that, as they most certainly should... with some exceptions. > >But for my outbound mail, that's not an issue. I plan to have my mail >client just give stuff (on 587) directly to -somebody's- smarthost... >either my own or somebody else's. > >With regards to *inbound* traffic with IP dest set to 25 or 80... I >don't >think that most providers give a rat's ass about that... except maybe >Comcast, who may indeed block it, just as a way of extorting even more >money out of their victims for "upgrades" to "business class" service. >But I don't think my provider is one of the ones that plays those >games. > >I guess I'll find out, soon enough. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
