Re: Starting postfix at boot time on Centos 7

2016-02-26 Thread Peter
On 25/02/16 06:25, i...@itrezero.it wrote: > I compiled postfix 3.0.3 from source code but (maybe a stupid question)… > don’t know how to start it at boot of a Centos 7 machine! > > Tried with “chkconfig” and “systemctl” without any results! > > How can I do this? Is there a “postfix.service” to

Re: Mail bagging

2016-02-26 Thread Glen Eustace
> > You can prepend a recipient header with an smtpd access rule: > > /etc/postfix/main.cf: >smtpd_recipient_restrictions = > check recipient_access prce:/etc/postfix/prepend-rcpt.pcre > ...other rules... > > /etc/postfix/prepend-rcpt.pcre: >/(.+)/ prepend X-Rcpt-To: $1 Thi

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Noel Jones
On 2/26/2016 1:25 PM, Saskia van Schagen wrote: > ... > > Is it perhaps my name and the fact that it shows that I am a woman. I didn't know you were a woman until you pointed it out. Everyone is welcome here. > Postfix is not connecting multiple times at the same time. I suggest you experiment

Re: Mail bagging

2016-02-26 Thread Glen Eustace
> On 27/02/2016, at 9:13 AM, Wietse Venema wrote: > > This is why Postfix by default adds an X-Original-To: header with > the original recipient up on mailbox delivery. This is with > "enable_original_recipient = yes”. I haven’t tried this yet, but it would appear this is the actual mailbag’s

Re: Mail bagging

2016-02-26 Thread Wietse Venema
Glen Eustace: > One of our customers has complained that our mail system is broken. We have > been using postfix for many years and have come across the behaviour the > complaint is about a number of times but haven?t spent a lot of time or > energy trying to solve it. I would like to try to d

Mail bagging

2016-02-26 Thread Glen Eustace
One of our customers has complained that our mail system is broken. We have been using postfix for many years and have come across the behaviour the complaint is about a number of times but haven’t spent a lot of time or energy trying to solve it. I would like to try to do so now. The issue i

THREAD CLOSED (no concurrent connections)

2016-02-26 Thread Wietse Venema
OK, you just hit the troll threshold (should probably have triggered this long ago, we don;t see that here often). I am closing this thread. Tresspassers will be punished. Wietse Saskia van Schagen: > Telnet sessions work as expected. I can connect multiple times with telnet > and since

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Wolfe, Robert
So are you saying that your postfix setup will only accept one connection at a time vs. more than one connection at once? -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Saskia van Schagen Sent: Friday, February 26, 2016 1:35 P

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Wietse Venema
Saskia van Schagen: > ... > > Is it perhaps my name and the fact that it shows that I am a woman. Please don't do that. We are grown-up people who can handle that. It's your message, not the messenger that is at issue Wietse

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
Telnet sessions work as expected. I can connect multiple times with telnet and since I have put a 20 second sleep in the worker threads, I don't even have to be fast. I connect, I get accepted, I connect with another window, get accepted. I print "bla", the window of the server sais : received bla

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
... Is it perhaps my name and the fact that it shows that I am a woman. My policy daemon runs just fine. It handles multiple requests at the same time. For some reason it is impossible for me to explain that the problem is that Postfix is not connecting multiple times at the same time. I think I h

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Wietse Venema
Saskia van Schagen: > 7. While the worker thread is still working and the main thread is blocking > on accept(), I'm sending another e-mail. > 8. The main thread is still blocking on accept(), there is no new client > connection. That is a bug in your server. It should accept the connection as so

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Noel Jones
On 2/26/2016 12:09 PM, Saskia van Schagen wrote: > If two smtpd processes would talk over the same connection at the same time, > we may receive something like this: No, that's where you go very wrong. Each smtpd process has its own connection and there is no crosstalk. This is similar to how yo

mail relay with local alias handling, but no local delivery

2016-02-26 Thread J.T. Conklin
The division of the company I work for was once a separate company that was acquired a couple of years ago. Since then, we've run the old mail system in parallel with the new. But now we're looking to deprecate the old email infrastructure (a handful of exchange servers) with a postfix mail relay.

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
First of all, thanks for your help. But this is just the problem. I have written many server / client models, so perhaps I can explain the problem better like this: 1. Server listens on 127.0.0.1 on port . 2. I send a test email. 3. Postfix connects and I "accept" a client socket side. 4. The

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Wietse Venema
Saskia van Schagen: > Victor, thanks for trying to help out. But still this cannot be true. In > Postfix I cannot setup a different socket for each smtpd process, if I had > 100 smtpd processes, I cannot tell Postfix that each of these 100 processes > should connect with a different client socket.

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
I just made some changes: // Just as an example smtpd_policy_service_request_limit = 5 In the policy server: bytes = recv( sock_c, buff, MAXBUF, 0 ); printf( "1 Received %d bytes...\n", bytes ); bytes = recv( sock_c, buff, MAXBUF, 0 ); printf( "2 Received %d bytes...\n", bytes ); Just for the h

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
Victor, thanks for trying to help out. But still this cannot be true. In Postfix I cannot setup a different socket for each smtpd process, if I had 100 smtpd processes, I cannot tell Postfix that each of these 100 processes should connect with a different client socket. So we have one socket here,

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Noel Jones
On 2/26/2016 11:13 AM, Saskia van Schagen wrote: > Not quite true, one can set smtpd_policy_service_request_limit to 1 and have > a new connection for each request. Yes, you can force a new connection for each request, which will reduce performance considerably. This should only be used if the po

Re: alias_maps delivery rights?

2016-02-26 Thread Wietse Venema
Jack Bates: > On 25/02/16 08:20 AM, Ralf Hildebrandt wrote: > > * Ralf Hildebrandt : > >> * Jack Bates : > >>> LOCAL(8) DELIVERY RIGHTS says: "Deliveries to external files and > >>> external commands are made with the rights of the receiving user on > >>> whose behalf the delivery is made." > >>> >

RE: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Saskia van Schagen
Not quite true, one can set smtpd_policy_service_request_limit to 1 and have a new connection for each request. But even if you don't and you keep using the same connection, Postfix is still not giving the next request before receiving the answer of the previous request. This is not strange, if you

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread Noel Jones
On 2/26/2016 10:31 AM, saskia101 wrote: > I guess there's still a problem... At least messages are now send faster than > 1 per second through the policy daemon, but still Postfix is not treating > the policy daemon as multi threaded. > > Postfix seems to wait until he got is "action=" answer, bef

Re: alias_maps delivery rights?

2016-02-26 Thread Viktor Dukhovni
On Fri, Feb 26, 2016 at 08:16:43AM -0800, Jack Bates wrote: > Hmmm ... That is what's happening, but why's there no user context? > I expected the first case ("the rights of the receiving user on whose > behalf the delivery is made") vs. the second ("the absence of a user > context"). Entries in

Re: Postfix & check_policyd_service no concurrent connections?

2016-02-26 Thread saskia101
I guess there's still a problem... At least messages are now send faster than 1 per second through the policy daemon, but still Postfix is not treating the policy daemon as multi threaded. Postfix seems to wait until he got is "action=" answer, before sending a new request. Even if I send back the

Re: alias_maps delivery rights?

2016-02-26 Thread Jack Bates
On 25/02/16 08:20 AM, Ralf Hildebrandt wrote: * Ralf Hildebrandt : * Jack Bates : LOCAL(8) DELIVERY RIGHTS says: "Deliveries to external files and external commands are made with the rights of the receiving user on whose behalf the delivery is made." So I put "nottheoilrig: /mnt/nottheoilrig/"