Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

Just following up to close this discussion. On Sun, 2012-05-06 at 09:35:24 -0400, Wietse Venema wrote: > Sahil Tandon: > > May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: psc_dnsbl_request: > > connect to private/dnsblog service: Connection refused > > May 5 10:00:26 mx1 last message

Re: Syntax error in main.cf

Please don't top post, it's annoying. On 13/05/12 13:59, gabrielt...@gmail.com wrote: > From: Peter > Date: Sun, 13 May 2012 11:37:31 > > On 13/05/12 10:17, gabrielt...@gmail.com wrote: >> postfix: fatal: /etc/postfix/main.cf, line 30: missing '=' after >> attribute name: "This file lists only

Re: Syntax error in main.cf

On 13/05/2012 04:59, gabrielt...@gmail.com wrote: This is strange, when I go to the line that the error is refering (with nano +30 /etc/postfix/main.cf) the editor opens right in the queue_directory line, so I put a # in that line for testing and run postfix check again, and I then receive an

Re: Syntax error in main.cf

This is strange, when I go to the line that the error is refering (with nano +30 /etc/postfix/main.cf) the editor opens right in the queue_directory line, so I put a # in that line for testing and run postfix check again, and I then receive an error in the command_directory line, which is also w

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

Vladimir V Kutyavin: > On 12.05.2012 23:48, Wietse Venema wrote: > > Override the option FOR THE COMMAND CONFIGURED IN THAT LINE. Wietse > > Now I understand it, but it was not clear from the manual. Inaccurate > documentation. If you are so smart, then you can post a diff. Wietse

Re: Syntax error in main.cf

On 13/05/12 10:17, gabrielt...@gmail.com wrote: > postfix: fatal: /etc/postfix/main.cf, line 30: missing '=' after > attribute name: "This file lists only a subset" WAG: Looks like you're missing a hash mark (#) at the beginning of the line to denote a comment. > queue_directory = /var/spool/post

Re: Syntax error in main.cf

Am 13.05.2012 00:17, schrieb gabrielt...@gmail.com: > Im having a strange issue on a new postfix setup, when I run the command > "postfix check" I receive the following error: > > postfix: fatal: /etc/postfix/main.cf, line 30: missing '=' after attribute > name: "This file lists only a subset"

Syntax error in main.cf

Hi all, Im having a strange issue on a new postfix setup, when I run the command "postfix check" I receive the following error: postfix: fatal: /etc/postfix/main.cf, line 30: missing '=' after attribute name: "This file lists only a subset" However, when I check that line, all seems to be in o

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

On 12.05.2012 23:48, Wietse Venema wrote: Override the option FOR THE COMMAND CONFIGURED IN THAT LINE. Wietse Now I understand it, but it was not clear from the manual. Inaccurate documentation.

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

On 13.05.2012 00:51, Peter wrote: On 13/05/12 05:04, Владимир Кутявин wrote: Ok there. Any way to make postfix do bcc for themessages from specified sender to specified recipient? sender_bcc_maps Peter I want to copy (all messages from a...@domain.org to a2.anotherdomain.org) to a...@domain.

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

On 13/05/12 05:04, Владимир Кутявин wrote: > Ok there. Any way to make postfix do bcc for themessages from specified > sender to specified recipient? sender_bcc_maps Peter

Re: postscreen - access list does not appear to be working

Chad M Stewart: > I don't understand why the IP would be whitelisted. I had stopped > postfix, removed the postscreen cache and restarted postfix, thus > no cache and this is the first time the IP has connected. Any > ideas? Wietse: > Because you have still have postscreen_blacklist_action = igno

Re: postscreen - access list does not appear to be working

On May 12, 2012, at 2:49 PM, Wietse Venema wrote: > Chad M Stewart: >> >> I don't understand why the IP would be whitelisted. I had stopped postfix, >> removed the postscreen cache and restarted postfix, thus no cache and this >> is the first time the IP has connected. Any ideas? > > Because

Re: postscreen - access list does not appear to be working

Chad M Stewart: > > It can be nice to have stupid systems out there that repeatedly connect and > try to deliver junk, I can use for testing new rules. :) I'm trying to test > blacklists in postscreen. From what I read on the postscreen readme, the > following should work to block this IP, bu

postscreen - access list does not appear to be working

It can be nice to have stupid systems out there that repeatedly connect and try to deliver junk, I can use for testing new rules. :) I'm trying to test blacklists in postscreen. From what I read on the postscreen readme, the following should work to block this IP, but alas the IP is still abl

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

On 12.05.2012 17:07, Wietse Venema wrote: As documented in the smtpd(8) manpage, always_bcc is not an smtpd(8) feature. I put a great deal of effort to provide accurate documentation. I would appreciate it if you would take the effort to read it. Wietse As documented in the master(5) -o nam

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

On Sat, May 12, 2012 at 03:28:08PM +0400, Vladimir V Kutyavin wrote: > I have set this trigger for the specification of non-default options > with key -o, I need to override always_bcc option: > > 127.0.0.1:10027 inet n - n - 10 smtpd > -o content_filter= > -o smtpd_sender_restrictions= >

Re: Postfix ignores -o always_bcc and -o recipient_bcc_maps

> with key -o, I need to override always_bcc option: > > 127.0.0.1:10027 inet n - n - 10 smtpd > -o content_filter= > -o smtpd_sender_restrictions= > -o always_bcc=c...@aaa.org As documented in the smtpd(8) manpage, always_bcc is not an smtpd(8) feature. I put a great deal of

Postfix ignores -o always_bcc and -o recipient_bcc_maps

I need to set bcc for messages from specified sender to specified recipient. smtpd_sender_restrictions = <...> check_sender_access mysql:/etc/postfix/mysql/mysql-sender.cf <...> For my sender adress vl...@aaa.org it resolves 'FILTER smtp: