Sandy Drobic wrote:
Joe Morris (NTM) wrote:
Sandy Drobic wrote:
- "postconf local_header_rewrite_clients" local_header_rewrite_clients = permit_inet_interfaces
Did you send the mail directly from the pc where Postfix is running or was it sent from a pc within your network? Directly from the computer running postfix.
What does "postconf inet_interfaces" say? jmorris:/home/joe # postconf inet_interfaces inet_interfaces = 127.0.0.1 ::1
I just checked a 10.1 and a 9.3, and those were the same exactly. I forgot, I have upgraded the original postfix on the 9.3 box. On the 9.3 box; joe@server:~> rpm -q postfix postfix-2.3_20051106-0.1 On the 10.1 box; joe@Sempron:~> rpm -q postfix postfix-2.2.9-10 Postfix isn't built with a single I-do-everything binary, instead it uses several programs to handle specific tasks. Generic is applied by the smtp client program, so it can only be used for mails which are handed to the smtp client, and the job of the smtp client is usually to send a mail out. So generic IS for outgoing mail.
canonical on the other hand is used by the cleanup daemon which checks a mail prior to queueing it to make sure that all required headers are present and if necessary insert it. Cleanup is also the daemon that applies header/body checks, by the way.
So these checks and rewriting take place for incoming mails, before they are queued. So the different canonical databases are for incoming mail, or with mail being scanned by amavisd-new, does all mail become incoming with regard to the queue? Some headers may not be present at the time cleanup is checking the mail, while generic will see all headers since it sees the mails at the time it leaves the system. So it could be a header added later than sender_canonical but caught by generic? If that is so, then it seems to be a new thing and may result in a bug for the Yast Postfix module (i.e. MTA).
-- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org