Re: monitoring outgoing emails

2018-04-04 Thread Viktor Dukhovni
> On Apr 5, 2018, at 1:39 AM, Scott Kitterman wrote: > > On Thursday, April 05, 2018 07:34:44 AM Poliman - Serwis wrote: >> Unfortunately I use Postfix from Ubuntu repos. > > apt-get source postfix > cd postfix-[version] (depends your Ubuntu release) > cd

Re: Keep Postfix running in the foreground

2018-04-04 Thread Bastian Blank
On Wed, Apr 04, 2018 at 08:56:46PM -0400, Wietse Venema wrote: > That may be so, but why does the lame Linux kernel silently ignore > the kill() call instead of properly returning an error. The signal is ignored the same way as if someone had called | signal(SIGFOO, SIG_IGN) Bastian -- You!

Re: monitoring outgoing emails

2018-04-04 Thread Scott Kitterman
On Thursday, April 05, 2018 07:34:44 AM Poliman - Serwis wrote: > Unfortunately I use Postfix from Ubuntu repos. apt-get source postfix cd postfix-[version] (depends your Ubuntu release) cd auxiliary/collate ls and you'll see both collate.pl and the associated README. Scott K > 2018-04-04

Re: monitoring outgoing emails

2018-04-04 Thread Poliman - Serwis
Unfortunately I use Postfix from Ubuntu repos. 2018-04-04 13:08 GMT+02:00 Wietse Venema : > Poliman - Serwis: > > Could you tell me I could add e-mails together from mail.log which are in > > line with "from=" part? Hmm I hope I say clear. I need count emails from > >

Re: monitoring outgoing emails

2018-04-04 Thread Poliman - Serwis
I am not sure I understood well. There are three "from=", and you said which one repond to which behavior, so I think I could base on "from=" from log file but I should divide by three number of emails send by specific user. Am I right? 2018-04-04 11:11 GMT+02:00 chaouche yacine

Re: Removing trace records on submission MSA

2018-04-04 Thread Philip Paeps
On 2018-04-05 08:54:45 (+0800), J Doe wrote: Hi Phillip, I have a question in regards to removing some trace records when providing submission on Postfix 3.1.x and later. While reading RFC 6409 (“Message Submission for Mail”), I note that the RFC observes that: "Even when submitted

Re: Keep Postfix running in the foreground

2018-04-04 Thread HAKNER J
>That may be so, but why does the lame Linux kernel silently ignore >the kill() call instead of properly returning an error. > > Wietse :) I don't write the code, just reporting the bad news! I think however the reasoning is as follows: clearly a user-mode process can send a signal to

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
HAKNER J: > > > > >>> I'd appreciate it if someone could verify that this will run the > > > > >>> master daemon with PID 1, and that 'postfix stop' in the container > > > > >>> will stop the master daemon. If it doesn't, then Linux does weird > > > > >>> stuff with PID 1 processes. > > Correct.

Re: Removing trace records on submission MSA

2018-04-04 Thread J Doe
Hi Phillip, >> I have a question in regards to removing some trace records when providing >> submission on Postfix 3.1.x and later. >> >> While reading RFC 6409 (“Message Submission for Mail”), I note that the RFC >> observes that: >> >> "Even when submitted messages are complete, local

Re: Keep Postfix running in the foreground

2018-04-04 Thread HAKNER J
> > > >>> I'd appreciate it if someone could verify that this will run the > > > >>> master daemon with PID 1, and that 'postfix stop' in the container > > > >>> will stop the master daemon. If it doesn't, then Linux does weird > > > >>> stuff with PID 1 processes. Correct. The Linux kernel

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
that fixes the PID=1 behavior? > > > > > > it does in any way. Thanks, Wietse! > > > > > > I tried both, exit(0) and _exit(0) :-) > > > > Andreas, thanks for the encouraging words :-) > > I also need you guys to verify that with the Postfix master running > as PID=1, "docker stop" will no longer leave the master daemon > running until Docker times out and forcibly terminates everything. > > By default, "docker stop" should send signal SIGTERM (signal 15) which > is what Postfix expects, but it is good to verify. BTW postfix-3.4-20180404 has the _exit() call. Wietse

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
Wietse Venema: > A. Schulze: > > Am 04.04.2018 um 19:08 schrieb Wietse Venema: > > > Eray Aslan: > > >> On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote: > > >>> I updated both the postfix-script file and the master daemon. > > >>> > > >>> I'd appreciate it if someone could verify

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
A. Schulze: > Am 04.04.2018 um 19:08 schrieb Wietse Venema: > > Eray Aslan: > >> On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote: > >>> I updated both the postfix-script file and the master daemon. > >>> > >>> I'd appreciate it if someone could verify that this will run the > >>>

Re: Keep Postfix running in the foreground

2018-04-04 Thread A. Schulze
Am 04.04.2018 um 19:08 schrieb Wietse Venema: > Eray Aslan: >> On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote: >>> I updated both the postfix-script file and the master daemon. >>> >>> I'd appreciate it if someone could verify that this will run the >>> master daemon with PID 1,

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
Viktor Dukhovni: > > > > On Apr 4, 2018, at 1:31 PM, Wietse Venema wrote: > > > > According to RTFM, the exit() function does not return so it can't 'fail'. > > > > FreeBSD: > > The exit() and _Exit() functions never return. > > The _exit() system call can never

Re: Keep Postfix running in the foreground

2018-04-04 Thread Viktor Dukhovni
> On Apr 4, 2018, at 1:31 PM, Wietse Venema wrote: > > According to RTFM, the exit() function does not return so it can't 'fail'. > > FreeBSD: > The exit() and _Exit() functions never return. > The _exit() system call can never return. > Linux: > The exit()

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
Wietse Venema: > Just for the heck of it, can you replace in src/master/master_sig.c > this code: > >if (kill(pid, SIGKILL) < 0) >msg_fatal("%s: kill myself: %m", myname); > > With this code: > >exit(0); > > And see if that fixes the PID=1 behavior? Viktor Dukhovni: > Perhaps

Re: Keep Postfix running in the foreground

2018-04-04 Thread Viktor Dukhovni
> On Apr 4, 2018, at 1:08 PM, Wietse Venema wrote: > > Just for the heck of it, can you replace in src/master/master_sig.c > this code: > >if (kill(pid, SIGKILL) < 0) >msg_fatal("%s: kill myself: %m", myname); > > With this code: > >exit(0); > > And

Re: Keep Postfix running in the foreground

2018-04-04 Thread Wietse Venema
Eray Aslan: > On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote: > > I updated both the postfix-script file and the master daemon. > > > > I'd appreciate it if someone could verify that this will run the > > master daemon with PID 1, and that 'postfix stop' in the container > > will

Re: Keep Postfix running in the foreground

2018-04-04 Thread Eray Aslan
On Tue, Apr 03, 2018 at 07:46:42PM -0400, Wietse Venema wrote: > I updated both the postfix-script file and the master daemon. > > I'd appreciate it if someone could verify that this will run the > master daemon with PID 1, and that 'postfix stop' in the container > will stop the master daemon.

Re: Use of separate storage for mailboxes

2018-04-04 Thread SAAHIL IFTEKHAR
Hi Initially I was able to deliver through the second option (the storage has some server running) through lmtp and port 24. But now the requirement is like the option one( using NFS, iSCSI,etc). Two queries regarding this first option:- 1) Its not like delivering to a different location, I

Re: Use of separate storage for mailboxes

2018-04-04 Thread Wietse Venema
SAAHIL IFTEKHAR: > Hi > > You mean we are actually sharing mailboxes to a separate storage? And > still mails are delivered in the same node(ip address) where postfix > is running? > > I am trying to find a way through which the mails can be delivered to > this separate storage. This storage is

Re: Use of separate storage for mailboxes

2018-04-04 Thread Matus UHLAR - fantomas
On 04.04.18 18:28, SAAHIL IFTEKHAR wrote: You mean we are actually sharing mailboxes to a separate storage? And still mails are delivered in the same node(ip address) where postfix is running? I am trying to find a way through which the mails can be delivered to this separate storage. This

Re: Use of separate storage for mailboxes

2018-04-04 Thread SAAHIL IFTEKHAR
Hi You mean we are actually sharing mailboxes to a separate storage? And still mails are delivered in the same node(ip address) where postfix is running? I am trying to find a way through which the mails can be delivered to this separate storage. This storage is like simply a remote storage not

Re: monitoring outgoing emails

2018-04-04 Thread Wietse Venema
Poliman - Serwis: > Could you tell me I could add e-mails together from mail.log which are in > line with "from=" part? Hmm I hope I say clear. I need count emails from > particular mailbox. Can I base on "from="? For example: > Apr 3 11:49:48 s1 postfix/qmgr[722]: 3B8C313BE2D:

Re: domain email autoconfiguration

2018-04-04 Thread Alex JOST
Am 04.04.2018 um 02:08 schrieb David Mehler: Hello, What I'm wanting to do is configure clients to get their account information automatically. I know this for Mozilla is called autoconfig and for Microsoft it's autodiscover, and apparently there's an srv record I just read about. If anyone

Re: monitoring outgoing emails

2018-04-04 Thread chaouche yacine
The log line from avmavis already has the sender a single time, regardless of the number of recipients. Also, if you grep on from, keep in mind that the email first goes from outside to postfix (1st from), the from postfix to amavis (second from), then from amavis back to postfix (third from).

Re: Keep Postfix running in the foreground

2018-04-04 Thread Ralph Seichter
On 03.04.2018 02:37, John Stoffel wrote: > But... isn't discourse running in it's own container, so you'd be > spinning up postfix it another container... John Allen asked "what is the attraction of docker", and I was just mucking about with a new Discourse installation, so I mentioned this as

Re: monitoring outgoing emails

2018-04-04 Thread Poliman - Serwis
Or maybe I could base on this value but divided by 3. 2018-04-04 9:43 GMT+02:00 Poliman - Serwis : > Hmm, probably I can't base on this, because when I send one email I have > in log three lines with "from=" and value . > 1st line --> Apr 4 09:32:41 s1

Re: monitoring outgoing emails

2018-04-04 Thread Poliman - Serwis
Hmm, probably I can't base on this, because when I send one email I have in log three lines with "from=" and value . 1st line --> Apr 4 09:32:41 s1 postfix/submission/smtpd[5622]: NOQUEUE: filter: RCPT from host-X.Y.Z.W.static.com[X.Y.Z.W]: < t...@example.com >: Sender address

Re: Keep Postfix running in the foreground

2018-04-04 Thread A. Schulze
Wietse Venema: I'd appreciate it if someone could verify that this will run the master daemon with PID 1, and that 'postfix stop' in the container will stop the master daemon. I'll verify that in the next days ... Andreas

Re: domain email autoconfiguration

2018-04-04 Thread Viktor Dukhovni
> On Apr 4, 2018, at 2:06 AM, David Mehler wrote: > > Do you use autoconfig/autodiscover? My users configure their MUAs statically. I am familiar with RFC6186 by way of looking at its security model when working on DANE-related RFCs. -- Viktor.

Re: domain email autoconfiguration

2018-04-04 Thread David Mehler
Hello Victor, Do you use autoconfig/autodiscover? Thanks. Dave. On 4/3/18, Viktor Dukhovni wrote: > > >> On Apr 3, 2018, at 8:08 PM, David Mehler wrote: >> >> What I'm wanting to do is configure clients to get their account >> information