Peter:
> On 07/06/16 22:29, Wietse Venema wrote:
> > Otherwise it replies with the query arguments plus an empty
> > address list and the reply TTL (-1 if unavailable).
> >
> > "otherwise" means that the IP address is not listed, or that no
> > reply was received.
> >
> > I have changed t
On 7 Jun 2016, at 11:48, Luca Fornasari wrote:
On Tue, Jun 7, 2016 at 5:18 PM, Wietse Venema
wrote:
[...]
You could use an SMTP-based filter that adds a blank after a boundary
line. Google for smtpprox, and configure it as a Postfix
smtpd_proxy_filter
Better, give it to the folks up-streeam
On 08/06/16 07:23, Bill Cole wrote:
> postconf(5) says:
>
> postscreen_dnsbl_min_ttl (default: 60s)
>
> So by default, postscreen will not query dnsblog regarding a specific
> address and DNSBL for 60 seconds after dnsblog has returned a TTL in the
> 0-60 range for that address and DNSBL.
Correc
On 08/06/16 08:48, Peter wrote:
>> I have changed the text to:
>>
>> Otherwise it replies with the query arguments plus an empty
>> address list and the reply TTL. The reply TTL is -1 if no
>> reply is received, or if the reply contains no TTL information).
>
> That still doesn't
On 07/06/16 22:29, Wietse Venema wrote:
> Otherwise it replies with the query arguments plus an empty
> address list and the reply TTL (-1 if unavailable).
>
> "otherwise" means that the IP address is not listed, or that no
> reply was received.
>
> I have changed the text to:
>
>
On 6 Jun 2016, at 13:39, Yuval Levy wrote:
Thanks for the help, Bill.
On 16-06-06 10:24 AM, Bill Cole wrote:
NOTE THAT 454 REPLY!
could it be because I have soft_bounce = yes while trying to
understand
the outcome of my rules without losing incoming emails?
Yes, I believe that would do
On 6 Jun 2016, at 16:51, Peter wrote:
On 07/06/16 01:07, Bill Cole wrote:
4. The resolver cache honors (as most do) a DNSBL's negative cache
TTL
which is less than 60 seconds, e.g. Spamcop (0 seconds) or the
various
Spamhaus lists (10) and others.
postscreen (specifically dnsblog(8)) honors
On Tue, Jun 7, 2016 at 5:18 PM, Wietse Venema wrote:
> Luca Fornasari:
>> In Postfix 2.3.3 the missing blank line was inserted while in Postfix
>> 2.6.6 it is not.
>> While looking at the source code diffs of src/global/mime_state.c I see
>>
>> * XXX We don't insert a blank line separ
Luca Fornasari:
> The problem is with missing blank line between MIME boundary and
> content in the body of the email i.e.
>
> --=boundary1=
> Content-type: multipart/related; boundary="=boundary2="
> --=boundary2=
> Content-type: text/html;charset="iso-8859-1"
>
> Segue tabella HTML
>
> 1A1B1C
Mr. Venema, thank you again!!
-Francesco
-Messaggio originale-
Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Per conto di Wietse Venema
Inviato: martedì 7 giugno 2016 16:19
A: Postfix users
Oggetto: Re: R: Keep messages in deferred and retry after 4 hours
i
Wietse Venema:
> Have you looked in the MAILLOG file for warning/error/fatal/panic
> messages as a result of doing these experiments? Postfix does not
> silently drop requests.
Simplify the configuration: place check_policy_service at the start
of your rules.
How do you measure the number of chec
Wietse Venema:
> Luca Fornasari:
>> I have an old Postfix 2.3.3 installation where the built-in MIME
>> parser is modifying (adjust) wrongly formatted MIME messages while
>> relaying them.
>>
>> This is not happening on a newer Postfix 2.6.6 installation and I
>> can't find any configuration parame
i...@itrezero.it:
> Thanks a lot Wietse.
> But... is it possible to limit this backoff-time to specific destinations
> (i.e. yahoo.com or hotmail.com) and not to all messages sent through a
> postfix instance?
No. Postfix is not a policy busting system.
Wietse
Thanks a lot Wietse.
But... is it possible to limit this backoff-time to specific destinations
(i.e. yahoo.com or hotmail.com) and not to all messages sent through a
postfix instance?
-Francesco
-Messaggio originale-
Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.
Sorry, maybe I was not clear enough, there are no dropped mails the all come is just that the policies are not trigerred in all.
--
eNeKuXOn 6/7/2016, 16:05 eNeKuX wrote:
From today's logs after all the tests I just have the next warnings, which were triggered wh
From today's logs after all the tests I just have the next warnings, which were triggered when I had in "main.cf" file the parameter: "smtpd_delay_reject=no"
# egrep '(warning|error|fatal|panic):' /var/log/mail.log
Jun 7 14:58:28 gobantest postfix/smtpd[21057]: warning: access table rege
i...@itrezero.it:
> Now I need an evolution of this configuration: I want to retain all messages
> to specific destinations in the Deferred queue and make the first retry
> after. 4 hours!
postconf -e minimal_backoff_time=4h
postfix reload
Wietse
Have you looked in the MAILLOG file for warning/error/fatal/panic
messages as a result of doing these experiments? Postfix does not
silently drop requests.
Wietse
Hi again Wietse,
as you pointed out we have "smtpd_delay_reject=no" configured in our "master.cf" as it is suggested for integration of amavisd-new with postfix:
https://www.ijs.si/software/amavisd/README.postfix.html#filter_service_global
We have tried setting the parameter to "yes" but w
Hi all.
I have the following settings in my Postfix main.cf. All is ok for
destinations where I need to send a limited number of messages in a specific
time:
transport_maps = hash:/etc/postfix/transport
veryslow_destination_rate_delay = 3s
slow_destination_rate_delay = 1s
Every message is
Luca Fornasari:
> Greetings everyone,
>
> I have an old Postfix 2.3.3 installation where the built-in MIME
> parser is modifying (adjust) wrongly formatted MIME messages while
> relaying them.
>
> This is not happening on a newer Postfix 2.6.6 installation and I
> can't find any configuration par
On 2016-06-07 05:15, Rich Wales wrote:
Does Postfix support blacklisting / whitelisting for IPv6 addresses?
yes
If so, is there any documentation available to help me with the
details?
http://www.postfix.org/IPV6_README.html
I'm running Postfix version 2.11.0 on an Ubuntu 14.04.4 LTS syst
Greetings everyone,
I have an old Postfix 2.3.3 installation where the built-in MIME
parser is modifying (adjust) wrongly formatted MIME messages while
relaying them.
This is not happening on a newer Postfix 2.6.6 installation and I
can't find any configuration parameter to restore the old behavi
Rich Wales:
> Does Postfix support blacklisting / whitelisting for IPv6 addresses?
Yes.
> If so, is there any documentation available to help me with the details?
Works in the same way.
x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.$dnsbl
where x is a hex digit, and where is more x.x.x.
> I'm ru
Peter:
[ Charset windows-1252 converted... ]
> On 07/06/16 12:23, Wietse Venema wrote:
> >> dnsblog(8) states, "Otherwise it replies with the query arguments plus
> >> an empty address list and the reply TTL (-1 if unavailable)." It is
> >> unclear that this references the negative cache TTL as re
> On Jun 7, 2016, at 2:46 AM, Alice Wonder wrote:
>
>
> Isn't generally better to use a new private key?
Not if doing so makes it impractical to maintain correct TLSA records.
Specifically, if certificate renewals are frequent and automated, it
becomes difficult to pre-stage new keys and assoc
mehmet gmail.com> writes:
>
> Hi,
>
> I am using postfix with latest version for smtp. And for pop3, I am using
> dovecot with Maildir.
> Postfix is running on centos.
>
> I have couple of users on the system (I have created users with useradd
> command with nologin). I want to configure som
27 matches
Mail list logo
