On Tue, Oct 26, 2021 at 02:01:11PM -0300, SysAdmin EM wrote:
> Hello everyone?
> Has anyone correctly configured kibana to read postfix logs?
>
> I read this documentation, but in kibana 7 not work for me.
> https://github.com/whyscream/postfix-grok-patterns
>
> postfix_queue_id postfix_from
On Tue, Oct 26, 2021 at 08:50:38PM -0400, Viktor Dukhovni
wrote:
> On Tue, Oct 26, 2021 at 08:41:20PM -0400, Viktor Dukhovni wrote:
>
> > With `bash` inline /dev/fd/ files:
> >
> > $ diff -U0 <(postconf -x -o compatibility_level=2) <(postconf -x -o
> > compatibility_level=3.6)
>
> A
On Tue, Oct 26, 2021 at 08:41:20PM -0400, Viktor Dukhovni wrote:
> With `bash` inline /dev/fd/ files:
>
> $ diff -U0 <(postconf -x -o compatibility_level=2) <(postconf -x -o
> compatibility_level=3.6)
A handly abstraction to a couple function definitions would be:
compatconf() {
On Wed, Oct 27, 2021 at 11:34:57AM +1100, raf wrote:
> > Is there a way, given a new warning about compatibility_level (say
> > you've been running with 3_5, and you're now running 3_6), to see
> > what changes to your config are effectively made by enabling that
> > level? (effectively, to show
On Tue, Oct 26, 2021 at 05:08:00PM -0700, Dan Mahoney
wrote:
>
>
> > On Oct 26, 2021, at 4:54 PM, raf wrote:
> >
> > On Tue, Oct 26, 2021 at 09:42:33AM -0400, Wietse Venema
> > wrote:
> >
> >> Vincent Pelletier:
> >>> On Mon, 25 Oct 2021 12:36:35 -0400 (EDT),
> >>> Wietse Venema wrote :
> On Oct 26, 2021, at 4:54 PM, raf wrote:
>
> On Tue, Oct 26, 2021 at 09:42:33AM -0400, Wietse Venema
> wrote:
>
>> Vincent Pelletier:
>>> On Mon, 25 Oct 2021 12:36:35 -0400 (EDT),
>>> Wietse Venema wrote :
This would require a new setting, for example to make smtp_bind_address
On Tue, Oct 26, 2021 at 09:42:33AM -0400, Wietse Venema
wrote:
> Vincent Pelletier:
> > On Mon, 25 Oct 2021 12:36:35 -0400 (EDT),
> > Wietse Venema wrote :
> > > This would require a new setting, for example to make smtp_bind_address
> > > failures a retryable error.
> > >
> > >
On Tue, Oct 26, 2021 at 09:05:46PM +, Cooper, Robert A wrote:
> Posftinger output:
> https://gist.github.com/racooper/a560c84080e2ee6c336d508918344f5a
Please avoid paste bins in the future. Also where are the (couple of)
requested log entries that show the problem behaviour?
(sorry for top-posting. OWA is evil in that way.)
Posftinger output:
https://gist.github.com/racooper/a560c84080e2ee6c336d508918344f5a
Contents of error_transport (the only defined transport_map):
fxgfd.com error:undeliverable
yahoo.es.comerror:undeliverable
site.co
On Tue, Oct 26, 2021 at 04:22:53PM +, Cooper, Robert A wrote:
> Howdy! We have noticed that certain email going through our outbound
> relay are ignoring the "relayhost = [smtp-relay.site.com]:25".
Sorry, that's not possible. The delivery of messages for *all*
recipients uses the same
Hello everyone?
Has anyone correctly configured kibana to read postfix logs?
I read this documentation, but in kibana 7 not work for me.
https://github.com/whyscream/postfix-grok-patterns
postfix_queue_id postfix_from postfix_to postfix_date
The idea is to have a dashboard with the mails sent
post...@ptld.com:
> >> It does not complicate the code. I am more concerned about
> >> discoverability (how would a user even find out that the behavior
> >> has become configurable).
> >
> > The best we can do is cross-reference the new parameter under
> > smtp_bind_address (and IPv6
Howdy! We have noticed that certain email going through our outbound relay are
ignoring the "relayhost = [smtp-relay.site.com]:25". The condition seems to be
when a message has an envelope rewrite based on LDAP lookup (specifically, from
site.com to email.site.com, which goes to gmail).
It does not complicate the code. I am more concerned about
discoverability (how would a user even find out that the behavior
has become configurable).
The best we can do is cross-reference the new parameter under
smtp_bind_address (and IPv6 equivalent), and then sufficiently
motivated
users
On Tue, Oct 26, 2021 at 09:42:33AM -0400, Wietse Venema wrote:
> It does not complicate the code. I am more concerned about
> discoverability (how would a user even find out that the behavior
> has become configurable).
The best we can do is cross-reference the new parameter under
Vincent Pelletier:
> On Mon, 25 Oct 2021 12:36:35 -0400 (EDT),
> Wietse Venema wrote :
> > This would require a new setting, for example to make smtp_bind_address
> > failures a retryable error.
> >
> > smtp_bind_address_failure_action = warn (or defer)
> >
> > warn: current behavior
> > defer:
16 matches
Mail list logo