On Mon, Jul 12, 2010 at 19:02, Wietse Venema <wie...@porcupine.org> wrote: > Phil Howard:
>> virtual_alias_domains already defaults to virtual_alias_maps. But >> that wasn't working. > > If you believe it is broken then you must provide the evidence, > otherwise you are just spreading false rumors. I'm not saying it is broken. I'm saying it isn't working. But that could be a misunderstanding on my part of how it is supposed to work. I always assume I misunderstand something when I can't get it to work as expected. Maybe my expectations are wrong. Or maybe my methods are wrong. That's why I'm asking, first. That fact that a domain is not being recognized as valid could be caused my many things. But I'd say the most obvious reason is because I have not configured that domain at all. It was a GUESS on my part that the existing of the domain in the virtual_alias_maps would somehow make it known that the domain is OK. But even I recognize that doing something like that would be non-trivial. For example, if incoming mail is to a non-existent users in an existing domain, looking up u...@domain does not gain any knowledge that the domain exists (at this server, somewhere) since the lookup is still going to fail. I have not yet added the domain to virtual_domain_maps since the documentation is adding a confusing element to that. I plan to do a reference test at some point with this and other configuration variations just to determine what that confusing element really means. That confusing element is that specification that virtual_alias_maps is the default value for virtual_domain_maps. > http://www.postfix.org/DEBUG_README.html#debugging I'm not debugging Postfix. I'm trying to grasp how to properly set this up. I'm assuming it can be, because it makes sense that someone would do this at some point. Jeroen's response suggests that is a reality, somewhere. But that response only rules out a few alternatives. -- sHiFt HaPpEnS!
