Mailinglist Archive: opensuse (4633 mails)

< Previous Next >
Re: [opensuse] Postfix Qwerkiness
  • From: Sandy Drobic <suse-linux-e@xxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 22 Jan 2007 23:24:05 +0100
  • Message-id: <45B53985.3070302@xxxxxxxxxxxxxxxxxxxxxxx>
Brian Blater wrote:

Hey, this is not Windows!

LOL, however in this case it is a test box and I'm documenting the
install etc. So, when things started acting weird and such I wanted to
go back through it and make sure I didn't deviate from the install
documents. Better me to reinstall and get the install instructions
perfected so if someone else has to install/support it, they can get
it right the first time.

I hate to tell you but not even the best install documentation will be fool-proof. No documentation will ever replace true understanding of a program. The best way is probably to post a few commands that show the configuration, write down how it is supposed to look and how you can modify it to match the documentation and verify it works.

Otherwise you will have to start with listing all dependencies and every file and the settings within that you regard as neccessary.

The most professional way would probably be to build a rpm package and make sure that all files in the package will replace existing ones.

Then you can simply say "install the postfix package with rpm and be done."

I tried to do that last year with the Postfix gateway installation in our company, and finally resigned when more and more details popped up that had to be explained what they are doing and how to verify that it works.

Now I have an written guide telling my collegues how to use an almost identical vmware installation in case of emergency if the main server is unresponsive and they can't solve the problem.


>> > The transport file has
>> > domain.com smtp:[w.x.y.z]
>> > anotherdomain.com smtp:[w.x.y.z]

What does "postconf transport_maps" say?
The default is empty.

Output of "postconf -n" shows what parameters deviate from default (or
were manually defined in /etc/postfix/main.cf).

Ok. The postconf -d you used in the first message just shows what was
default correct?

Yes. Postfix has an excellent documentation. Wietse takes great pain to ensure that the documentation is accurate and up-to-date.

Also, If I'm not mistaken, you usually just modify the main.cf
yourself instead of using yast. How would I go about adding the change
to myorigin without manually editing the main.cf or using postconf -e
(which I think will cause SuSEconfig to choke on the file)? Is the
only way to add the change via the /etc/sysconfig/postfix file with
POSTFIX_ADD_MYORIGIN = ?

Okay, you've got me there. Since I usually modify settings directly I never tried to do it the Yast way. The one thing I would like to remember is where in Yast the setting was to tell Yast NOT to touch the Postfix configuration.

Sandy
--
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >