On 8 Feb 2016, at 0:25, LuKreme wrote:

On Feb 7, 2016, at 14:12, Wietse Venema <wie...@porcupine.org> wrote:
Viktor Dukhovni:

On Feb 7, 2016, at 3:16 PM, @lbutlr <krem...@kreme.com> wrote:
/usr/local/etc/postfix which has a symlink at /etc/psotfix and

That is unlikely.
[...]
No, it is unlikely, because he said it was linked to /etc/psotfix.

I said that /usr/local/etc/postfix HAS a symlink at /etc/postfix/.

See it now?

It was about your typo.

The email had errors in command (postmap -q -q) and pathname
(/etc/psotfix) information. If someone else wants to give it
a try, they are most welcome.

All config files are in /usr/local/etc/postfix/, /etcpostfix is just a link.

Presumably you mean /etc/postfix/, which makes more sense.

Postmap -q returns th correct value, postfix itself does not access the virtual table for the header_checks or sender_bcc_maps or check_sender_access. I've provided unmunged postmap and master.cf. there are no errors or warnings in the logs.

I don't know what to do now, and I don't understand at all why you think I am lying.

Hyperliteralism? That's not a terrible trait when trying to provide technical support, given the endemic problem of people making simple config errors that are or resemble trivial typos, sometimes consciously and intentionally. Just last week someone here was arguing with Dr. Venema about how Postfix finds config files...

However, there's still something missing in what you've provided: "postconf -n" output. All of it. Preferably unmunged, but if you absolutely must obfuscate details, do so programmatically and carefully. Also, if you use ANY transport maps, include those.

The reason that's needed (at least for me...) is that you have shown mail being delivered via 'pipe' rather than 'local' or 'virtual' and that says for sure that you have a non-default delivery rig. Since your problem is in delivery, you must show how your delivery is rigged.

Reply via email to