[opensuse] Postfix Qwerkiness

newer
[opensuse] Compiling Driver for...

Brian Blater

22 Jan 2007 22 Jan '07

13:32

I have a 10.2 box running as a postfix mail gateway for a couple of domains I have. This box is running spamassassin, maia mailguard and clamav. Local mail is disabled on this machine. I've setup postfix so that myhostname = mail.domain.com relay_domains = domain.com anotherdomain.com mydomain = domain.com relayhost = 1.2.3.4 The transport file has domain.com smtp:[w.x.y.z] anotherdomain.com smtp:[w.x.y.z] The virtual file has root me@domain.com vscan me@domain.com vscan@mail.domain.com me@domain.com Here's the qwerky part that I can't figure out. When the maia script runs in the vscan crontab it sends a mail message to vscan@mail.domain.com. I see this in the log file: Jan 21 19:00:11 mail postfix/pickup[22275]: D07832078F: uid=65 from=<vscan> Jan 21 19:00:11 mail postfix/cleanup[22582]: D07832078F: message-id=<20070122000011.D07832078F@mail.domain.com> Jan 21 19:00:11 mail postfix/qmgr[5929]: D07832078F: from=, size=837, nrcpt=1 (queue active) Jan 21 19:00:11 mail postfix/error[22584]: D07832078F: to=, orig_to=<vscan>, relay=none, delay=0.19, delays=0.18/0/0/0.01, dsn=5.0.0, status=bounced (local mail delivery is disabled) Jan 21 19:00:11 mail postfix/bounce[22585]: D07832078F: sender non-delivery notification: D4BE62078D Jan 21 19:00:11 mail postfix/qmgr[5929]: D07832078F: removed So, my first question is why is it trying to deliver it locally? It should be sending it to the alias me@domain.com as defined in the virtual file. Second, in the log files I see the following: Jan 21 19:00:11 mail postfix/cleanup[22582]: D4BE62078D: message-id=<20070122000011.D4BE62078D@mail.domain.com> Jan 21 19:00:11 mail postfix/bounce[22585]: D07832078F: sender non-delivery notification: D4BE62078D Jan 21 19:00:11 mail postfix/qmgr[5929]: D4BE62078D: from=<>, size=2674, nrcpt=1 (queue active) Jan 21 19:00:13 mail postfix/smtp[22586]: D4BE62078D: to=, orig_to=, relay=1.2.3.4[1.2.3.4]:25, delay=1.2, delays=0.01/0/0.18/1, dsn=2.0.0, status=sent (250 2.0.0 l0M00Cju028485 Message accepted for delivery) Jan 21 19:00:13 mail postfix/qmgr[5929]: D4BE62078D: removed Why is it trying to send this message to me@domain.com through the relay server 1.2.3.4 when it knows (via transport file) that this domain should be sent to w.x.y.z? I've done this same setup on a 10.1 box previously and it is working just fine. Any ideas what I'm missing? I'm just confused. Thanks for any suggestions. Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Sandy Drobic

22 Jan 22 Jan

17:15

Brian Blater wrote:

...

I have a 10.2 box running as a postfix mail gateway for a couple of domains I have. This box is running spamassassin, maia mailguard and clamav. Local mail is disabled on this machine. I've setup postfix so that myhostname = mail.domain.com relay_domains = domain.com anotherdomain.com mydomain = domain.com relayhost = 1.2.3.4

Addresses in Postfix are qualified with the value of $myorigin, and the default value of $myorigin is $myhostname: # postconf -d myorigin myorigin = $myhostname postconf -e "myorigin = $mydomain" postfix reload should solve your problem.

...

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

The virtual file has root me@domain.com vscan me@domain.com

Don't do that! do not use unqualified addresses in virtual. Because virtual is applied to ALL mails (also outgoing mails) any mail sent to root@not-your-domain.com will be rewritten to me@domain.com!

...

Second, in the log files I see the following: Jan 21 19:00:11 mail postfix/cleanup[22582]: D4BE62078D: message-id=<20070122000011.D4BE62078D@mail.domain.com> Jan 21 19:00:11 mail postfix/bounce[22585]: D07832078F: sender non-delivery notification: D4BE62078D Jan 21 19:00:11 mail postfix/qmgr[5929]: D4BE62078D: from=<>, size=2674, nrcpt=1 (queue active) Jan 21 19:00:13 mail postfix/smtp[22586]: D4BE62078D: to=, orig_to=, relay=1.2.3.4[1.2.3.4]:25, delay=1.2, delays=0.01/0/0.18/1, dsn=2.0.0, status=sent (250 2.0.0 l0M00Cju028485 Message accepted for delivery) Jan 21 19:00:13 mail postfix/qmgr[5929]: D4BE62078D: removed

Why is it trying to send this message to me@domain.com through the relay server 1.2.3.4 when it knows (via transport file) that this domain should be sent to w.x.y.z?

I've done this same setup on a 10.1 box previously and it is working just fine. Any ideas what I'm missing? I'm just confused.

Can't help you here with incomplete und obfuscated data. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Brian Blater

20:23

On 1/22/07, Sandy Drobic wrote:

...

Brian Blater wrote:

...
I have a 10.2 box running as a postfix mail gateway for a couple of domains I have. This box is running spamassassin, maia mailguard and clamav. Local mail is disabled on this machine. I've setup postfix so that myhostname = mail.domain.com relay_domains = domain.com anotherdomain.com mydomain = domain.com relayhost = 1.2.3.4

Addresses in Postfix are qualified with the value of $myorigin, and the default value of $myorigin is $myhostname:

# postconf -d myorigin myorigin = $myhostname

postconf -e "myorigin = $mydomain" postfix reload

should solve your problem.

Thanks, Sandy. This helps clarify the situation. As for the stuff below. I'm not sure what is happening. It doesn't appear to be reading the transport file at all and other things are not behaving normally. I'm going to rebuild (it's a test box right now anyways.)

...

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

The virtual file has root me@domain.com vscan me@domain.com

Don't do that! do not use unqualified addresses in virtual. Because virtual is applied to ALL mails (also outgoing mails) any mail sent to root@not-your-domain.com will be rewritten to me@domain.com!

Thanks, fixed. All aliases in virtual will be FQ now.

...

...
Second, in the log files I see the following: Jan 21 19:00:11 mail postfix/cleanup[22582]: D4BE62078D: message-id=<20070122000011.D4BE62078D@mail.domain.com> Jan 21 19:00:11 mail postfix/bounce[22585]: D07832078F: sender non-delivery notification: D4BE62078D Jan 21 19:00:11 mail postfix/qmgr[5929]: D4BE62078D: from=<>, size=2674, nrcpt=1 (queue active) Jan 21 19:00:13 mail postfix/smtp[22586]: D4BE62078D: to=, orig_to=, relay=1.2.3.4[1.2.3.4]:25, delay=1.2, delays=0.01/0/0.18/1, dsn=2.0.0, status=sent (250 2.0.0 l0M00Cju028485 Message accepted for delivery) Jan 21 19:00:13 mail postfix/qmgr[5929]: D4BE62078D: removed

Why is it trying to send this message to me@domain.com through the relay server 1.2.3.4 when it knows (via transport file) that this domain should be sent to w.x.y.z?

I've done this same setup on a 10.1 box previously and it is working just fine. Any ideas what I'm missing? I'm just confused.

Can't help you here with incomplete und obfuscated data.

After the rebuild if this comes up again I will post unmangled log files for you to see. Thanks again for setting me straight. Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sandy Drobic

21:02

Brian Blater wrote:

...

As for the stuff below. I'm not sure what is happening. It doesn't appear to be reading the transport file at all and other things are not behaving normally. I'm going to rebuild (it's a test box right now anyways.)

Hey, this is not Windows!

...

...
...
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). Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Brian Blater

21:22

On 1/22/07, Sandy Drobic wrote:

...

Brian Blater wrote:

...
As for the stuff below. I'm not sure what is happening. It doesn't appear to be reading the transport file at all and other things are not behaving normally. I'm going to rebuild (it's a test box right now anyways.)

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.

...

...
...
...
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? 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 = ? Thanks, Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sandy Drobic

22:24

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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan

22:34

* Sandy Drobic [01-22-07 17:26]:

...

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.

16:21 wahoo:~ > ls -la /var/adm/SuSEconfig/md5/etc/postfix/ total 16 drwxr-xr-x 2 root root 4096 2007-01-06 14:37 . drwxr-xr-x 6 root root 4096 2007-01-06 14:37 .. -rw-r--r-- 1 root root 36 2007-01-06 14:37 main.cf -rw-r--r-- 1 root root 36 2007-01-06 14:37 master.cf rm main.cf and/or master.cf run SuSEConfig --module postfix which will regenerate the md5 checksums -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sandy Drobic

23:00

Patrick Shanahan wrote:

...

* Sandy Drobic [01-22-07 17:26]:

...
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.

16:21 wahoo:~ > ls -la /var/adm/SuSEconfig/md5/etc/postfix/ total 16 drwxr-xr-x 2 root root 4096 2007-01-06 14:37 . drwxr-xr-x 6 root root 4096 2007-01-06 14:37 .. -rw-r--r-- 1 root root 36 2007-01-06 14:37 main.cf -rw-r--r-- 1 root root 36 2007-01-06 14:37 master.cf

rm main.cf and/or master.cf

run SuSEConfig --module postfix

which will regenerate the md5 checksums

So, does this mean that Yast will try to modify Postfix again with each run of SuSEConfig or not? If I recall correctly there was a setting somewhere in yast -> system -> sysconfig editor, where you could tell yast not to touch Postfix. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan

23:14

* Sandy Drobic [01-22-07 18:02]:

...

So, does this mean that Yast will try to modify Postfix again with each run of SuSEConfig or not?

aiui, SuSEconfig checks the md5 checksum and does not modify if they match. rm'ing the md5 checksum causes SuSEconfig to generate a new sum matching the 'changed' 'original' config file. This satisfies SuSEconfig.

...

If I recall correctly there was a setting somewhere in yast -> system -> sysconfig editor, where you could tell yast not to touch Postfix.

I just searched YaST2 and did not find that option ???? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

23 Jan 23 Jan

00:33

Sandy Drobic wrote:

...

If I recall correctly there was a setting somewhere in yast -> system -> sysconfig editor, where you could tell yast not to touch Postfix.

Yast>System>/etc/sysconfig Editor>Network>Mail>General>MAIL_CREATE_CONFIG (yes,no) -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

09:51

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-01-22 at 23:24 +0100, Sandy Drobic wrote:

...

...
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.

You can add new setting to the yast part; ie, defining "POSTFIX_ADD_MYORIGIN = ..." in /etc/sysconfig/postfix will make Yast add a "myorigin = ..." line to postfix's main.cf file. I think this change can also be made from inside Yast somewhere. Using "POSTFIX_ADD_...whatever" you can create new settings, for variables Yast did not initially consider. Also, just by editing /etc/postfix/main.cf or master.cf files, yast will refuse to touch them ever again (or SuSEconfig, for that matter). In /var/adm/SuSEconfig/md5/etc/postfix/* it stores the calculated md5 values of the original files: if they are different from the actual value, it will leave your files alone. Meaning, that the instant the admin takes over postfix Yast will not modify your files and you can forget that danger. This technique applies to all or most of the configuration files Yast handles. SuSE has been doing this for years: I have md5 files there dating from 2003 ;-) There are also a few settings common to postfix or sendmail in "/etc/sysconfig/mail". One of them is "MAIL_CREATE_CONFIG". If you set it to no, Yast will not even try to create or modify the mail configuration; but I find easier to let Yast create an initial sensible configuration, then tailor it to my liking, than starting from scratch. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFtdqQtTMYHG2NR9URAtvAAJ9tg+nx+Bp+Q+kRXKOWOQGt0m6pfwCfaQvE TPFf5nZ7Hck2LRnkXnlsVQk= =0S6p -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sandy Drobic

10:53

Carlos E. R. wrote:

...

...
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.

...

There are also a few settings common to postfix or sendmail in "/etc/sysconfig/mail". One of them is "MAIL_CREATE_CONFIG". If you set it to no, Yast will not even try to create or modify the mail configuration; but I find easier to let Yast create an initial sensible configuration, then tailor it to my liking, than starting from scratch.

Very nice to know. I will probably set this as the very first thing during every installation. When I tried to do the initial configuration with yast I became confused and couldn't relate the dialogues with the settings I wanted to use, so I broke off and did everything manually again. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

15:43

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-01-23 at 11:53 +0100, Sandy Drobic wrote:

...

...
There are also a few settings common to postfix or sendmail in "/etc/sysconfig/mail". One of them is "MAIL_CREATE_CONFIG". If you set it to no, Yast will not even try to create or modify the mail configuration; but I find easier to let Yast create an initial sensible configuration, then tailor it to my liking, than starting from scratch.

Very nice to know. I will probably set this as the very first thing during every installation. When I tried to do the initial configuration with yast I became confused and couldn't relate the dialogues with the settings I wanted to use, so I broke off and did everything manually again.

Ha! Enter, enter, enter.... be done. X-) You know too much :-P - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFti0StTMYHG2NR9URAqADAJ9xMkV2IUR67e1EObOjfLWgdN0B2gCfT8je VhAIcnQmFM6QkH2d8p8ZoyU= =vPRw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris (NTM)

00:36

Brian Blater wrote:

...

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 = ? IIANM, yes. That is the acceptable way to have Yast configure a customized (meaning not normally set by Yast as installed from SUSE) setting. BTW, if you do an update, these changes are not deleted.

-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dean.Maguire＠L-3com.com

22 Jan 22 Jan