Joe Morris (NTM) wrote:
Sandy Drobic wrote:
Theo v. Werkhoven wrote:
Reporting-MTA: dns; jmorris.home
X-Postfix-Queue-ID: 639CC26F0DF
X-Postfix-Sender: rfc822; [EMAIL PROTECTED]
Remote-MTA: dns; smtp.postoffice.net
Diagnostic-Code: smtp; 553 Invalid sender domain
The mailserver at postoffice.net checked for the existence of
"jmorris.home", and couldn't find it, which is not surprising.
I think he already solved the problem, but asked why yast did not set
up generic as required, when he configured postfix in yast.
Almost correct. I did find the problem. The Yast MTA module has a
Masquerading button, which effectively edits sender_canonical and
creates the hash. This has worked up until 10.2. This quit working
with 10.2, so I did some digging. I believe it still changed the from
address, but somehow there was a header line, X-Postfix-Sender (see
above), with the original sender. Research seemed to indicate what I
needed to use was generic and not sender_canonical. So, I added via
What I find strange about this is why this header was added at all.
Headers with the format X-xxxxxx are non-standard headers, and a closer
look in this case reveals that it isn't a header at all, it is part of the
body of the bounce message.
POSTFIX_ADD_GENERIC the hash type and path to /etc/sysconfig/postfix, as
well as added generic to the postfix maps SuSEconfig creates. I then
added the same mapping as in sender_canonical to generic, ran
SuSEconfig, and it fixed the problem. So my question I guess, in the
interest of making 10.2 a great release, is has postfix changed in this
regard, has generic vs sender_canonical changed, which may need a bug
report for the Yast module, or have I made some flawed steps in my
understanding or troubleshooting?
Can't say that without more details. It should work with canonical as
well, but it might be that additional settings are necessary.
Here's what the documentation say:
By default the canonical(5) mapping affects both message
header addresses (i.e. addresses that appear inside messages)
and message envelope addresses (for example, the addresses
that are used in SMTP protocol commands). This is controlled
with the canonical_classes parameter.
NOTE: Postfix versions 2.2 and later rewrite message headers
from remote SMTP clients only if the client matches the
local_header_rewrite_clients parameter, or if the
remote_header_rewrite_domain configuration parameter speci-
fies a non-empty value. To get the behavior before Postfix
2.2, specify "local_header_rewrite_clients = static:all".
It might be worth to investigate this. Could you check your configuration
in for these settings with output of postconf:
- "postconf local_header_rewrite_clients"
- "postconf remote_header_rewrite_domain"
- "postconf canonical_classes"
I can't really comment on the yast module for the postfix
configuration, since I never used it (I always configure all files
manually).
Sandy
I figured as much. I have appreciated your depth of postfix knowledge,
Sandy, but for me SuSEconfig's postfix script and the Yast module have
done a very good job for the most part, and improving it would help more
users in the long run. Thanks again for your thoughts.
The yast modules is helping to set up a local server for a small company
or a home network. Most of these users don't need to work out the finer
details of antispam configuration or tune the server for effective use of
available resources.
A few weeks ago I set up a temporary replacement server for our
mailgateway (Suse 9.2 needed to be upgraded) and tried to set up the basic
config with the postfix yast module (now on Suse 10.0). Half way during
the configuration I didn't understand what settings yast offered to me and
gave up.
My trouble appearantly was that I couldn't understand Yast anymore since
it didn't speak to me in Postfix terms. (^-^)
Sandy
--
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
