• Accepting emails without name resolution of incoming host.

    From markrlondon@gmail.com@21:1/5 to All on Mon Jun 12 08:07:10 2023
    Hi - I'm setting up a brand new sendmail server.

    I thought that FEATURE(`accept_unresolvable_domains') would accept any email. Not so.

    Some emails were still getting stuck. For example, emails from mail.easyspirit.com, which doesn't resolve. Error message in my log shows:

    Jun 10 08:54:08 psfcmail2 sm-mta[59026]: 35ACrYZS059024: to=<XX@PSFC.MIT.EDU> ... relay=localhost, dsn=4.4.2, stat=Deferred: Name server: localhost: host name lookup failure

    I found online that FEATURE(`nocanonify') could help. I'm not clear on what this does, but it helped. Why???

    Because it broke a special virtualtable configuration that I use. I can't explain that, because I don't understand that either. But I'll include that in another message, if necessary. Thanks.

    Thanks for any help. - Mark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Claus =?iso-8859-1?Q?A=DFmann?= @21:1/5 to markr...@gmail.com on Mon Jun 12 14:23:42 2023
    markr...@gmail.com wrote:

    I thought that FEATURE(`accept_unresolvable_domains') would accept any
    email. Not so.

    It does what the fine documentation claims...
    Normally, MAIL FROM: commands in the SMTP session will be
    refused if the host part of the argument to MAIL FROM:
    cannot be located in the host name service (e.g., an A or
    MX record in DNS).

    Some emails were still getting stuck. For example, emails from mail.easyspirit.com, which doesn't resolve. Error message in my log
    shows:

    Jun 10 08:54:08 psfcmail2 sm-mta[59026]: 35ACrYZS059024:
    to=<XX@PSFC.MIT.EDU> ... relay=localhost, dsn=4.4.2, stat=Deferred:
    Name server: localhost: host name lookup failure
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    That does not say anything about mail.easyspirit.com

    The error message clearly states what is wrong:
    your system is broken - it can't even look up "localhost".
    If you don't have a way to fix this in DNS or /etc/hosts
    (or you have some of those $#%^Q@^ systemd options...)
    then use [127.0.0.1] instead of localhost.

    BTW: are you sure your routing of <XX@PSFC.MIT.EDU> is correct?

    --
    Note: please read the netiquette before posting. I will almost never
    reply to top-postings which include a full copy of the previous
    article(s) at the end because it's annoying, shows that the poster
    is too lazy to trim his article, and it's wasting the time of all readers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From markrlondon@gmail.com@21:1/5 to All on Mon Jun 12 13:00:34 2023
    I did some more searching. accept_unresolvable_domains only applies to the MAIL FROM address in SMTP, Not the From: address in the actual email address. A subtle difference that has tripped people up:

    https://forums.freebsd.org/threads/sendmail-throwing-aaa-bbb-deferred-name-server-xxx-host-name-lookup-failure.70549/ So they recommend the nocanonify feature.

    But I don't know why when I turn that on, it breaks my virtualtable rule. It's some sort of hack that I don't understand, for mailman 3 to talk to sendmail using LMTP., which is above my pay level.

    I get error messages >>> RCPT To <foo@list.psfc.mit.edu.private> <<< 550 Requested action not taken: mailbox unavailable 550 5.1.1 <foo@list.psfc.mit.edu>... User unknown I need to look at this more.

    virtualtable:

    @lists.psfc.mit.edu %1%3@list.psfc.mit.edu.private

    mailertable:
    list.psfc.mit.edu.private mm3lmtp:[localhost]

    Then in sendmail.mc, I need this rule, for Mailman 3 to talk to sendmail.

    MAILER_DEFINITIONS
    Mmm3lmtp, P=[IPC], F=PSXmnz9, S=EnvFromSMTP/HdrFromSMTP,
    R=EnvToMM3, E=\r\n, L=1024,
    A=TCP $h 8024

    LOCAL_RULESETS
    SEnvToMM3
    R$+ $: $>EnvToSMTP $1
    R$+ < @ list . psfc . mit . edu . private > $* $: $1 < @ list . psfc . mit . edu . > $2

    On Monday, June 12, 2023 at 2:23:45 PM UTC-4, Claus Aßmann wrote:
    markr...@gmail.com wrote:

    I thought that FEATURE(`accept_unresolvable_domains') would accept any email. Not so.
    It does what the fine documentation claims...
    Normally, MAIL FROM: commands in the SMTP session will be
    refused if the host part of the argument to MAIL FROM:
    cannot be located in the host name service (e.g., an A or
    MX record in DNS).
    Some emails were still getting stuck. For example, emails from mail.easyspirit.com, which doesn't resolve. Error message in my log
    shows:

    Jun 10 08:54:08 psfcmail2 sm-mta[59026]: 35ACrYZS059024: to=<X...@PSFC.MIT.EDU> ... relay=localhost, dsn=4.4.2, stat=Deferred:
    Name server: localhost: host name lookup failure
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    That does not say anything about mail.easyspirit.com

    The error message clearly states what is wrong:
    your system is broken - it can't even look up "localhost".
    If you don't have a way to fix this in DNS or /etc/hosts
    (or you have some of those $#%^Q@^ systemd options...)
    then use [127.0.0.1] instead of localhost.

    BTW: are you sure your routing of <X...@PSFC.MIT.EDU> is correct?

    --
    Note: please read the netiquette before posting. I will almost never
    reply to top-postings which include a full copy of the previous
    article(s) at the end because it's annoying, shows that the poster
    is too lazy to trim his article, and it's wasting the time of all readers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From markrlondon@gmail.com@21:1/5 to markr...@gmail.com on Mon Jun 12 22:54:34 2023
    I found my solution. I had to use this command to add my virtualtable hosts. to be domains I wanted canonified,.

    Why is everything so hard~

    CANONIFY_DOMAIN(`list of domains')

    On Monday, June 12, 2023 at 4:00:35 PM UTC-4, markr...@gmail.com wrote:
    I did some more searching. accept_unresolvable_domains only applies to the MAIL FROM address in SMTP, Not the From: address in the actual email address. A subtle difference that has tripped people up:

    https://forums.freebsd.org/threads/sendmail-throwing-aaa-bbb-deferred-name-server-xxx-host-name-lookup-failure.70549/ So they recommend the nocanonify feature.

    But I don't know why when I turn that on, it breaks my virtualtable rule. It's some sort of hack that I don't understand, for mailman 3 to talk to sendmail using LMTP., which is above my pay level.

    I get error messages >>> RCPT To <f...@list.psfc.mit.edu.private> <<< 550 Requested action not taken: mailbox unavailable 550 5.1.1 <f...@list.psfc.mit.edu>... User unknown I need to look at this more.

    virtualtable:

    @lists.psfc.mit.edu %1%3...@list.psfc.mit.edu.private

    mailertable:
    list.psfc.mit.edu.private mm3lmtp:[localhost]

    Then in sendmail.mc, I need this rule, for Mailman 3 to talk to sendmail.

    MAILER_DEFINITIONS
    Mmm3lmtp, P=[IPC], F=PSXmnz9, S=EnvFromSMTP/HdrFromSMTP,
    R=EnvToMM3, E=\r\n, L=1024,
    A=TCP $h 8024

    LOCAL_RULESETS
    SEnvToMM3
    R$+ $: $>EnvToSMTP $1
    R$+ < @ list . psfc . mit . edu . private > $* $: $1 < @ list . psfc . mit . edu . > $2
    On Monday, June 12, 2023 at 2:23:45 PM UTC-4, Claus Aßmann wrote:
    markr...@gmail.com wrote:

    I thought that FEATURE(`accept_unresolvable_domains') would accept any email. Not so.
    It does what the fine documentation claims...
    Normally, MAIL FROM: commands in the SMTP session will be
    refused if the host part of the argument to MAIL FROM:
    cannot be located in the host name service (e.g., an A or
    MX record in DNS).
    Some emails were still getting stuck. For example, emails from mail.easyspirit.com, which doesn't resolve. Error message in my log shows:

    Jun 10 08:54:08 psfcmail2 sm-mta[59026]: 35ACrYZS059024: to=<X...@PSFC.MIT.EDU> ... relay=localhost, dsn=4.4.2, stat=Deferred: Name server: localhost: host name lookup failure
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    That does not say anything about mail.easyspirit.com

    The error message clearly states what is wrong:
    your system is broken - it can't even look up "localhost".
    If you don't have a way to fix this in DNS or /etc/hosts
    (or you have some of those $#%^Q@^ systemd options...)
    then use [127.0.0.1] instead of localhost.

    BTW: are you sure your routing of <X...@PSFC.MIT.EDU> is correct?

    --
    Note: please read the netiquette before posting. I will almost never
    reply to top-postings which include a full copy of the previous
    article(s) at the end because it's annoying, shows that the poster
    is too lazy to trim his article, and it's wasting the time of all readers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)