Re: postmulti fatal error with 3.0.0

On Wed, Feb 18, 2015 at 02:11:34AM +0100, Andreas wrote: > On many systems (Debian, Arch, and probably more) daemon_directory is > /usr/lib/postfix as well, which will lead to a broken multi-instance > capability by default. Note that on BSD systems daemon_directory is /usr/libexec, and Linux FHS

Re: smtp_recipient_restrictions policy server

On 2/17/2015 9:03 PM, Viktor Dukhovni wrote: On Tue, Feb 17, 2015 at 08:52:12PM -0500, Rod K wrote: I want to create a policy server that will process once per recipient. My understanding is that this would work when placed under smtpd_recipient_restrictions. Is this correct? Yes. My other

Re: SMTP scanning server pool

Then I'm at a loss... Perhaps I missed a reload at a strange point or something. I shall keep an eye on it and follow up if there are any changes. Thank you very much for your assistance!! Cheers, Daniel On Wed, Feb 18, 2015 at 2:35 PM, Wietse Venema wrote: > Daniel Hopkirk - RandomInsanity: >

Re: smtp_recipient_restrictions policy server

On Tue, Feb 17, 2015 at 08:52:12PM -0500, Rod K wrote: > I want to create a policy server that will process once per recipient. My > understanding is that this would work when placed under > smtpd_recipient_restrictions. Is this correct? Yes. > My other question is will access results be honor

smtp_recipient_restrictions policy server

I've done a bit of research into this and I'm hoping someone can verify a conclusion and also answer one question that I cannot seem to find an answer for. I want to create a policy server that will process once per recipient. My understanding is that this would work when placed under smtpd_

Re: How I do to add headers by command?

Now it does work. However, the SMTP server wont send its queue/OK message until the hashcash generation is done, which means that client will timeout if hashcash generation takes too long. Any way to solve that? I wish hashcash generation start just when the mail is ready for dispatch, when the

Re: SMTP scanning server pool

Daniel Hopkirk - RandomInsanity: > However out of curiosity as much as clutching at straws I cleared the > verify cache and restarted postfix. After a couple of test emails it now > appears to be refusing the email instantly as expected. My best guess > would be that the invalid test address I was

Re: Transitioning from cyrus-SASL to dovecot-SASL

On Tue, Feb 17, 2015 at 05:21:52PM -0800, Rich Shepard wrote: > The thread I read said that dovecot does not work with smtp when outbound > messages are relayed and authenticated through another server. Is this > correct? If so, it looks like I need to stay with cyrus-sasl for both smtp > and sm

Re: Transitioning from cyrus-SASL to dovecot-SASL

On Tue, Feb 17, 2015 at 05:21:52PM -0800, Rich Shepard wrote: > The thread I read said that dovecot does not work with smtp when outbound > messages are relayed and authenticated through another server. Is this > correct? Sounds like nonsense to me. You can operate a port 587 submission service

Re: Transitioning from cyrus-SASL to dovecot-SASL

Rich Shepard: >The thread I read said that dovecot does not work with smtp when outbound > messages are relayed and authenticated through another server. Is this > correct? If so, it looks like I need to stay with cyrus-sasl for both smtp > and smtpd. Dovecot has no client support. Server only

Re: Transitioning from cyrus-SASL to dovecot-SASL

On Tue, 17 Feb 2015, Rich Shepard wrote: I'm not a professional SysAdmin or network admin but have been running my own smtpd using cyrus-SASL for years. I want now to transition to using dovecot-SASL and have difficulty correctly configuring dovecot. Found a web forum thread that seems to a

Re: postmulti fatal error with 3.0.0

Yes, this is what the error tells me, but is there any reason behind this? In the documentation i couldn't find any hint, why this should be a bad idea. Also i did not set this explicitly, but shlib_directory by default will be /usr/lib/postfix if compiled with shared=yes On many systems (Debian,

Re: postmulti fatal error with 3.0.0

On Tue, Feb 17, 2015 at 07:32:22PM -0500, Wietse Venema wrote: > > > # postmulti -l > > > postmulti: fatal: instance /etc/postfix, > > > shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, > > > daemon_directory=/usr/lib/postfix > > DO NOT set daemon_directory the same as shli

Re: SMTP scanning server pool

Ahh that makes sense; I'd just written the logging order off to multiple processes and flushing. Neither address_verify_poll_count nor address_verify_poll_delay are in the master.cf. It does use smtpd_proxy_filter (amavis) but I don't know if that can impact at this stage? This is indeed on VMWar

Re: postmulti fatal error with 3.0.0

Andreas: > Hi, > > i installed the new postfix-3.0.0 in my arch system, however by default > (default main.cf ) postmulti results in a fatal error > for a reason (conflict) i don't understand: > > > # postmulti -l > > postmulti: fatal: instance /etc/postfix, > > shlib_directory=/u

Re: How I do to add headers by command?

Sebastian Nielsen: > On the server, on mail put in outgoing queue (to be relayed), I > want to run the following command: /usr/bin/hashcash -mXb 26 > [recipient01] [recipient02] .. [recipientNN] Wietse: > Use a Milter, written in Python or Perl. It needs to receive the > "end of message" event and

Re: Transitioning from cyrus-SASL to dovecot-SASL [DONE]

On Tue, 17 Feb 2015, Wietse Venema wrote: Rich Shepard: Now the only remaining issue is the lack of double quotes around $path on line 504 of /usr/libexec/postfix/post-install. At worst after the next postfix upgrade, I'll just edit it by hand again. May I ask again, do you have spaces in

Re: Transitioning from cyrus-SASL to dovecot-SASL [DONE]

On Tue, Feb 17, 2015 at 03:01:38PM -0800, Rich Shepard wrote: > Now the only remaining issue is the lack of double quotes around $path on > line 504 of /usr/libexec/postfix/post-install. At worst after the next > postfix upgrade, I'll just edit it by hand again. I would not call this a "lack of

Re: Transitioning from cyrus-SASL to dovecot-SASL [DONE]

Rich Shepard: >Now the only remaining issue is the lack of double quotes around $path on > line 504 of /usr/libexec/postfix/post-install. At worst after the next > postfix upgrade, I'll just edit it by hand again. May I ask again, do you have spaces in pathnames? Wietse

postmulti fatal error with 3.0.0

Hi, i installed the new postfix-3.0.0 in my arch system, however by default (default main.cf ) postmulti results in a fatal error for a reason (conflict) i don't understand: > # postmulti -l > postmulti: fatal: instance /etc/postfix, > shlib_directory=/usr/lib/postfix conflicts wi

Re: How I do to add headers by command?

Have now solved half of the problem. My next problem is that " $recipient = $ctx->getsymval('{rcpt_addr}'); " only return the latest recipient. How can I make so it return all receipients? Should I get it in array contect (@receipients) or how do I fetch all recipients? -Ursprungligt medde

Re: 2.11.4: Error in post-install

On Tue, 17 Feb 2015, Viktor Dukhovni wrote: I am guessing that your shell read and split the whole "postfix-files" file in one gulp, rather than split each line. Too many tokens from a single line in that file is implausible. Viktor, I passed on your message to the postfix SlackBuilds maint

Re: Transitioning from cyrus-SASL to dovecot-SASL [DONE]

On Tue, 17 Feb 2015, Viktor Dukhovni wrote: Perhaps you should be asking the dovecot list, not the Postfix list. Viktor, Rather than joining the dovecot mail list I went to their Web site and worked through the configuration documentation step-by-step. After running all their reommended che

Re: How I do to add headers by command?

Sebastian Nielsen: > I have a postfix server. > > On the server, on mail put in outgoing queue (to be relayed), I > want to run the following command: /usr/bin/hashcash -mXb 26 > [recipient01] [recipient02] .. [recipientNN] > > The output of the command (STDOUT) should be put somewhere in the > MI

Re: transport_maps and tcp_table lookup

Marius Gologan: > Hi Wietse, > > This is a test machine. I was trying to capture the query in that /tmp/spawn > file. I get empty lines. > I don't think I get a correct query in 127.0.0.1:. It connects, gets the > echo and closes. It needs to read a query from standard input, and write a repl

Re: SMTP scanning server pool

Daniel Hopkirk - RandomInsanity: > Thanks Wietse, > > I'm still a little confused here. Based on the logs (and what I expect) the > server 202.137.240.16 which is the destination server for this mail has > rejected the recipient with a permanent error. The "user unknown" is logged AFTER the SMTP

How I do to add headers by command?

I have a postfix server. On the server, on mail put in outgoing queue (to be relayed), I want to run the following command: /usr/bin/hashcash -mXb 26 [recipient01] [recipient02] .. [recipientNN] The output of the command (STDOUT) should be put somewhere in the MIME headers. My first idea would

RE: smtpd_recipient_restrictions to restrict outbound email to selected domains

Thanks for the note. Yes. It is for null-client MSAs that use a common smart host, which is defined by: relayhost = [mail.mycompany.com] Thanks, Steve -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Viktor Dukhovni Sent: T

Re: smtpd_recipient_restrictions to restrict outbound email to selected domains

On Tue, Feb 17, 2015 at 07:03:39PM +, Steve Zeng wrote: > Thanks for the hint. The transport map seems do the trick... > > /etc/postfix/main.cf > transport_maps = hash:/etc/postfix/transport > > /etc/postfix/transport > mypartnerorg.com : > mycompany.com : > *

Re: header_checks BCC multiple rules hit

Am 17.02.2015 um 19:29 schrieb Viktor Dukhovni: On Tue, Feb 17, 2015 at 07:14:51PM +0100, li...@rhsoft.net wrote: Am 17.02.2015 um 19:05 schrieb Viktor Dukhovni: On Tue, Feb 17, 2015 at 07:02:27PM +0100, li...@rhsoft.net wrote: (*) The exceptions are REJECT and DISCARD which terminate furthe

RE: transport_maps and tcp_table lookup

I found the problem. The script should listen like "while read line" ... conditions. Thank you. Marius. -Original Message- From: Marius Gologan [mailto:marius.golo...@gmail.com] Sent: Tuesday, February 17, 2015 10:13 PM To: 'Postfix users' Subject: RE: transport_maps and tcp_table looku

RE: transport_maps and tcp_table lookup

Hi Wietse, This is a test machine. I was trying to capture the query in that /tmp/spawn file. I get empty lines. I don't think I get a correct query in 127.0.0.1:. It connects, gets the echo and closes. I will read more about tcp_table lookups since it appears I didn't understand it, probably

Re: SMTP scanning server pool

Thanks Wietse, I'm still a little confused here. Based on the logs (and what I expect) the server 202.137.240.16 which is the destination server for this mail has rejected the recipient with a permanent error. *host 202.137.240.16[202.137.240.16] said: 550 5.1.1 >: Recipient address rejected: Use

RE: smtpd_recipient_restrictions to restrict outbound email to selected domains

Viktor, Thanks for the hint. The transport map seems do the trick... /etc/postfix/main.cf transport_maps = hash:/etc/postfix/transport /etc/postfix/transport mypartnerorg.com : mycompany.com : *error: 5.1.2 recipient domains not allowed Thanks, Steve -Ori

Re: smtpd_recipient_restrictions to restrict outbound email to selected domains

On Tue, Feb 17, 2015 at 06:35:11PM +, Steve Zeng wrote: > > Via SMTP from outside, or via sendmail(1) locally? > > I run mail locally as below: > mail -s "hotmail" myusern...@hotmail.com < /etc/hosts Well, smtpd(8) restrictions don't apply to locally submitted email. I generally configure t

RE: smtpd_recipient_restrictions to restrict outbound email to selected domains

Noticed the non-html version messed up the output of 'postconf -n' to a single line. So I resent it. # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases config_directory = /etc/postfix debug_peer_level = 7 inet_interfaces = localhost mailq_path = /usr/bin/mailq

RE: smtpd_recipient_restrictions to restrict outbound email to selected domains

Thanks, Viktor. > Via SMTP from outside, or via sendmail(1) locally? I run mail locally as below: mail -s "hotmail" myusern...@hotmail.com < /etc/hosts >You'll need to post "postconf -n" output to prove this. Also relevant >master.cf entries in case these contain overrides. # postconf -n smtp

Re: header_checks BCC multiple rules hit

On Tue, Feb 17, 2015 at 07:14:51PM +0100, li...@rhsoft.net wrote: > Am 17.02.2015 um 19:05 schrieb Viktor Dukhovni: > >On Tue, Feb 17, 2015 at 07:02:27PM +0100, li...@rhsoft.net wrote: > > > >>>(*) The exceptions are REJECT and DISCARD which terminate further > >>>table lookups because the decisio

Re: transport_maps and tcp_table lookup

Marius Gologan: > I other words, I would like to query different tcp_tables per > recipient@domain{1..n}.com or > @domain{1..n}.com. Postfix does not query different tables for different domains. This applies to all table types. > 2. I can't get this

Re: header_checks BCC multiple rules hit

Am 17.02.2015 um 19:14 schrieb Wietse Venema: li...@rhsoft.net: Am 17.02.2015 um 18:46 schrieb Wietse Venema: li...@rhsoft.net: is it intentional that if a message hits more than one Regex that it creates also more than once BCC like below? it's little bit surprising Of course. If more tha

Re: header_checks BCC multiple rules hit

Am 17.02.2015 um 19:05 schrieb Viktor Dukhovni: On Tue, Feb 17, 2015 at 07:02:27PM +0100, li...@rhsoft.net wrote: (*) The exceptions are REJECT and DISCARD which terminate further table lookups because the decision is obviously final. and DUNNO NO! That's not a final decision, processing

Re: header_checks BCC multiple rules hit

li...@rhsoft.net: > Am 17.02.2015 um 18:46 schrieb Wietse Venema: > > li...@rhsoft.net: > >> is it intentional that if a message hits more than one Regex that it > >> creates also more than once BCC like below? it's little bit surprising > > > > Of course. If more than one header line matches the t

Re: header_checks BCC multiple rules hit

On Tue, Feb 17, 2015 at 07:02:27PM +0100, li...@rhsoft.net wrote: > >(*) The exceptions are REJECT and DISCARD which terminate further > >table lookups because the decision is obviously final. > > and DUNNO NO! That's not a final decision, processing of more headers continues. > >That is absol

Re: header_checks BCC multiple rules hit

On Tue, Feb 17, 2015 at 06:52:59PM +0100, li...@rhsoft.net wrote: > >>Is it intentional that if a message hits more than one Regex that it creates > >>also more than once BCC like below? it's little bit surprising because in > >>all known cases the first rule hit's and the evaluation of the file i

Re: header_checks BCC multiple rules hit

Am 17.02.2015 um 18:46 schrieb Wietse Venema: li...@rhsoft.net: is it intentional that if a message hits more than one Regex that it creates also more than once BCC like below? it's little bit surprising Of course. If more than one header line matches the table, then more than one action wil

transport_maps and tcp_table lookup

Hi, I'm trying to implement a transport_maps with tcp_table lookup. I know a bit how hash, pcre, regex work, but it seems I'm getting confused about tcp_table. 1. Is there any way I can query recipi...@domain1.com, recipient or domain1.com in the tcp_table in order to have conditiona

Re: header_checks BCC multiple rules hit

Am 17.02.2015 um 17:55 schrieb Viktor Dukhovni: On Tue, Feb 17, 2015 at 05:51:07PM +0100, li...@rhsoft.net wrote: Is it intentional that if a message hits more than one Regex that it creates also more than once BCC like below? it's little bit surprising because in all known cases the first rule

Re: header_checks BCC multiple rules hit

li...@rhsoft.net: > is it intentional that if a message hits more than one Regex that it > creates also more than once BCC like below? it's little bit surprising Of course. If more than one header line matches the table, then more than one action will execute(*). Why is that surprising? (*) Th

Re: header_checks BCC multiple rules hit

On Tue, Feb 17, 2015 at 05:51:07PM +0100, li...@rhsoft.net wrote: > Is it intentional that if a message hits more than one Regex that it creates > also more than once BCC like below? it's little bit surprising because in > all known cases the first rule hit's and the evaluation of the file is > st

header_checks BCC multiple rules hit

is it intentional that if a message hits more than one Regex that it creates also more than once BCC like below? it's little bit surprising because in all known cases the first rule hit's and the evaluation of the file is stopped the intention of the "spamfilter+inbox...@rhsoft.net" is to get

Re: 2.11.4: Error in post-install

On Tue, 17 Feb 2015, Viktor Dukhovni wrote: Before you do, insert debugging code to print the "$path" in question. Something like: Viktor, Thank you; I'll do this. Rich

Re: 2.11.4: Error in post-install

On Tue, Feb 17, 2015 at 08:07:00AM -0800, Rich Shepard wrote: > On Tue, 17 Feb 2015, Viktor Dukhovni wrote: > > >This is a symptom of a deeper problem, possibly a bug in the Bourne > >shell implementation on the system in question. > > Victor, > > Standard linux bash. > > >I am guessing that

Re: 2.11.4: Error in post-install

On Tue, 17 Feb 2015, Viktor Dukhovni wrote: This is a symptom of a deeper problem, possibly a bug in the Bourne shell implementation on the system in question. Victor, Standard linux bash. I am guessing that your shell read and split the whole "postfix-files" file in one gulp, rather than

Re: Transitioning from cyrus-SASL to dovecot-SASL

On Tue, Feb 17, 2015 at 06:43:40AM -0800, Rich Shepard wrote: > I'm not a professional SysAdmin or network admin but have been running my > own smtpd using cyrus-SASL for years. I want now to transition to using > dovecot-SASL and have difficulty correctly configuring dovecot. Perhaps you shoul

Re: Sanity check

On Tue, Feb 17, 2015 at 07:07:04AM -0500, Wietse Venema wrote: > Viktor Dukhovni: > > > submission inet n - n - 30 smtpd > > > -o syslog_name=postfix/submission > > > -o smtpd_tls_wrappermode=no > > > > Postfix 3.0? (smtpd_tls_wrappermode is new with 3.0 IIRC, just

Re: 2.11.4: Error in post-install

On Tue, Feb 17, 2015 at 06:33:08AM -0800, Rich Shepard wrote: > When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding > double quotes to $path fixes this problem. This is a symptom of a deeper pr

Re: Transitioning from cyrus-SASL to dovecot-SASL

Am 17.02.2015 um 15:43 schrieb Rich Shepard: I'm not a professional SysAdmin or network admin but have been running my own smtpd using cyrus-SASL for years. I want now to transition to using dovecot-SASL and have difficulty correctly configuring dovecot. Reading the postfix/dovecot Web p

Transitioning from cyrus-SASL to dovecot-SASL

I'm not a professional SysAdmin or network admin but have been running my own smtpd using cyrus-SASL for years. I want now to transition to using dovecot-SASL and have difficulty correctly configuring dovecot. Reading the postfix/dovecot Web pages and following the links, I created /etc/pam.d

2.11.4: Error in post-install

When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding double quotes to $path fixes this problem. Is this an issue with the source for post-install? I don't see any reference to that file in the S

Re: SMTP scanning server pool

Daniel Hopkirk - RandomInsanity: > Hi Guys, > > Thanks Wietse for your comments, you confirmed what I assumed but couldn't > afford to assume! > > And thanks for your thoughts Bennett. I'm happy to say that the key points > you mentioned are ones we have already given thought as part of our gener

Re: Sanity check

On 2/16/2015 10:29 PM, Viktor Dukhovni wrote: On Mon, Feb 16, 2015 at 09:46:17PM -0500, John Allen wrote: smtp_dns_support_level = dnssec smtp_tls_security_level = dane Givent he above, the following are pointless: smtp_tls_enforce_peername = no A Postfix 2.2 parameter Obsoleted by smt

Re: Sanity check

Viktor Dukhovni: > > submission inet n - n - 30 smtpd > > -o syslog_name=postfix/submission > > -o smtpd_tls_wrappermode=no > > -o smtpd_tls_security_level=encrypt > > -o smtpd_sasl_auth_enable=yes > > -o smtpd_relay_restrictions=permit_sasl_authenticated,reject >

Re: SMTP scanning server pool

Hi Guys, Thanks Wietse for your comments, you confirmed what I assumed but couldn't afford to assume! And thanks for your thoughts Bennett. I'm happy to say that the key points you mentioned are ones we have already given thought as part of our general planning. I've been progressing following y