If /dev/log would not be hardcoded in syslog.h it would be possible to
make the socket configurable in postfix and output directly to the
rsyslog process.
:-(
On 2017-01-23 15:04, wie...@porcupine.org wrote:
And the logging daemon uses more CPU than Postfix. We're back 20 years
ago.
--
Hi,
on most linux distributions /dev/log is owned by systemd-journald these
days.
Check if your logs reach the journal:
journalctl -u postfix
If thats the case, check if rsyslog reads logs from journald:
$ModLoad imjournal
Markus
On 2017-01-22 16:41, Bartłomiej Solarz-Niesłuchowski
On 2016-12-02 15:10, Michael Munger wrote:
This is a great idea. This is a spam filter that is integrated into a
CRM system, so I needed to parse and dump the information so it could
be
sucked up later.
Here's what I ultimately created. It still needs some work (mainly
because it re-reads the
On 2016-08-17 17:34, Zhang Huangbin wrote:
I got a problem with my own Postfix policy server (written in Python).
Postfix usually works fine with it, but sometimes it raised error like
this:
Aug 17 08:32:52 mail1 postfix/smtpd[24298]: warning: problem talking
to server 127.0.0.1:1234:
On 2016-07-09 18:34, Robert Schetterer wrote:
additional fail2ban, but log parse was to slow at my side
and for sure use postscreen
Its possible to trigger fail2ban from a policyd:
https://www.mtpolicyd.org/documentation.html#Mail::MtPolicyd::Plugin::Fail2Ban
Markus
--
On 2016-06-28 07:46, Zhang Huangbin wrote:
I have a simple Postfix policy server, and got a problem to reject
sender login mismatch (sender != sasl_username) with Outlook 2016:
user is able to specify a From: address, it would be any address you
want, and the From: address is not passed to
On 2016-06-14 02:28, list...@tutanota.com wrote:
I am considering the installation of Greylisting with Postfix.
I want it only for one condition, to greylist mail originating from
certain countries.
Hi,
may be mtpolicyd is an option for you:
https://www.mtpolicyd.org
It is a modular
On 2016-04-06 16:19, Benning, Markus wrote:
In sasl.h:
#define SASL_FAIL -1 /* generic failure */
Could this one be added to the AUTH_TEMP case?
I took a look at the cyrus-sasl code in lib/checkpw.c and most error
cases there
return SASL_FAIL.
Wrong credentails return SASL_BADAUTH
On 2016-04-06 16:19, Benning, Markus wrote:
In sasl.h:
#define SASL_FAIL -1 /* generic failure */
Could this one be added to the AUTH_TEMP case?
Could it be that the libsasl uses SASL_FAIL also in case of a wrong
password?
In this case i think it would be an error in libsasl
Hi,
when i use a cyrus saslauthd:
pwcheck_method: saslauthd
mech_list: plain login
saslauthd_path: /var/run/kokolores/mux
And the saslauthd is not running.
Then the socket /var/run/kokolores/mux does not exist and postfix
returns
535 5.7.8 Error: authentication failed: generic failure
On 2016-03-24 15:31, Benning, Markus wrote:
i'm currently searching for a way to implement SASL authentication with
postfix
and a secure password mechanism like bcrypt.
Here comes kokolores:
https://github.com/benningm/kokolores
An alternative saslauthd with plugin support.
--
https
Hello postfix users,
i'm currently searching for a way to implement SASL authentication with
postfix
and a secure password mechanism like bcrypt.
sasldb -> plain text
sql -> requires plain text passwords
ldapdb -> requires a ldap server (could use whatever the ldap server
implements)
On 2016-03-03 08:12, Eero Volotinen wrote:
Can some one give working migation intructions for postfix 2.3
(postfix-2.3.3-7.el5) many of instructions are not working correctly
on so old version. (as settings are not supported)
Just install the RHSA errata:
On 2015-11-10 23:42, Donald Bindner wrote:
smtpd_recipient_restrictions = check_policy_service
inet:127.0.0.1:10040
You may want to use a different restriction than recipient.
The recipient restrictions are executed for every recipient.
It gets executed multiple times if the mail has more than
I'm also using a policy daemon to build a score based on Whitelists,
SPF, RBLs, GeoIP, etc.
And then apply greylisting, rejects based on the score.
(as in mtpolicyd example configuration:
https://github.com/benningm/mtpolicyd/blob/master/etc/mtpolicyd.conf)
But you can't do content checks in
Am 2015-09-05 20:43, schrieb Viktor Dukhovni:
What I've not yet checked, is whether Fedora (like Debian) has
started splitting up Postfix into multiple RPMs with optional
databases (LDAP, MySQL, ...) in separate packages, now that Postfix
supports shared library builds, and dynamic maps. If
Am 2015-05-08 15:38, schrieb Tom Johnson:
Beside the classic pflogsumm interface my goal for the project is to
be able
to output log data to ElasticSearch and counters to graphit.
That would enable live pflogsum, interactive and in color ;-)
Have you considered integrating amavisd-new log
Am 2015-05-01 17:43, schrieb Patrick Ben Koetter:
You can find the project at Github:
https://github.com/benningm/saftpresse
ACK. Good tool. We use it a lot.
Good to know.
Beside the classic pflogsumm interface my goal for the project is to be
able
to output log data to ElasticSearch and
the manpage.
Markus
Am 2015-05-05 11:43, schrieb Birta Levente:
On 01/05/2015 17:45, Benning, Markus wrote:
Hi,
if you are willed to test my pflogsumm fork and to provide some sample
loglines
i'll implement postscreen statistics.
You can find the project at Github:
https://github.com/benningm
Hi,
if you are willed to test my pflogsumm fork and to provide some sample
loglines
i'll implement postscreen statistics.
You can find the project at Github:
https://github.com/benningm/saftpresse
I modularized the pflogsumm code into seperate plugins:
Am 2015-02-27 14:45, schrieb MickTW8:
This issue I have is knowing how to read any of the attributes listed
here
www.postfix.org/SMTPD_POLICY_README.html#protocol
Hello Mick,
it may be an option for your to implement your code as a plugin for
mtpolicyd.
There's documentation for wrinting a
Am 2015-03-01 12:38, schrieb Mick:
Hello Markus,
Thanks very much for your reply. I didn't come across Cookbook in my
searches but I don't think I will need it now as I'm very pleased to
report I got my first test policy implemented yesterday evening. Don't
laugh, all it does so far is block
Am 2015-01-22 10:26, schrieb hyndavirap...@bel.co.in:
I have enabled enable_long_queue_id = yes
Now my doubt is how long, queueids will be unique, for 150 mails/min
mail
flow?
The id is build from the time and the file-id within the filesystem.
So each queue_id should be locally unique.
The
-Original Message- From: Noel Jones
Sent: Saturday, January 17, 2015 12:20 AM
You want to conditionally run some extra restrictions based on the
outcome of prior restrictions? Some of the existing policy servers
do weighted scoring, which gives very similar results.
Conditional
Am 2015-01-09 07:27, schrieb m...@ruggedinbox.com:
Hi all, when hardening dovecot against the POODLE vulnerability,
we followed the advise to disable SSL2 and SSL3
but this is giving problems with some email clients (claws-mail).
ssl_protocols = !SSLv2 !SSLv3
results in the following error:
::HowtoAccountingQuota
--
Markus
Am 2014-12-23 13:50, schrieb Benning, Markus:
I just implemented a first version of a accounting plugin for
mtpolicyd:
https://www.mtpolicyd.org/documentation.html#Mail::MtPolicyd::Plugin::Accounting
github project: https://github.com/benningm/mtpolicyd
I'm currently
plugin
to enforce limits and then release it with the next version.
Markus
On Sat, Dec 20, 2014 at 02:16:56PM +0100, Benning, Markus wrote:
Hello,
i created a policyd called mtpolicyd. You can find the project
website at:
https://mtpolicyd.org/
It is written in perl and is easily
Hello,
i created a policyd called mtpolicyd. You can find the project website
at:
https://mtpolicyd.org/
It is written in perl and is easily extentible thru perl plugins.
Currently its main target is spamfiltering/reputation and therefor i'm
already using it in production.
I'll have to
28 matches
Mail list logo
