Ken Gillett via Postfix-users:
> Thank you for your words of wisdom Wietse. ??>
> I rather thought you understood how 'silly' it would be to run a find command
> for postconf as I had already clearly explained (at least 3 times ?? I knew
> where both versions were located and always ensured I was running the correct
> one. Apologies if I wasn't clear enough for you. ??>
> In any case, to please you I did run it and er, it confirmed what I have been
> saying. 2 postconfs, each in the location I said they were.
>
> I have now established which master is running and unless postfix reads
> configuration from a main.cf other than what it has been told to use when
> executed, I am running the MacOSX Server install of postfix which uses
> /Library/Server/Mail/Config/postfix/main.cf. End of.
>
> However, postfix is still exhibiting errant behaviour:-
>
> user@mydomain works
>
> user@myhostname fails
>
> Help with troubleshooting this issue is much appreciated.
Use the right postconf command to verify that the configuration of the
running master matches the settings that you poresented in the
first postihg and that I verified on my own machine.
If that configuration is what is running, then any difference in
behavior is due to something that you or Apple did, snf for which
I cannot be held responsible..
> Is there perhaps a postfix utility to which you can pass an address
> and have it spit out exactly how it is dealt with? So it would
There is a way to make the Postfix SMTP daemon more chatty in the
logfile, but that works only if you can update and verify the right
configuration files. Which you haven't, going by your reports sofar.
/path/to/postconf debug_peer_list=ip-of-telnet-client
/path/to/postconf debug_peer_level=2
/path/to/postfix reload
where ip-of-telnet-client is the IP address of the client
that you use to send the commands with telnet.
> e.g. reveal what it thinks is the domain, what it thinks is the
> user to be validated. Is there anything like that? Currently all
> I know is that one doesn't work, without any indication of what
> is being done internally and hence resulting in the failure. Is
> there anything really useful like that?
The debug logging will show the working of the guts, but it will
take someone like Viktor or me to make sense of the gibberish.
Wietse
> Otherwise I'll just have to put this down to postfix failure in a Mac Server
> and wait until I can start with a clean install on a *nix replacement server.
>
>
> Ken G i l l e t t
>
> _/_/_/_/_/_/_/_/
>
>
>
> > On Mon 28 Oct 2024, at 19:00, Wietse Venema via Postfix-users
> > <postfix-users@postfix.org> wrote:
> >
> > Ken Gillett via Postfix-users:
> >> Does 'postconf daemon_directory' simply return info from the
> >> main.cf, or does it query the running process to get exactly what
> >> is being used?
> >
> > Don't be silly. By design, the postconf command uses the same
> > main.cf file as the master daemon.
> >
> > If you have more than one Postfix installation, then you need to find the
> > postconf command that "belongs" to the same installation as the
> > running master daemon.
> >
> > Again for the third time.
> >
> > As root, execute the command:
> >
> > find / -name postconf
> >
> >> Which still leaves the question of why emails to user@myhostname are
> >> rejected.
> >
> > You are looking at the wrong configuration with the wrong postconf command.
> >
> > Over and out.
> >
> > Wietse
> > _______________________________________________
> > Postfix-users mailing list -- postfix-users@postfix.org
> > To unsubscribe send an email to postfix-users-le...@postfix.org
>
> _______________________________________________
> Postfix-users mailing list -- postfix-users@postfix.org
> To unsubscribe send an email to postfix-users-le...@postfix.org
>
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
