On 2025-01-15 15:44:35 +1100, Viktor Dukhovni via Postfix-users wrote:
> On Wed, Jan 15, 2025 at 03:47:19AM +0100, Vincent Lefevre via Postfix-users
> wrote:
>
> > As documented in https://www.postfix.org/VIRTUAL_README.html
> > section "Mail forwarding domains", to forward mail to another user,
On Wed, Jan 15, 2025 at 03:47:19AM +0100, Vincent Lefevre via Postfix-users
wrote:
> As documented in https://www.postfix.org/VIRTUAL_README.html
> section "Mail forwarding domains", to forward mail to another user,
> I have in the /etc/postfix/main.cf file (something set up in 2009):
>
> virtua
Hi,
As documented in https://www.postfix.org/VIRTUAL_README.html
section "Mail forwarding domains", to forward mail to another user,
I have in the /etc/postfix/main.cf file (something set up in 2009):
virtual_alias_domains = vinc17.org
virtual_alias_maps = hash:/etc/postfix/virtual
and in the /e
set virtual_alias_domains explicitly to a list of your
desired virtual alias domains, or a separate table with same, unless
you really mean to have an empty list of virtual alias domains.
Do not rely on the obsolete backwards-compatibility setting:
$ postconf -d virtual_alias_domains
virtual_a
For practical reaons all Postfix address rewriting table lookups
are case-insensitive by default(*), both for the domain and local
part, regardless of what the RFCs say.
(*) When creating an indexed table, the postmap command folds the
input to lowercase before writing to the table, and code that
arts.
The manpage to virtual(5) suggests in section TABLE SEARCH ORDER that
it first tries left hand sides of the form ⟨local-part⟩@⟨domain⟩ ,
then ⟨local-part⟩ and finally @⟨domain⟩ . It also introduces the
concept of virtual alias domains and that with an empty
virtual_alias_domains , the /firs
- Message from Simon Wilson -
Date: Wed, 24 Mar 2021 09:57:37 +1000
From: Simon Wilson
Reply-To: si...@simonandkate.net
Subject: Re: Setting up virtual alias domains and maps - failing to deliver
To: postfix-users@postfix.org
- Message from Noel Jones
- Message from Noel Jones -
Date: Tue, 23 Mar 2021 12:46:29 -0500
From: Noel Jones
Reply-To: njo...@megan.vbhcs.org
Subject: Re: Setting up virtual alias domains and maps - failing to deliver
To: postfix-users@postfix.org
On 3/23/2021 6:31 AM, Simon Wilson wrote
On 3/23/2021 6:31 AM, Simon Wilson wrote:
Changes:
mydestination - removed, left as default
Don't do that. Set it to something specific maybe "localhost.local"
virtual_alias_domains = simonandkate.lan, simonandkate.net, etc...
virtual_alias_maps = hash:/etc/postfix/virtual (and postmappe
- Message from Simon Wilson -
Date: Tue, 23 Mar 2021 21:31:29 +1000
From: Simon Wilson
Reply-To: si...@simonandkate.net
Subject: Re: Setting up virtual alias domains and maps - failing to deliver
To: postfix-users@postfix.org
- Message from Simon Wilson
- Message from Simon Wilson -
Date: Tue, 23 Mar 2021 17:45:56 +1000
From: Simon Wilson
Reply-To: si...@simonandkate.net
Subject: Setting up virtual alias domains and maps - failing to deliver
To: postfix-users@postfix.org
Following recommendation from Viktor
Following recommendation from Viktor, trying to set up virtual alias domains.
Previous arrangement works fine: domains in mydestination, local
transport uses lmtp to cyrus. Here is an example of that arrangement -
sent off to Amavis, then off to lmtp for successful delivery:
Mar 23 14:25
On Mon, Sep 30, 2019 at 01:00:18PM +, Nicolas Breuer wrote:
> Indeed if i remove the IP address from "mynetworks", I got a "relay access
> denied"
Good, this is the expected behaviour.
> The behavior is strange because :
> - the MX of the domain is not this server itself.
That's not releva
iktor Dukhovni
Envoyé : samedi 28 septembre 2019 18:18
À : postfix-users@postfix.org
Objet : Re: Virtual Alias Domains
On Sat, Sep 28, 2019 at 03:55:04PM +, Nicolas Breuer wrote:
> I'm not sure you understand the issue.
Sadly, you've got the wrong end of the stick. Your logs s
On Sat, Sep 28, 2019 at 03:55:04PM +, Nicolas Breuer wrote:
> I'm not sure you understand the issue.
Sadly, you've got the wrong end of the stick. Your logs start with:
Sep 28 11:12:35 ns2 postfix/smtpd[16268]: generic_checks:
name=permit_mynetworks status=1
Sep 28 11:12:35 ns2 pos
enema
Envoyé : samedi 28 septembre 2019 17:10
À : Postfix users
Objet : Re: Virtual Alias Domains
Did you miss this?
Wietse
VIRTUAL(5) VIRTUAL(5)
NAME
virtual - Postfix virtual alias table format
SYNOPSIS
post
Did you miss this?
Wietse
VIRTUAL(5) VIRTUAL(5)
NAME
virtual - Postfix virtual alias table format
SYNOPSIS
postmap /etc/postfix/virtual
postmap -q "string" /etc/postfix/virtual
postmap -q - /etc/postf
See doc
Virtual alias domains are not to be confused with the virtual mailbox
domains that are implemented with the Postfix virtual(8) mail delivery
agent. With virtual mailbox domains, each recipient address can have
its own mailbox.
With a virtual alias
Nicolas Breuer:
>
> Hello,
>
> I'm running Postfix 3.
> I try to add a mailbox without aliasing the domain.
> The delivery is accepted, should not be because the domain is not in local
> domain file ?
>
As documented, virtual aliases can be used to alias *ANY* email
address, remote or local.
Hello,
I'm running Postfix 3.
I try to add a mailbox without aliasing the domain.
The delivery is accepted, should not be because the domain is not in local
domain file ?
virtual_alias_domains = /etc/postfix/local-host-names
virtual_alias_maps = hash:/etc/postfix/virtual
See
On Tue, Dec 03, 2013 at 09:06:10PM +0400, Igor Zinovik wrote:
> >That makes no sense. You don't have to update the LDAP records
> >for every user when adding a new domain, unless for some strange
> >reason every user needs to have an additional email address in that
> >domain. Generally, users d
ain
is not known to be local.
> the reason it is a bad idea is precisely because it forces each
> user to get yet another address when some set of user want a new
> set of addresses. Perhaps in your environment it is an axiom that
> all user addresses are valid in all virtual domains, b
reason it is a bad idea is precisely because it forces each
> > user to get yet another address when some set of user want a new
> > set of addresses. Perhaps in your environment it is an axiom that
> > all user addresses are valid in all virtual domains, but more
> > t
set of user want a new
> set of addresses. Perhaps in your environment it is an axiom that
> all user addresses are valid in all virtual domains, but more
> typically, virtual alias domains are for having an independent
> namespace for each domain.
>
I just forced to do this mapping by settings made by previous postmaster.
recisely because it forces each
user to get yet another address when some set of user want a new
set of addresses. Perhaps in your environment it is an axiom that
all user addresses are valid in all virtual domains, but more
typically, virtual alias domains are for having an independent
Hello, list.
I'm using Postfix with one hosted virtual domain and a few
virtual alias domains. All my data is stored in LDAP catalog.
Right now it is a bit tedious to add new virtual alias domain.
I need to map each user in virtual alias domain to corresponding
user in hosted d
Ben,
An issue I'm trying to solve - but never mind - I figured out a simpler way
with transport maps.
Mike Durket
On Aug 2, 2012, at 2:36 PM, Ben Rosengart wrote:
> On Thu, Aug 02, 2012 at 12:02:56PM -0700, Michael Durket wrote:
>> I have a host (A) acting as an MX for host (B). Currentl
On Thu, Aug 02, 2012 at 12:02:56PM -0700, Michael Durket wrote:
> I have a host (A) acting as an MX for host (B). Currently I do this via
> relay_domains and relay_recipient_maps. Is it possible to do this instead via
> virtual_domains and virtual_aliases? Or would a virtual_alias map entry on MX
On 8/2/2012 2:02 PM, Michael Durket wrote:
> I have a host (A) acting as an MX for host (B). Currently I do this via
> relay_domains and relay_recipient_maps. Is it possible to do this instead via
> virtual_domains and virtual_aliases? Or would a virtual_alias map entry on MX
> host A to forward
I have a host (A) acting as an MX for host (B). Currently I do this via
relay_domains and relay_recipient_maps. Is it possible to do this instead via
virtual_domains and virtual_aliases? Or would a virtual_alias map entry on MX
host A to forward user@B to user@B not work right (because the right
mouss wrote:
-
wildcard virtual aliases break recipient validation. This is a known
issue. You'll need to generate the map with a script or use sql/ldap.
Thanks for the info. As I'm running this on a vps I don't have alot of
RAM to use, I don't want to get sql/ldap involved really.
Time for
MPays wrote:
All,
I have postfix 2.3.8 running on a debian etch vps, I have everything
running as i need, with the exception of virtual aliased domains. I
would like to be able to setup forwarders on one domain, and for other
domains that are aliased to it pick up these forwarders. At the mom
All,
I have postfix 2.3.8 running on a debian etch vps, I have everything
running as i need, with the exception of virtual aliased domains. I
would like to be able to setup forwarders on one domain, and for other
domains that are aliased to it pick up these forwarders. At the moment
it reject
33 matches
Mail list logo
