Re: What's new in log file parsers? Anything better than pflogsumm?

> On Mar 25, 2019, at 1:13 PM, Jim Rice wrote: > > I'm looking for a postfix log file parser that can provide the number of > messages delivered, > broken down by sending domain, and per hour counts on a daily basis. Make sure you have a clear definition of "messages delivered"? Is it messages

What's new in log file parsers? Anything better than pflogsumm?

I'm looking for a postfix log file parser that can provide the number of messages delivered, broken down by sending domain, and per hour counts on a daily basis. I have looked at pflogsumm, but it seems a bit dated, and isn't as flexible as I had hoped. Can someone suggest any alternatives?

Re: Relay Access Denied

> > On Mar 25, 2019, at 11:28 AM, Viktor Dukhovni > wrote: > > As for why "mynetworks" is not enough, perhaps time to look > at your master.cf file... Fixed. I needed a “From” header for gmail to accept it. That was inside the Ruby gem configuration. Cheers _ Rich in

Re: pishing from ME

Before you freak out about whether or not your passwords were leaked please understand that this is might be a complete hoax that takes advantage of the fact that e-mail is just a string of text passed from server to server. Using telnet you can forge the From: field in an e-mail message provided

Re: Relay Access Denied

> On Mar 25, 2019, at 11:28 AM, Viktor Dukhovni > wrote: > > As for why "mynetworks" is not enough, perhaps time to look > at your master.cf file... Here it is: # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command:

Re: Relay Access Denied

> On Mar 25, 2019, at 7:23 AM, VP Lists wrote: > >>> smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated >>> permit >> >> This is rather pointless. Delete it, it serves no purpose. >>> smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks >>> reject

Re: Relay Access Denied

On Mon, 25 Mar 2019, VP Lists wrote: On Mar 25, 2019, at 1:37 AM, Viktor Dukhovni wrote: This must be some Apple-specific Postfix setting, are you running Apple's Postfix binaries? mail_version = 2.9.2 smtpd_relay_restrictions appeared only with 2.10. That explains the "unused parameter"

Re: $queue_directory/private permissions

On 2019-03-25 1:32 a.m., Viktor Dukhovni wrote: >> On Mar 24, 2019, at 8:17 PM, Simon Deziel wrote: >> >> I was not clear because my issue is indeed with those accesses before >> privs get dropped. I noticed that tlsproxy accesses tlsmgr's socket >> while still running as root so it depends on

Re: Relay Access Denied

> On Mar 25, 2019, at 1:37 AM, Viktor Dukhovni > wrote: > >> >> # /var/log/mail.log: >> Mar 24 18:37:35 alpha.mydomain.com postfix/postscreen[11964]: CONNECT from >> [192.168.1.4]:52147 to [192.168.1.6]:25 >> Mar 24 18:37:35 alpha.mydomain.com postfix/postscreen[11964]: PASS OLD >>

Re: Relay Access Denied

> On Mar 25, 2019, at 1:37 AM, Viktor Dukhovni > wrote: > > This must be some Apple-specific Postfix setting, are you running Apple's > Postfix binaries? mail_version = 2.9.2 _ Rich in Toronto @ VP

Re: $queue_directory/private permissions

Bastian Blank: > On Mon, Mar 25, 2019 at 01:32:28AM -0400, Viktor Dukhovni wrote: > > Sorry, that breaks the Postfix internal access control model in unsupported > > ways. Root needs to be able to read the directory with its standard > > permissions. > > How exactly does "root" get permissions

Re: $queue_directory/private permissions

On Mon, Mar 25, 2019 at 01:32:28AM -0400, Viktor Dukhovni wrote: > Sorry, that breaks the Postfix internal access control model in unsupported > ways. Root needs to be able to read the directory with its standard > permissions. How exactly does "root" get permissions to read the directory? It's