o_header_body_checks,no_milters
Try to see whether it works when you remove "no_milters"
Kind regards,
Martijn Brinkers
On 16-06-19 21:50, Peter wrote:
> On 17/06/19 2:00 AM, Stefan Bauer wrote:
>> we are running a small smtp relay service with postfix for
>> authenticated users. Unfortunately office 365 does not offer any smtp
>> authentication mechanism when sending mails via connectors to smarthosts.
>
> I
be that your postfix server now
favors ipv6 over ipv4? According to the docs, inet_protocols for <= 2.8
was set to ipv4 but is now set to all. There are other reports of issues
with using ipv6 and Gmail (for example
http://postfix.1071664.n5.nabble.com/disable-ipv6-when-sending-to-gmail-td60672.html)
Kind regards,
Martijn Brinkers
that the filter again accepts email.
Is it possible to have different queue_run_delay, minimal_backoff_time
etc. settings for the filter transport?
Thanks,
Martijn Brinkers
On Fri, 2009-01-30 at 11:43 -0600, Noel Jones wrote:
Seems to me the first action should be to reduce the number of
smtp connections to the content_filter to a number it's able
to consistently handle.
There is a big difference in filtering speed between messages. The
filter is an encryption
iminate all queues from the filter, it should be a proxy. Let Postfix
do all the queueing, it is much better at this than the filter.
The filter is based on James which is a Java based email server and
cannot be used as a proxy, at least not without a major overhaul. The
biggest reason I added
