Hi,
I'm changing postfix local delivery to LMTP dovecot delivery and I'm
have some doubts:
Before to move to LMTP I have something like this:
virtual_mailbox_maps:
h...@example.com maildir1/
ad...@example.com maildir2/
@example.com maildir1/
This works ok with "@example.com" as catcha
On Tue, Feb 22, 2022 at 10:16:26AM +0100, Víctor Rubiella Monfort wrote:
> Next test should be test to add all-accounts to alias maps:
>
> virtual_mailbox_maps:
>h...@example.com maildir1/
>ad...@example.com maildir2/
>
> virtual_alias_maps
>@example.com h...@example.com
>h...@ex
Viktor Dukhovni:
> On Tue, Feb 22, 2022 at 10:16:26AM +0100, V?ctor Rubiella Monfort wrote:
>
> > Next test should be test to add all-accounts to alias maps:
> >
> > virtual_mailbox_maps:
> >h...@example.com maildir1/
> >ad...@example.com maildir2/
> >
> > virtual_alias_maps
> >@exam
Hello,
I am trying to set up postgresql-based virtual domains. I am on
FreeBSD 13. When I try to test my domain mapping, I get a strange
error about character encodings:
# postmap -v -q example.org
pgsql:/usr/local/etc/postfix/pgsql-virtual-mailbox-domains.cf
postmap: name_mask: ipv4
postmap: n
On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
> I have enabled UTF8 in postfix as per the instructions here:
> http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> see in the following config info:
This enables UTF8 in SMTP, but does not presently affect the
On Tue, Feb 22, 2022, 14:29 Viktor Dukhovni
wrote:
> On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
>
> > I have enabled UTF8 in postfix as per the instructions here:
> > http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> > see in the following config info:
On Tue, Feb 22, 2022 at 02:32:29PM -0800, Nathan Van Ymeren wrote:
> > So UTF8 is only used in development snapshots and not in release builds.
> > This code needs to be made either conditional on EAI (UTF8) being
> > enabled, or a new user-settable PgSQL table parameter.
> >
> > > How do I get po
On Tue, Feb 22, 2022, 14:49 Viktor Dukhovni
wrote:
> On Tue, Feb 22, 2022 at 02:32:29PM -0800, Nathan Van Ymeren wrote:
>
> > > So UTF8 is only used in development snapshots and not in release
> builds.
> > > This code needs to be made either conditional on EAI (UTF8) being
> > > enabled, or a ne
Viktor Dukhovni:
> On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
>
> > I have enabled UTF8 in postfix as per the instructions here:
> > http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> > see in the following config info:
>
> This enables UTF8 in SMTP, bu
On Tue, Feb 22, 2022 at 07:10:44PM -0500, Wietse Venema wrote:
> There are two #ifdef SNAPSHOT blocks.
>
> - The one in dict_pgsql_lookup() returns not found when SMTPUTF8
> is enabled, but a query is not valid UTF8.
>
> - The one in plpgsql_connect_single() sets the PgSQL client encoding
>
On 20/02/22 05:35, Bill Cole wrote:
We have listed all IPs. We can use a FW rule, but its heavy and hard to
manage. A Postfix list may be easier.
On Linux, using ipsets instead of putting IPs directly in rules helps
a lot with managing large lists. Fail2ban can do its work via ipsets.
An alt
Hi all,
I’m having some issues figuring out if this is possible and then if so, how to
approach it. This isn’t for production use, just some internal testing and
experimentation...
My goal is to set a relay destination based on the SASL username used for smtp
authentication. So if I have users
Oops, sorry, "sender_dependent_relayhost_maps” should be
“sender_dependent_default_transport_maps” below...
> On Feb 23, 2022, at 2:17 AM, Charles Sprickman wrote:
>
> Hi all,
>
> I’m having some issues figuring out if this is possible and then if so, how
> to approach it. This isn’t for prod
13 matches
Mail list logo
