On 24.03.23 09:16, fh--- via Postfix-users wrote:
I have a domain setup in postfix as virtual domains.
But MX records for this domain point to external systems currently,
such as google workspace.
When other users in this postfix system send email to users in this
domain, will it be delivered l
According to
https://www.postfix.org/CONNECTION_CACHE_README.html#implementation there
are "two connection caching strategies".
Are smtp_connection_cache_on_demand and
smtp_connection_cache_destinations mutually exclusive?
ie, if I enable smtp_connection_cache_destinations, does the on_demand
On 25.03.23 08:26, Amit Gupta via Postfix-users wrote:
According to
https://www.postfix.org/CONNECTION_CACHE_README.html#implementation there
are "two connection caching strategies".
Are smtp_connection_cache_on_demand and
smtp_connection_cache_destinations mutually exclusive?
smtp_connectio
smtp_tls_security_level = may/encrypt sets global policy for the server. Is there a way
to override that on a per user basis when delivering mail to another public server? For
example if the server default is "may" can email being sent from
a_select_u...@example.com behave as if smtp_tls_securi
postfix--- via Postfix-users:
> smtp_tls_security_level = may/encrypt sets global policy for the
> server. Is there a way to override that on a per user basis when
> delivering mail to another public server? For example if the server
> default is "may" can email being sent from a_select_u...@exampl
On Sat, Mar 25, 2023 at 02:43:35PM -0400, Wietse Venema via Postfix-users wrote:
> postfix--- via Postfix-users:
> > smtp_tls_security_level = may/encrypt sets global policy for the
> > server. Is there a way to override that on a per user basis when
> > delivering mail to another public server? F
Hi, Is there any reason for smtp_connection_cache_time_limit to be set
differently than connection_cache_ttl_limit?
It seems like cache TTL would be limited by whichever one of these
parameters is lower. Is this a correct understanding?
I was reading the CONNECTION_CACHE_README and it says the f
On Sat, Mar 25, 2023 at 12:46:26PM -0700, Amit Gupta via Postfix-users wrote:
> Hi, Is there any reason for smtp_connection_cache_time_limit to be set
> differently than connection_cache_ttl_limit?
No. After all, both have the same default. But also note that the
reason there are two parameters
On 25/03/23 11:50, raf via Postfix-users wrote:
On Fri, Mar 10, 2023 at 09:11:58AM +1300, Peter via Postfix-users
wrote:
* Don't add a Reply-To:. I actually question if this is really needed as we
likely want replies to go to the list the vast majority of time anyways. I
have seen other lis
Peter via Postfix-users skrev den 2023-03-26 01:05:
Mailman has a setting that addresses this, reply_goes_to_list.
According to mm docs, this adds the original From: address as a CC
there will be a day when mailman dont sink ships, so titanik survived
it, if just mailman was called AFTER rspa
On 26/03/23 13:55, Benny Pedersen via Postfix-users wrote:
Peter via Postfix-users skrev den 2023-03-26 01:05:
Mailman has a setting that addresses this, reply_goes_to_list.
According to mm docs, this adds the original From: address as a CC
there will be a day when mailman dont sink ships, so
Peter via Postfix-users skrev den 2023-03-26 06:15:
DKIM and ARC signatures need to be checked right after the message is
received,
not really, all that is needed is to frezze stata of dkim, arc, dmarc at
recieve state, when this is frezzed in arc, then downstreams can trust
it or dont care
12 matches
Mail list logo
