Hi,
I have a set of grok patterns for logstash. You can send the postfix
logs to logstash, have them parsed into something more or less
structured by the pattersn, then expose the logstash data through some api.
https://github.com/whyscream/postfix-grok-patterns/
Kind regards,
Tom
On 0
* Илья Шипицин :
> > Here is an idea: combine log analysis with a web API. End of problem.
>
> that was what I was going to implement.
> however, I do not like to implement thing that are implemented already.
> so, I did a google search and I asked mailing list.
>
> seems, I need to implement res
пн, 1 окт. 2018 г. в 12:30, Tom Hendrikx :
> Hi,
>
> I have a set of grok patterns for logstash. You can send the postfix
> logs to logstash, have them parsed into something more or less
> structured by the pattersn, then expose the logstash data through some api.
>
> https://github.com/whyscream/
I’ve just tired to install Postfix 3.3.1 on macOS X 10.13.6 High Sierra.
Sudo make install finishes with:
Updating /usr/sbin/sendmail...
mv: rename /Users/jlbrown/Downloads/postfix-3.3.1/junk to /usr/sbin/sendmail:
Operation not permitted
make: *** [install] Error 1
My make command was:
make -
On Mon, Oct 01, 2018 at 05:56:57PM +1000, James Brown wrote:
> I’ve just tired to install Postfix 3.3.1 on macOS X 10.13.6 High Sierra.
>
> Sudo make install finishes with:
>
> Updating /usr/sbin/sendmail...
In MacOSX /usr is immutable, except during upgrade reboots. You
can't install Postfix
Hi
Looking for some hints on a performance problem i have with postfix and looping
mail through a content filter and it slowly feedback back out via the maildrop.
It would seem that pickup process is trickle feeding the maildrop back into the
active queue. I conscious that pickup is single th
I have implemented such policy server: it lookups MTA-STS policy, caches and
updates it as RFC 8461 defines.
Github: https://github.com/Snawoot/postfix-mta-sts-resolver
PyPI: https://pypi.org/project/postfix-mta-sts-resolver/
Daemon lacks some features required by standard like proactive policy f
Hello,
we have pretty complicated setup. when we change something, we can break
something else.
however, we can describe "what must work".
is there a way of describing configuration testing like
https://openresty.gitbooks.io/programming-openresty/content/testing/test-nginx.html
?
cheers,
Ilya Sh
Human guru perhaps not, but programs , spammers, or others may.
So how to reject mail with bad sender addresses that postfix accept.
Any help is welcome.
-
Thank you for helping
Opensuse Leap 15
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
jcdole:
> Human guru perhaps not, but programs , spammers, or others may.
>
> So how to reject mail with bad sender addresses that postfix accept.
>
> Any help is welcome.
Use check_sender_access with PCRE patterns, to retrict the subset
of address syntax that you want to allow.
http://www.post
On 01.10.18 12:48, jcdole wrote:
> So how to reject mail with bad sender addresses that postfix accept.
A PCRE-based access restriction "/[@!%].*[@!%]/ REJECT" should do it
(untested).
-Ralph
Hello!,
I'm can't see references about SNI in 3.4 release notes, this feature has
been discarded for next release or is WIP?
Thks!
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
vrubiella:
> Hello!,
>
> I'm can't see references about SNI in 3.4 release notes, this feature has
> been discarded for next release or is WIP?
It's in progress. We don't announce things until they exist.
Wietse
Hello,
Running Postfix 2.10.1.
I am setting up an internal mail relay to receive mail from other
internal clients. I have a requirement that all email be received via
TLS only.
I have configured TLS using our internal PKI and set the appropriate
settings in main.cf and mail is being receiv
Dear Postfix folks,
On 02/19/18 20:11, Wietse Venema wrote:
> Jonathan Sélea:
[...]. One can of course automate periodic SMTP TLS policy
updates from the STS URIs of a handful of providers, and let the
usual outbound TLS policy take care of the rest:
http://www.postfi
yarmak:
> I have implemented such policy server: it lookups MTA-STS policy, caches and
> updates it as RFC 8461 defines.
>
> Github: https://github.com/Snawoot/postfix-mta-sts-resolver
> PyPI: https://pypi.org/project/postfix-mta-sts-resolver/
>
> Daemon lacks some features required by standard l
Paul Menzel:
> Dear Postfix folks,
>
>
> On 02/19/18 20:11, Wietse Venema wrote:
> > Jonathan S?lea:
> [...]. One can of course automate periodic SMTP TLS policy
> updates from the STS URIs of a handful of providers, and let the
> usual outbound TLS policy take care of the rest:
>
Virtual Xmas:
> Hello,
>
> Running Postfix 2.10.1.
>
> I am setting up an internal mail relay to receive mail from other
> internal clients.? I have a requirement that all email be received via
> TLS only.
>
> I have configured TLS using our internal PKI and set the appropriate
> settings in
> On Oct 1, 2018, at 3:13 AM, Viktor Dukhovni
> wrote:
>
> On Mon, Oct 01, 2018 at 05:56:57PM +1000, James Brown wrote:
>
>> I’ve just tired to install Postfix 3.3.1 on macOS X 10.13.6 High Sierra.
>>
>> Sudo make install finishes with:
>>
>> Updating /usr/sbin/sendmail...
>
> In MacOSX /usr
That does not work with the data I have use to make a test.
This is the reason I open a thread.
email-address :: local-p...@example.com
but if local-part :: local-p...@example.com ==>
local-p...@example.com@example.com
Now the lookup table
local-p...@example.comOK
*postmap -q "local-p...@ex
On 1 Oct 2018, at 3:56, James Brown wrote:
Is this a SIP thing?
Yes. As Viktor said, Apple-populated paths under /usr are immutable
while SIP is enabled.
Anyone come across this? How to fix?
Don't fight it. As Viktor said, you can adjust your build to NOT replace
the system 'sendmail' (
On 01.10.18 10:21, Virtual Xmas wrote:
Running Postfix 2.10.1.
I am setting up an internal mail relay to receive mail from other
internal clients. I have a requirement that all email be received via
TLS only.
I have configured TLS using our internal PKI and set the appropriate
settings in
???:
> Hello,
>
> we have pretty complicated setup. when we change something, we can break
> something else. however, we can describe "what must work".
In the case of email, this is usually tested by sending email and
monitoring one or more destination mailboxes, to determine if the
mes
23 matches
Mail list logo
