Re: Question on embedded variables in postconf command

Sorry, Viktor, I was not clear in my intent. This is for a guide that uses a number of interactive environment variables to build lots of conf files that are needed, it seems, for a mail server. So the variables are long gone when the server is up and running. Thus for main.cf, I want to

unused parameter: virtual_mailbox_limit_maps

I found one article: https://www.howtoforge.com/community/threads/postfix-warning-undefined-parameter-virtual_mailbox_limit_maps.71474/ that says it is not required anymore. To remove it. I am *assuming* that I then also remove: /etc/postfix/mysql-virtual_mailbox_limit_maps.cf I looked

Re: Bypass restrictions for postmaster/abuse

On Thu, Mar 09, 2017 at 04:12:32PM -0800, MRob wrote: > On 2017-03-09 14:35, /dev/rob0 wrote: > >On Thu, Mar 09, 2017 at 12:44:04PM -0800, MRob wrote: > >>Are there any admins with opinions where in the order is best > >>for postmaster/abuse whitelisting? > > > >My opinion is "don't do it." I use

Re: Testing reject_unknown_client_hostname

On 10/03/17 12:44, Viktor Dukhovni wrote: On Mar 9, 2017, at 8:22 PM, MRob wrote: So is there any restriction that compares the client IP mapping with the HELO hostname? Nothing built-in Is that a bad idea? Yes. Unless the system you're receiving email from

Re: Question on embedded variables in postconf command

On 03/07/2017 02:43 PM, Peter wrote: On 08/03/17 08:00, Robert Moskowitz wrote: After a bit of reflection, I may have asked the wrong question. Perhaps a better question is does the substitution take place on processing the option? It would take place at runtime (I believe). If you want it

Re: Setting amavis content_filter in main.cf

Thank you for this. I will review it. One comment I got over on the amavis list was that not to filter from localhost. Like mail sent from logwatch. How does this handle localhost sent mail? On 03/09/2017 06:01 AM, chaouche yacine wrote: Hello Robert, Here's my setup : in main.cf :

Re: Setting amavis content_filter in main.cf

Interesting question. In my master.cf, I have two smtp services : one is listening on the internet SMTP port (25) and the other is listening locally on a unix socket root@messagerie-secours[CHROOT][10.10.10.19] /home/serveur # grep ^smtp /etc/postfix/master.cf smtp inet n -

Question about Postfix/Nginx integration / XCLIENT support

Hi, I’m playing with using Nginx as an IMAP and SMTP proxy for our mail servers, as it will help us migrate and horizontally scale. Sorted the Nginx/Cyrus stuff out, and can proxy IMAP sessions to multiple back end mail servers. The problem I'm having, is trying to use a standard mail client to

Re: unused parameter: virtual_mailbox_limit_maps

On Thu, Mar 09, 2017 at 11:04:02AM -0500, Robert Moskowitz wrote: > I found one article: > > https://www.howtoforge.com/community/threads/postfix-warning-undefined-parameter-virtual_mailbox_limit_maps.71474/ > > that says it is not required anymore. It never was a part of Postfix. This was

Testing reject_unknown_client_hostname

Hello, in Postfix v3.1 I'm having a hard time getting reject_unknown_client_hostname to bounce test messages. I set an external host's Postfix myhostname to be purposefully incorrect, like nosuchhost.example.com and sent a message to the test system. If I have reject_unknown_helo_hostname

Re: Bypass restrictions for postmaster/abuse

On 2017-03-08 15:23, Noel Jones wrote: On 3/8/2017 2:53 PM, MRob wrote: Hello all, Is there a best practices for exempting the postmaster/abuse address from certain smtpd_mumble_restrictions? The procedure to whitelist a recipient is to use a check_recipient_access map prior to whatever

Re: Testing reject_unknown_client_hostname

On 2017-03-09 13:06, Noel Jones wrote: On 3/9/2017 2:58 PM, MRob wrote: Hello, in Postfix v3.1 I'm having a hard time getting reject_unknown_client_hostname to bounce test messages. See the docs for what this rejects. http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname

Re: Bypass restrictions for postmaster/abuse

On Thu, Mar 09, 2017 at 12:44:04PM -0800, MRob wrote: > Are there any admins with opinions where in the order is best > for postmaster/abuse whitelisting? My opinion is "don't do it." I use smtpd_reject_footer to point to my web page for frustrated human senders. If they're not smart enough

Re: Question about Postfix/Nginx integration / XCLIENT support

> On 9 Mar 2017, at 20:28, Marty Lee wrote: > > Hi, > > I’m playing with using Nginx as an IMAP and SMTP proxy for our mail servers, > as it will help us migrate and horizontally scale. Sorted the Nginx/Cyrus > stuff out, and can proxy IMAP sessions to multiple back

Re: Question on embedded variables in postconf command

On 10/03/17 04:20, Robert Moskowitz wrote: > I was not clear in my intent. No, you were not, and yet... > This is for a guide that uses a number of interactive environment > variables to build lots of conf files that are needed, it seems, for a > mail server. > > So the variables are long gone

Re: Question on embedded variables in postconf command

Ah, On 03/09/2017 10:13 AM, Viktor Dukhovni wrote: On Mar 9, 2017, at 9:54 AM, Robert Moskowitz wrote: I have modified my guide by setting interactive variables in the beginning and then using them throughout, so that it is not necessary (or much less) to modify stuff.

Re: Bypass restrictions for postmaster/abuse

On 2017-03-09 14:35, /dev/rob0 wrote: On Thu, Mar 09, 2017 at 12:44:04PM -0800, MRob wrote: Are there any admins with opinions where in the order is best for postmaster/abuse whitelisting? My opinion is "don't do it." I use smtpd_reject_footer to point to my web page for frustrated human

Re: Testing reject_unknown_client_hostname

On 2017-03-09 13:41, Noel Jones wrote: On 3/9/2017 3:16 PM, MRob wrote: obtained by HELO? Is there something in the tcp connection that identifies the hostname? Sorry if I misunderstood this part. The HELO name is not related to and doesn't matter for reject_unknown_client_hostname. Perhaps

Re: Testing reject_unknown_client_hostname

> On Mar 9, 2017, at 8:22 PM, MRob wrote: > > So is there any restriction that compares the client IP mapping with the HELO > hostname? Nothing built-in > Is that a bad idea? Yes. -- Viktor.

Re: Setting amavis content_filter in main.cf

> One comment I got over on the amavis list was that not to filter from > localhost. Like mail sent from logwatch. How does this handle > localhost sent mail? Those submit through the pickup service, simply donk the content_filter on the pickup service similar to how you do it on port 10025.

Re: Question on embedded variables in postconf command

On 10/03/17 12:59, Robert Moskowitz wrote: > There appears to be a difference between what you show above and what I > tested: > > So I did a little googling and learned the difference: > > http://stackoverflow.com/questions/6697753/difference-between-single-and-double-quotes-in-bash Yep, you

Re: Testing reject_unknown_client_hostname

On 3/9/2017 2:58 PM, MRob wrote: > Hello, in Postfix v3.1 I'm having a hard time getting > reject_unknown_client_hostname to bounce test messages. See the docs for what this rejects. http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname Warning: this is a very strict test likely

Re: Testing reject_unknown_client_hostname

On 3/9/2017 3:16 PM, MRob wrote: > obtained by HELO? Is there something in the tcp connection that > identifies the hostname? Sorry if I misunderstood this part. The HELO name is not related to and doesn't matter for reject_unknown_client_hostname. Perhaps you were confused by the different

Re: Testing reject_unknown_client_hostname

On 2017-03-09 13:41, Noel Jones wrote: On 3/9/2017 3:16 PM, MRob wrote: obtained by HELO? Is there something in the tcp connection that identifies the hostname? Sorry if I misunderstood this part. The HELO name is not related to and doesn't matter for reject_unknown_client_hostname. Perhaps

Re: Question on embedded variables in postconf command

> On Mar 9, 2017, at 9:54 AM, Robert Moskowitz wrote: > > I have modified my guide by setting interactive variables in the beginning > and then using them throughout, so that it is not necessary (or much less) to > modify stuff. I came up with: > > eval $(echo

Re: Bypass restrictions for postmaster/abuse

> On Mar 10, 2017, at 12:03 AM, /dev/rob0 wrote: > > Sure, you can do what you want, and in theory it sounds prudent to > exempt postmaster & abuse from spam controls, but in practice, it > turns out only to be a way to get yourself a lot more spam. > > I don't have enough

Re: Postfix, Hotmail never arrive

On 2017-03-08 (07:54 MST), Sebastian Wiesinger wrote: > > So I'm blocked, the block can't be mitigated and they will not tell me > why I was blocked. Sounds about right. -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

Re: Bypass restrictions for postmaster/abuse

On 2017-03-08 Noel Jones wrote: > On 3/8/2017 2:53 PM, MRob wrote: >> Is there a best practices for exempting the postmaster/abuse address >> from certain smtpd_mumble_restrictions? > > The procedure to whitelist a recipient is to use a > check_recipient_access map prior to whatever rule might

Re: postfix upgrade-configuration messes up main.cf (candidate patch)

On 08/03/17 19:08, Viktor Dukhovni wrote: On Wed, Mar 08, 2017 at 11:10:45AM -0500, Viktor Dukhovni wrote: On Mar 8, 2017, at 9:03 AM, Mario Theodoridis wrote: /usr/sbin/postfix set-permissions upgrade-configuration \ config_directory=/etc/postfix \

Re: Setting amavis content_filter in main.cf

Hello Robert, Here's my setup : in main.cf : content_filter = amavis:[127.0.0.1]:10024 This tells postfix to use the amavis "service" (defined later in master.cf) to send all incoming mails to localhost port 10024 in master.cf : amavis unix - - - - 2 smtp -o

Re: postfix upgrade-configuration messes up main.cf

On 08/03/17 16:48, Wietse Venema wrote: Mario Theodoridis: Hello everyone, i'm having a problem upgrading to Centos-6.8 from an older 6.x version. The problem is created when the rpm post script runs the below command: File a bug with CentOS. Some distros make improvements that screw up