Update:The error message my mail client receives is as follows:
"lmtp:+51c0564a95aa31a8840305bec77e9023baa46477"@Domain.TLD *User doesn't
exist: lmtp:@Domain.TLD* (in reply to RCPT TO command)and
"lmtp:[127.0.0.1]:8024"@Domain.TLD (expanded from l...@list.tld): host
* Fazzina, Angelo :
>
> Hi, I added this to main.cf
>
> relayhost = [massmail.uconn.edu]:587
> smtp_fallback_relay = [massmail.uconn.edu]:587
> smtp_sasl_auth_enable = yes
> smtp_sasl_password_maps = hash:/etc/postfix/nexus_passwd
> smtp_sasl_security_options =
This is looking ok. You're
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
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
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
Maztec wrote on Thu, 8 Aug 2019 01:13:18 -0700 (MST):
> However, Mailman3 does not use a socket -
> nonetheless I tried.
I wrote that because your service specification in master.cf says it does
use a Unix socket.
I think you have to specify that in the mailman3 service in your
master.cf!
