| |||||||||||||||||||||||||||||||
|
become resolved within a few hours. I see what our problem was now. We actually had $mydomain in front of !subdomain.example.com in the masquerade_domains list. I had not noticed before that it is parsed from left to right and first match wins. Putting the negation case in front (left) fixed the problem. --Donald On 10/23/07, D G Teed <donald.teed> wrote: > We have 2 inbound only MX and 1 outbound SMTP - all unique postfix instances. > > There is a subdomain for which we do not handle the email, and so > the DNS MX entry handles the pointer to who does MX that email, > and on outbound SMTP we use: > masquerade_domains = !subdomain.example.com $mydomain > This set up worked OK for preventing the @subdomain.example.com > being altered on the From line. > > Now we have an issue where the users receiving the message don't > see @subdomain.example.com on the To: line, but rather @example.com > (but it does deliver OK to @subdomain.example.com through our outbound > SMTP). The docs I see say that the headers shouldn't be impacted > by default, so I don't understand why this is happening. > > I'm thinking of using masquerade_classes, but I don't see any examples > of living purpose to using each of the four possible settings. I'm reading > that if I set up all four possible settings, then SMTP can't do > delivery to our mail server inbox machines directly through virtual lookups - it > would need to send it out to our MXes to process. > > What would happen if I only set up header_sender, header_recipient > for masquerade_classes? Would that prevent the rewrite of the subdomain > in the email headers while still allowing for local delivery from SMTP > directly to our various email servers referenced in virtual? > > Regards, > > --Donald >
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com