Thank you for your reply!
Is there any plans to implement to "Expires" header as Postfix feature?
It is defined in RFC-5536, and sometimes others MTA has that feature.
Azusa
- Original Message -
> From: Wietse Venema
> To: Postfix users
> Cc:
> Date: 2019/2/18, Mon 21:46
> Subject: R
failure to the caller, the
> > successful outcome was treated as a failure (whose reason would
> > have already been logged if it were a real failure).
> >
> > The patch is a one liner, below.
>
> I have uploaded postfix-3.4.1-RC1 (stable) and postfix-3.5-20190304
> (un
On Tue, Mar 05, 2019 at 06:03:47AM +0500, Mike Kazantsev wrote:
> Thanks for testing this one-file case, such a quick patch and releases.
You're welcome.
> It's rare that such things are bugs and not my misconfiguration, so
> apologies for maybe being too long-winded in describing the wrong prob
> On Mar 4, 2019, at 9:14 PM, Mayhem wrote:
>
> The spam bots are not that short-lived though. I see the same IP's for weeks
> on end.
>
> It's unfortunate that there are no internal options available to handle this
> issue, so I will rely on fail2ban to blacklist the offenders that fail the
> D
The spam bots are not that short-lived though. I see the same IP's for weeks
on end.
It's unfortunate that there are no internal options available to handle this
issue, so I will rely on fail2ban to blacklist the offenders that fail the
DNSBL checks.
Thank you for your time.
Wietse Venema wrote
On Mon, 4 Mar 2019 18:43:32 -0500
Viktor Dukhovni wrote:
> > Neither of these tells me what the problem with TLS engine was, and why
> > it stopped working in 3.4.0, which I think is the main problem here.
>
> The reason there's no logging of a problem, is that there is no
> problem to log! :-
ason would
> have already been logged if it were a real failure).
>
> The patch is a one liner, below.
I have uploaded postfix-3.4.1-RC1 (stable) and postfix-3.5-20190304 (unstable).
Wietse
On Tue, Mar 05, 2019 at 04:02:36AM +0500, Mike Kazantsev wrote:
> And logs only show two kinds of messages on delivery:
>
> postfix/smtp[16394]: initializing the client-side TLS engine
> postfix/smtp[16393]: 869C7A23AD: TLS is required, but our TLS engine is
> unavailable
>
> Neither of the
Hello,
I have recently updated postfix on Arch to 3.4.0 and had an interesting
hard-to-debug (with my limited knowledge) problem where it fails to
deliver all mail to relayhost via TLS.
main.cf configuration file for that host looks like this:
https://gist.github.com/mk-fg/f9ac42ff34a5694ce24cd
Greetings, Ronald F. Guilmette!
>>Postfix is in a different league than software that just runs the
>>system into the ground under load, and that requires a babysitter
>>to become unstuck.
> Thanks for the clarification and the clarity.
> You wouldn't happen to have the names of any products tha
Wietse Venema:
> Wietse Venema:
> > Ian! D. Allen:
> > > On Sun, Mar 03, 2019 at 03:51:35PM -0500, Wietse Venema wrote:
> > > > smtp unix - - n - - smtp
> > > > -o { smtp_generic_maps = inline:{{idal...@idallen.ca =
> > > > you@college}}}
> > > > This update
Wietse,
On 04/03/2019 15:34, Wietse Venema wrote:
> Vsevolod Stakhov:
>> I don't call any library, I have my own implementation of the milter
>> protocol. It checks for any errors that could arise but there are no
>> errors of course, or I would have not asked this question.
>
> Could that be a p
Vsevolod Stakhov:
> I don't call any library, I have my own implementation of the milter
> protocol. It checks for any errors that could arise but there are no
> errors of course, or I would have not asked this question.
Could that be a problem? Before I sink any time into this, does the
problem a
On 04/03/2019 15:23, Vsevolod Stakhov wrote:
> Bill,
>
> On 04/03/2019 15:11, Bill Cole wrote:
>> On 4 Mar 2019, at 6:58, Vsevolod Stakhov wrote:
>>
>>> Hello,
>>>
>>> I'm trying to debug one issue with the milter interface in Postfix. I
>>> want to remove multiple headers with the same name, for
Bill,
On 04/03/2019 15:11, Bill Cole wrote:
> On 4 Mar 2019, at 6:58, Vsevolod Stakhov wrote:
>
>> Hello,
>>
>> I'm trying to debug one issue with the milter interface in Postfix. I
>> want to remove multiple headers with the same name, for example:
>>
>> X-Spam-Flag: No
>> X-Spam-Flag: No
>> X-S
Mayhem:
> postscreen_dnsbl_max_ttl :
>
> The maximum amount of time that postscreen(8) will use the result from a
> successful DNS-based reputation test before a client IP address is required
> to pass that test again.
Postscreen requires that a remote SMTP client PASS zero or more
TESTs before
On Mon, Mar 04, 2019, Bill Cole wrote:
> Again, I have not tested this but I know that chgheader CAN return an error
> and would expect it to do so when passed an out-of-range index.
Did you check the documentation?
> Return values exist for good reasons. One of them is to help novice coders
> a
On 4 Mar 2019, at 6:58, Vsevolod Stakhov wrote:
Hello,
I'm trying to debug one issue with the milter interface in Postfix. I
want to remove multiple headers with the same name, for example:
X-Spam-Flag: No
X-Spam-Flag: No
X-Spam-Flag: Not really
X-Spam-Flag: No
To do that, I track headers on
Hello,
I'm trying to debug one issue with the milter interface in Postfix. I
want to remove multiple headers with the same name, for example:
X-Spam-Flag: No
X-Spam-Flag: No
X-Spam-Flag: Not really
X-Spam-Flag: No
To do that, I track headers on header phase and track numbers for each
header. For
thanks i had permit and dont work noi use PERMIT and work corretly
*
Este mensaje y todos los archivos adjuntos son confidenciales y de uso
exclusivo por parte
de su/sus destinatario/s. Si usted ha re
You could build a cidr file (say /etc/postfix/postscreen_access.cidr)
to whitelist gmail servers with the output from:
dig +short _spf.google.com TXT|awk '{for (f=1; f<=NF; f++) {if
(substr($f,1,8)=="include:") print substr($f,9)}}'|xargs -I {} dig
+short {} TXT|awk '{for (f=1; f<=NF;f++) {if (sub
this is my postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
allow_percent_hack = no
allow_untrusted_routing = yes
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
content_filter = smtp-amavis:[127.0.0.1]:10024
debug_peer_list = 213.97.47.158 192.168.1
i use postscreen
postscreen_dnsbl_sites = cbl.abuseat.org=127.0.0.2*3
b.barracudacentral.org=127.0.0.2*3 bl.spamcop.net=127.0.0.2*2
hostkarma.junkemailfilter.com=127.0.0.2*2
hostkarma.junkemailfilter.com=127.0.0.4*1
dnsbl.sorbs.net=127.0.0.[2;3;4;5;9;10$
the line does not fit me completely
On 04.03.19 10:55, Francesc Peñalvez wrote:
Subject: Is there any way to add whitelist to ranges or ips domains so that
dnsbl are skipped?
Gmail has its ips stuck in almost all dnsbl spam and for that reason I
do not receive any mail from gmail, I see the rebounds that postfix
sends to the adm
Gmail has its ips stuck in almost all dnsbl spam and for that reason I
do not receive any mail from gmail, I see the rebounds that postfix
sends to the administration mail according to the failures of those ips,
but no mail arrives from that domain
--
**
On 03.03.19 21:46, Mayhem wrote:
I was under the impression that Postscreen kept a cache of the IP addresses
that failed Pregreet / DNSBL tests.Then it would use those cached results to
drop clients immediately based on that previously cached results / expire
time.
What is throwing me off is thi
26 matches
Mail list logo
