other side of reject_unverified is postfix checking all
addresses, even located on the internet what is not always welcome.
Is there any way to limit reject_unverified_recipient to local
domain? Or maybe I can use maps for using unlisted_recipient instead?
--
Sincerely yours,
Dima Veselov
Physics R&a
unix:private/policy-spf
And AFAIK there is no way other _restrictions make postfix skip checking
of recipient_restrictions.
Is there any circumstances that can make postfix skip SPF?
--
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
I found that private/lmtp is the service which do
the actual transport into other LMTPs, so it should not be
replaced in any way.
This was my mistake, excuse me.
On 14.06.2021 17:43, Dima Veselov wrote:
Greetings,
I am using Postfix 3.6.0 on NetBSD 9.2 with Dovecot 2.3.14
acting as LMTP
=
lmtp_connection_cache_on_demand = yes
lmtp_connection_cache_time_limit = 2s
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
or mailhub (if
situation persists). My conclusion: its too early.
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
cal",
and local aliases(5) would rewrite the address to "ivan" (possibly
with an appropriate @domain suffix), and deliver to the user's mailbox.
That is what I am wondering most about. Do we really have to rewrite
anything? Or you just mean aliases(5) will find proper mailbox to drop
mail in?
--
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
ddress which will never be seen except technical headers?
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
, May 27, 2020 at 06:13:46PM +0200, Matteo Cazzador wrote:
example1.com smtp:gw1.gateway.com
example2.com smtp:gw2.gateway.com
example3.com smtp:gw3.gateway.com
than i use make "postmap transport".
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Sa
