From: Thelma <thelma@sys-concept.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] postfix error: External senders are prohibited to send to local recipient
Date: Mon, 8 Jul 2024 16:58:24 -0600 [thread overview]
Message-ID: <c4dfd7b0-3016-4bd4-b421-eae9f23268a1@sys-concept.com> (raw)
In-Reply-To: <9280d8d222beea42f300d1d8815dfd0a@vnecke.de>
Thank you for the input.
Yes, you are correct, in my case "postfix" was missing "sasl" flag.
I needed to run:
postmap hash:/etc/postfix/saslpass
and add entry to:
/etc/postfix/sender_canonical
now it works; until Rogers decided to add something new.
On 7/7/24 23:24, david@vnecke.de wrote:
> Hello Thelma,
>
> depends on how these files are configured in your main.cf.
> If it says
>
> smtp_sasl_password_maps = hash:/etc/postfix/saslpass
> and/or
> sender_canonical_maps = hash:/etc/postfix/sender_canonical
>
> you have to build the hashtables with
> postmap hash:/etc/postfix/saslpass
> and/or
> postmap hash:/etc/postfix/sender_canonical
>
> A "postfix reload" (or a restart of the service) might be necessary after creating the hashtables.
>
> Other filetypes might be supported too, have a look into "man postmap" for more info.
>
> Kind regards,
> David
>
> Am 2024-07-07 07:12, schrieb Thelma:
> ...
>
>>
>> ... status=bounced (host mail.domain.com[69.xx.xxx.xxx] said: 550 5.7.1 <admin@domain.com>... External senders are prohibited to send to local recipients without authentication (in reply to RCPT TO command))
>>
>> Does these two files need special command to activate them? They seem to be simple text files.
>>
>> /etc/postfix/sender_canonical
>> /etc/postfix/saslpass
>
> ...
>
prev parent reply other threads:[~2024-07-08 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 5:12 [gentoo-user] postfix error: External senders are prohibited to send to local recipient Thelma
2024-07-08 5:24 ` david
2024-07-08 22:58 ` Thelma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4dfd7b0-3016-4bd4-b421-eae9f23268a1@sys-concept.com \
--to=thelma@sys-concept.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox