Thanks. The tip about trivial-rewrite was exactly what I needed. It was
chrooted in master.cf, setting that to 'n' fixed the issue. :)
> In this case they contain your SASL login name and password for
pomas...@raygun.zat.
Yes, I didn't bother sanitizing the logs because this is all throwaway.
It's in a vm as well. And my LAN is firewalled. :)
On 8/11/20 7:11 PM, Viktor Dukhovni wrote:
On Tue, Aug 11, 2020 at 06:47:06PM -0700, David Reagan wrote:
Here's the output of `postqueue -p`:
https://gist.github.com/jerrac/d957f37b0ce24e82aa7244a0e57f41c3#file-postqueue-p-txt
Non-verbose logging from the delivery agent is what's needed.
The status/error appears to be "address resolver failure". That made me
think it was something with dns.
It is most likely the trivial-rewrite service, performing transport
table lookups. Perhaps its entry is broken in master.cf?
Here's my postconf -n:
https://gist.github.com/jerrac/d957f37b0ce24e82aa7244a0e57f41c3#file-postconf-cf
It does not show a transport table definition, so the master.cf issue
looks more likely.
My verbose/debug maillog:
https://gist.github.com/jerrac/d957f37b0ce24e82aa7244a0e57f41c3#file-maillog-log
You SHOULD NOT post verbose logs unless initial investigation of your
problem shows them to be necessary. In this case they contain your
SASL login name and password for pomas...@raygun.zat.
If you turn off the verbose logging, you might actually see what's
going on behind all the excess noise.
Any info I should add to my gist?
None, post concise data directly to the list.
1. Logging. For messages already in the queue, those would be delivery
agent logs and/or queue manager logs. How the message entered the queue
is no longer especially relevant.
2. postconf -nf
3. postconf -Mf
