Thanks so much, Viktor
I tried the config from your last email and got the same results:
rcpt to: t...@fongaboo.com
550 5.1.1 : Recipient address rejected: User unknown in
relay recipient table
I returned config to:
# relay_domains = whitehouse.gov
# relay_recipient_maps = inline:{@=@}
On Thu, Dec 08, 2022 at 01:16:34PM -0600, Scott Mutter wrote:
> I'm just beginning to look at Postfix configurations (at a very leisurely
> pace I might add).
You reall should read the Postfix book by Ralf and Patrick, despite its
age, it substantially applies to all Postfix releases since.
The
Dnia 8.12.2022 o godz. 13:16:34 Scott Mutter pisze:
> In an SMTP transaction there are certain commands that pertain to certain
> areas of the SMTP message, specifically:
>
> MAIL FROM
> RCPT TO
> DATA
>
> In Exim, there is an ACL configuration block - acl_smtp_mail - that can be
> used to
On 08.12.22 13:16, Scott Mutter wrote:
In Exim, there is an ACL configuration block - acl_smtp_mail - that can be
used to parse the information presented in the MAIL FROM command and this
determines if the connection should be allowed to proceed.
Likewise, there is an ACL configuration block -
I'm just beginning to look at Postfix configurations (at a very leisurely
pace I might add).
I come from a mostly Exim background, so the configuration of Postfix is
really somewhat foreign to me.
In an SMTP transaction there are certain commands that pertain to certain
areas of the SMTP
On Thu, Dec 08, 2022 at 11:44:53AM -0500, Jonathan Capra wrote:
> I tried the config from your last email and got the same results:
>
> rcpt to: t...@fongaboo.com
> 550 5.1.1 : Recipient address rejected: User unknown in
> relay recipient table
In other words, Postfix rejects relay recipients
On Thu, Dec 08, 2022 at 04:48:25PM +, Sean Hennessey wrote:
> Thanks. Can you point me to docs or what to search for to set up the
> per-sender default transports? I might be able to make that work.
> Running multiple postfix instances isn't a show stopper for me for
> this exercise.
Easily
On 12/5/2022 10:03 AM, post...@ptld.com wrote:
Is there a way, in postfix, to run a script when the authentication
fails, please ?
I would like to use nftables sets, with the timeout option, to ban IP
addresses. I know fail2ban exists, but I am considering other options.
nftables sets,
Thanks. Can you point me to docs or what to search for to set up the per-sender
default transports? I might be able to make that work. Running multiple postfix
instances isn't a show stopper for me for this exercise.
-Original Message-
From: owner-postfix-us...@postfix.org On
Behalf
Thanks so much, Viktor
I tried the config from your last email and got the same results:
rcpt to: t...@fongaboo.com
550 5.1.1 : Recipient address rejected: User unknown in
relay recipient table
I returned config to:
# relay_domains = whitehouse.gov
# relay_recipient_maps = inline:{@=@}
On Thu, Dec 08, 2022 at 04:01:26PM +, Sean Hennessey wrote:
> As is sometimes the case, this has turned a bit into going down a
> rabbit hole. I find the case now that it would be "really nice" to be
> able to also throw from addresses in the loop here. So basically, if
> the from address is
As is sometimes the case, this has turned a bit into going down a rabbit hole.
I find the case now that it would be "really nice" to be able to also throw
from addresses in the loop here. So basically, if the from address is
a...@somewhere.com, then I want to relay X% of traffic to one relay as
Dnia 8.12.2022 o godz. 11:29:35 Sam pisze:
> My plan is to pass port 465
> straight to haproxy, then haproxy does the encryption in and out.
> Ports 587 and 25 won't even be exposed. I only need one port. What
> kind of scenario are we trying to prevent?
Is your Postfix instance for sending mail
On 06.12.22 02:58, linux...@gmx.net wrote:
If I have setup this:
smtpd_sender_restrictions = reject_sender_login_mismatch
does it work?
- you need proper smtpd_sender_login_maps
- restriction only applies for envelope (mail from:) address, not to header
(From:) address. you may apply
On Thu, Dec 08, 2022 at 11:29:35AM +0400, Sam wrote:
> Thank you very much for your quick reply and insight. I went ahead and
> disabled wrapper mode in master.cf (and there's no wrapper mode in
> main.cf), and I still can't telnet to port 465, even though it's in use
> in the container. When
15 matches
Mail list logo
