Viktor I apologize for the confusion.
An overview of the smtp connection/transaction is as follows: Remote Server/Client with public IP is configured with the following transport: "domainofserver.org smtp:domainofserver.org:587" Mail from Remote Server/Client is accepted by domainofserver.org & bypasses the postfix spamassassin. The mail server accepting the mail is configured with a the following master.cf filter. "smtp inet n - n - - smtpd -o content_filter=spamassassin" At this point it appears that all mail from "Remote Server/Client" is passed directly without being filtered by the spamassassin. However mail from the internet that is sent via smtp without transport mapping is filtered as anticipated. Hoping to clarify if possible how to reject the Remote Server/Client "transport" mail and if so how what configuration etc are needed. The question specfic to "master_service_disable" was an attempt to determine if the mail is being passed is due to it not being considered "inet" and perhaps due to the transport being considered a postdrop queue. Perhaps an smtpd_command_filter is an option however it is unknown what smtp commands are allowing the mail to be accepted as a "postrdrop queue" localhost.localdomain email instead of an smtp inet mail that is normally processed by spamassassin. Regards Patrick -----Original Message----- From: owner-postfix-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: > 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 know what "restricting remote transport mappings" means. > ... it appears that master_service_disable allows for specific > listeners to be disabled. As does commenting out entries in master.cf, but the ability to easily turn them back on when needed makes "master_service_disable" useful in some cases. > However the type of listener/service specific to transport mappings "587 > submission" is unclear. What is "transport mapping 587 submission". Do you mean the optional (commented out in the stock master.cf file from postfix.org) submission service entry in master.cf? > Essentially transport mappings are currently bypassing the unix spamc. No idea what that means. > If possible please clarify if transport mappings can be restricted or > "forwarded" to the unix spamc. Or this. You'll to explain your goals more clearly. Most importantly explain what you're really trying to achieve, rather than difficulties with a particular, possibly less than ideal approach to getting there. -- Viktor.
