I've been using Postfix for 9 years, and I really like it. There is
still one thing I can't seem to be able to do:
I' using the following config options:
virtual_mailbox_domains = proxy:mysql:virtual_mailbox_domains.sql
virtual_mailbox_maps = proxy:mysql:virtual_mailbox_maps.sql
Marc Jauvin:
I've been using Postfix for 9 years, and I really like it. There is
still one thing I can't seem to be able to do:
I' using the following config options:
virtual_mailbox_domains = proxy:mysql:virtual_mailbox_domains.sql
virtual_mailbox_maps =
Hi Wietse, I understand this.
Here is a more complete description of my problems:
We're offering mail services for our clients, we also provide dns
services for them. So in practice, most of our customers will have
their MX record point to our mail servers by default while we provide
the
On Mar 12, 2009, at 9:56, Marc Jauvin m...@r4l.com wrote:
So how can we configure postfix so that it will realize that the
mail should be routed to the NEW MX host?
1) don't top post.
2) Remove the domain from your maps.
Marc Jauvin wrote:
Now, at some point if the customer decides to point their MX records to
an external mail server (whether it handles the final delivery of the
email is of no concern to us at this point), but our mail server is not
aware of the change (and still has mapping in the internal
Marc Jauvin:
virtual maps. So at this point, if we send this customer an email at
his domain, the email will be delivered internally instead of being
sent to his NEW external MX host.
So how can we configure postfix so that it will realize that the
mail should be routed to the NEW MX
Well, other than postfix's virtual mapping rules, that's what I mean:
postfix has no idea if he's supposed to be MX host or not, because
it's treating the virtual mapping rules as authoritative, as far as
I know.
Since we have no means to know that the MX records were modified, then
we
Marc Jauvin wrote:
Well, other than postfix's virtual mapping rules, that's what I mean:
postfix has no idea if he's supposed to be MX host or not, because it's
treating the virtual mapping rules as authoritative, as far as I know.
Postfix doesn't care if it's the MX host or not, because
That's what I was afraid of... when you're hosting multi-thousands of
domains, that's not an easy task... :(
Noel Jones njo...@megan.vbhcs.org wrote:
Marc Jauvin wrote:
Well, other than postfix's virtual mapping rules, that's what I
mean: postfix has no idea if he's supposed to be MX host
Marc Jauvin:
virtual maps. So at this point, if we send this customer an email at
his domain, the email will be delivered internally instead of being
sent to his NEW external MX host.
So how can we configure postfix so that it will realize that the
mail should be routed to the NEW MX host?
On 12-Mar-2009, at 10:50, Marc Jauvin wrote:
Since we have no means to know that the MX records were modified,
then we can't remove those virtual mapping rules from our database.
$ dig mx example.com | grep -A1 ANSWER SECTION | grep MX
I suppose you could run that each day and flag domains
2009/3/13 Marc Jauvin m...@r4l.com:
Since we have no means to know that the MX records were modified, then we
can't remove those virtual mapping rules from our database.
As others have said, you need to make sure your postfix configuration
matches the reality of the situation. As I work at a
12 matches
Mail list logo
