RE: Postfix transport - master_service_disable

2016-09-15 Thread postadmin
>Of course, because the content_filter is defined just for the port Ok, Thanks understood. Regards Patrick

Re: Postfix transport - master_service_disable

2016-09-15 Thread Viktor Dukhovni
On Thu, Sep 15, 2016 at 10:36:43AM -0500, postadmin wrote: > Remote Server/Client with public IP is configured with the following > transport: > > "domainofserver.org smtp:domainofserver.org:587" You're providing submission service to suitably authorized clients. Presumably via SASL, clie

RE: Postfix transport - master_service_disable

2016-09-15 Thread postadmin
stfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Viktor Dukhovni Sent: Thursday, September 15, 2016 9:56 AM To: postfix-users@postfix.org Subject: Re: Postfix transport - master_service_disable On Wed, Sep 14, 2016 at 12:23:17PM -0500, postadmin wrote: > Hop

Re: Postfix transport - master_service_disable

2016-09-15 Thread Viktor Dukhovni
On Wed, Sep 14, 2016 at 12:23:17PM -0500, postadmin wrote: > Hoping to clarify if remote transport mappings can be restricted. This sentence employes unusual terminology. It is unlikely to be understood here. Please explain yourself more clearly, avoiding dense jargon. Nobody on this list will

Postfix transport - master_service_disable

2016-09-14 Thread postadmin
Hi List Hoping to clarify if remote transport mappings can be restricted. At this point it appears that master_service_disable allows for specific listeners to be disabled. However the type of listener/service specific to transport mappings "587 submission" is unclear. Essentially t