Huge log is being held for approval, but probably not required to pass the
message to the list.
I have found why:-
user@mydomain works
user@myhostname fails
The first is listed in virtual_users, but the latter is not. This is an Apple
thing. I'll have a look at that in the Server.app and see if I can make changes
there in case it otherwise gets overwritten in the file, but Server.app has
removed most of the configuration options.
However I am still puzzled that after the latter is not found in virtual_users,
the address checking continues to check in passwd (or OD):-
smtpd: send attr table = unix:passwd.byname
smtpd: send attr flags = 524352
smtpd: send attr key = ken
smtpd: private/proxymap socket: wanted attribute: status
smtpd: input attribute name: status
smtpd: input attribute value: 0
smtpd: private/proxymap socket: wanted attribute: value
smtpd: input attribute name: value
smtpd: input attribute value: ken:********:501:20:Ken
Gillett:/Users/ken:/bin/bash
smtpd: private/proxymap socket: wanted attribute: (list terminator)
smtpd: input attribute name: (end)
smtpd: dict_proxy_lookup: table=unix:passwd.byname flags=lock|utf8_request
key=ken -> status=0 result=ken:********:501:20:Ken Gillett:/Users/ken:/bin/bash
smtpd: maps_find: local_recipient_maps:
proxy:unix:passwd.byname(0,lock|fold_fix|utf8_request): ken =
ken:********:501:20:Ken Gillett:/Users/ken:/bin/bash
smtpd: send attr request = lookup
smtpd: send attr table = unix:passwd.byname
smtpd: send attr flags = 524352
smtpd: send attr key = @macserve.home
smtpd: private/proxymap socket: wanted attribute: status
smtpd: input attribute name: status
smtpd: input attribute value: 1
smtpd: private/proxymap socket: wanted attribute: value
smtpd: input attribute name: value
smtpd: input attribute value: (end)
smtpd: private/proxymap socket: wanted attribute: (list terminator)
smtpd: input attribute name: (end)
smtpd: dict_proxy_lookup: table=unix:passwd.byname flags=lock|utf8_request
key=@macserve.home <mailto:key=@macserve.home> -> status=1 result=
smtpd: maps_find: local_recipient_maps: @macserve.home: not found
smtpd: mail_addr_find: k...@macserve.home <mailto:k...@macserve.home> -> (not
found)
smtpd: NOQUEUE: reject: RCPT from macpro.home[10.33.33.26]: 550 5.1.1
<k...@macserve.home <mailto:k...@macserve.home>>: Recipient address rejected:
User unknown in local recipient table; from=<> to=<k...@macserve.home
<mailto:k...@macserve.home>> proto=ESMTP helo=<macserve.home>
smtpd: > macpro.home[10.33.33.26]: 550 5.1.1 <k...@macserve.home
<mailto:k...@macserve.home>>: Recipient address rejected: User unknown in local
recipient table
and despite clearly finding the user (me) it then proceeds to think it's "not
found".
How can I fix that?
Ken G i l l e t t
_/_/_/_/_/_/_/_/
> On Tue 29 Oct 2024, at 01:04, Wietse Venema via Postfix-users
> <postfix-users@postfix.org <mailto:postfix-users@postfix.org>> wrote:
>
> 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.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
