Noel Jones wrote on Thu, 8 Aug 2019 10:49:54 -0500:
> That looks like a policy service and not a milter.
Yeah, right. It's a dovecot authenticator I think.
>
> Regardless, postfix accepts mail, running it through all configured
> milters, restrictions, and policy services, then puts it in the
On 8/8/2019 10:41 AM, Kai Schaetzl wrote:
I have still one question, though.
I fear that forwarding the mail via transport may not consult the milter.
At the moment the remote Exchange is still not configured to accept the
domain. I'm still waiting for that to take place.
In the meantime,
I have still one question, though.
I fear that forwarding the mail via transport may not consult the milter.
At the moment the remote Exchange is still not configured to accept the
domain. I'm still waiting for that to take place.
In the meantime, though, I would have expected that the course of
I went back to my original config with virtual users and domains, with and
without the milter. I left transport and mynetworks as they were. I have
no idea why, but it's working now and I get a bounce from the remote
server (= it's not yet accepting the mail). No more attempts to deliver
Wietse Venema wrote on Wed, 7 Aug 2019 19:33:05 -0400 (EDT):
> Once a message enters in the hold queue IT WILL SIT THERE FOREVER
> unless something releases it from that queue.
Understood. Thanks! I should have known from the past (see below).
>
> You need to figure out why messages are placed
Kai Schaetzl:
> Noel Jones wrote on Wed, 7 Aug 2019 13:37:08 -0500:
>
> > Postfix logs all delivery attempts.
>
> I thought so, but ...
> In that case it just hangs in the queue and nothing happens after the
> milter was consulted. I can see it getting logged in rspamd and then it
> just sits
Noel Jones wrote on Wed, 7 Aug 2019 13:37:08 -0500:
> Postfix logs all delivery attempts.
I thought so, but ...
In that case it just hangs in the queue and nothing happens after the
milter was consulted. I can see it getting logged in rspamd and then it
just sits in the hold queue.
On 8/7/2019 1:11 PM, Kai Schaetzl wrote:
Kai Schaetzl wrote on Wed, 07 Aug 2019 19:11:19 +0200:
Should I remove the domain from $mydestination ?
I did that now and postfix still accepts the mail.
However, it doesn't deliver it to the remote server.
It hangs in the queue.
It's possible that
Kai Schaetzl wrote on Wed, 07 Aug 2019 19:11:19 +0200:
> Should I remove the domain from $mydestination ?
I did that now and postfix still accepts the mail.
However, it doesn't deliver it to the remote server.
It hangs in the queue.
It's possible that the remote side is not accepting that
Thanks for the reply, but no.
I had to, indeed, remove the domain from $mydestination to not deliver
locally, but it's still not working correctly.
Your map configuration lines may be wrong.
I think the only thing you need is this as a destination:
/^List@List\.TLD$/mailman3:
(no
Kai:
I think this issue might be the same as the one that I'm encountering in my
post yesterday titled, "Postfix not using LMTP Transport in map".
Can you look at your logs and see if you're getting a similar message to
what I have below?
Host postfix/lmtp[22981]: C0EEEA8:
Postfix 3.1.0, set up with virtual domains and users in a database via
virtual_ directives in main.cf
rspamd set up as a milter
-> everything works just fine.
I have one server where the client wants to get mail delivered to his
Exchange server remotely instead. He wants to have the mail
12 matches
Mail list logo
