On 18/03/2021 22:34, Antonio Leding wrote:
> Hello all,
>
>
> 1. Where to place IPBL\DNSBL rules
>
> * Because the result of a hit against an IPBL\DNSBL is to REJECT, does it
> make
> sense to place these kind of rules earlier in the SMTPD_RESTRICTIONS eval
> chain (i.e. CLI
Running postfix in k8s and using cert-manger to manage certificates it would be
nice
if postfix could pickup new certificates for long running processes like smtpd.
Much like it picks up updated databases like those managed by postmap.
I do not see any mention of this in man 5 postconf.
For now
On 19/03/2021 11:14, Leo Baltus wrote:
Running postfix in k8s and using cert-manger to manage certificates it would be
nice
if postfix could pickup new certificates for long running processes like smtpd.
Much like it picks up updated databases like those managed by postmap.
I do not see any me
On 18.03.21 22:34, Antonio Leding wrote:
1. Where to place IPBL\DNSBL rules
* Because the result of a hit against an IPBL\DNSBL is to REJECT, does
it make sense to place these kind of rules earlier in the
SMTPD_RESTRICTIONS eval chain (i.e. CLIENT) rather than later (i.e.
RECIPIENT) as s
Dear,
I have a postfix server with virtual_transport = lmtp:unix:private/dovecot-lmtp
Is there a way to send and advise to another email address each time I receive
an email?
--
---
Enrico Morelli
System Administrator | Programmer | W
Hi,
we run coverity & clang scans time to time. I filtered all the
false positives and the following are results which seemed
suspicious to me. It's mostly for unlikely code paths which
could be triggered by error state or invalid input. I am not
familiar with the code internals, so maybe it's unl
After updating from postfix.x86_64 2:3.3.1-12.el to postfix.x86_64
2:3.5.8-1.el8 I'm getting frequent log entries
Mar 19 10:51:58 mail postfix/smtpd[XX]: discarding EHLO keywords: CHUNKING
I understand an option is to disable BDAT, but I'd rather have BDAT working.
I'm not quite sure what
Hello Viktor,
Indeed, your are right again. I had '%d' in a complex query, changed it
to '%s' and extracted the substring for the domain. That did it! There
are three select statements in a UNION with the others referencing '%s'
already. Too bad there wasn't a switch to make it so '%d' doe
LoneStarKen:
> After updating from postfix.x86_64 2:3.3.1-12.el to postfix.x86_64
> 2:3.5.8-1.el8 I'm getting frequent log entries
>
> Mar 19 10:51:58 mail postfix/smtpd[XX]: discarding EHLO keywords: CHUNKING
You have one or both of
smtpd_discard_ehlo_keyword_address_maps
smtpd_dis
On Tue, Mar 16, 2021 at 05:51:07PM +0100, Matus UHLAR - fantomas wrote:
> >When the Postfix TLS security level requires authentication (mandatory
> >TLS stronger than just "encrypt"), Postfix automatically disables the
> >aNULL ciphers internally. You never need to do explicitly, except to
> >sat
On Fri, Mar 19, 2021 at 11:18:27AM -0400, Jaroslav Skarvada wrote:
> 14. postfix-3.5.8/src/util/dict_inline.c:124: uninit_use_in_call: Using
> uninitialized value "value" when calling "dict_file_to_b64".
> 17. postfix-3.5.8/src/util/dict_inline.c:125: overwrite_var: Overwriting
> "err" in "err =
On Fri, Mar 19, 2021 at 11:02:09AM -0500, LoneStarKen wrote:
> Mar 19 10:51:58 mail postfix/smtpd[XX]: discarding EHLO keywords: CHUNKING
Presumably you have a non-default setting of
smtp_discard_ehlo_keywords
possibly via master.cf overrides?
--
Viktor.
Enrico Morelli:
> Dear,
>
> I have a postfix server with virtual_transport =
> lmtp:unix:private/dovecot-lmtp
>
> Is there a way to send and advise to another email address each
> time I receive an email?
This is the wrong mailing list.
Wietse
Hi Wietse,
Thank you for the response. Those entries don't seem to exist in my main.cf or
master.cf.
I grepped (case insensitive) main.cf for ehlo, keywords, and discard and none
of those words exist.
The master.cf has a discard in the section "-o
syslog_name=postfix/$service_name" though i
On Tue, Mar 16, 2021 at 05:51:07PM +0100, Matus UHLAR - fantomas wrote:
>When the Postfix TLS security level requires authentication (mandatory
>TLS stronger than just "encrypt"), Postfix automatically disables the
>aNULL ciphers internally. You never need to do explicitly, except to
>satisfy s
On Fri, Mar 19, 2021 at 07:53:09PM +0100, Matus UHLAR - fantomas wrote:
> I mean, aNULL on port 25 is fine.
>
> aNULL on port 465 and 587 is not fine, is it?
Of course it is fine, if you're not asking for client certs, and the
client is willing to do aNULL (i.e. ignore your certificates), then
f
On Fri, Mar 19, 2021 at 01:48:53PM -0500, LoneStarKen wrote:
> Thank you for the response. Those entries don't seem to exist in my main.cf
> or master.cf.
>
> I grepped (case insensitive) main.cf for ehlo, keywords, and discard and none
> of those words exist.
Are you running a modified Post
Hi Viktor,
Maybe so. Here is output from postconf containing "discard_ehlo_keywords":
# postconf | grep discard_ehlo_keywords
postscreen_discard_ehlo_keywords = $smtpd_discard_ehlo_keywords
smtp_discard_ehlo_keywords =
smtpd_discard_ehlo_keywords = chunking
Looks like postscreen may somehow be
> On Mar 19, 2021, at 3:56 PM, LoneStarKen wrote:
>
> Maybe so. Here is output from postconf containing "discard_ehlo_keywords":
>
> # postconf | grep discard_ehlo_keywords
> postscreen_discard_ehlo_keywords = $smtpd_discard_ehlo_keywords
> smtp_discard_ehlo_keywords =
> smtpd_discard_ehlo_keyw
LoneStarKen:
> smtpd_discard_ehlo_keywords = chunking
Well there is your problem. If you did not configure this, i.e.
"postonf -d smtpd_discard_ehlo_keywords" shows "chunking", then
complain to your vendor.
Otherwise, how many (Postfix) master daemons are there on your system?
Wietse
Hi Wietse,
I think I just have one postfix master:
# ps aux | grep postfix
root1693 0.0 0.1 123108 6356 ?Ss 13:31 0:00
/usr/libexec/postfix/master -w
postfix 1703 0.0 0.2 150548 11020 ?S13:31 0:00 qmgr -l -t
unix -u
postfix 4340 0.0 0.3 154824 12
Hi Viktor,
# postconf -d | grep smtpd_discard
postscreen_discard_ehlo_keyword_address_maps =
$smtpd_discard_ehlo_keyword_address_maps
postscreen_discard_ehlo_keywords = $smtpd_discard_ehlo_keywords
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps
$virtual_alias_domains
On Fri, Mar 19, 2021 at 04:14:30PM -0500, LoneStarKen wrote:
> # postconf -d | grep smtpd_discard
> smtpd_discard_ehlo_keywords = chunking
That's the only value needed. Whoever built your package decided to
disable the ESMTP CHUNKING extension (aka BDAT). If you want/need
BDAT, you'll need to s
A fix that I recently applied for a backscatter problem.
Gmail is the example used below, but the problem and solution are not
Gmail-specific.
The problem: Spam arrives for a user, gets past spam filter, is forwarded
by receiving user to their Gmail address, gets a permanent rejection from
G
Rahul Dhesi:
> There is a second problem for which the fix is not so elegant. If Gmail
> detects spam but returns a temporary error, the spam will remain in the
> queue until its lifetime expires. The only way I found of dealing with
> this is to run a cron job that does 'mailq', finds Gmail spa
On Fri, 19 Mar 2021, Wietse Venema wrote:
See examples in:
http://www.postfix.org/postconf.5.html#default_delivery_status_filter
(this was originally designed to turn soft TLS errors into hard ones).
Thanks, that is a vey nice feature I did not know about.
I should mention that my strategy of
26 matches
Mail list logo
