[opensuse] Postfix Qwerkiness
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=
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
On 1/22/07, Sandy Drobic
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
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
On 1/22/07, Sandy Drobic
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
Have installed 10.2 on a Dell Precision 690 which has a Qlogic 2GB HBA installed. During the installation process the controller is recognised and the following drivers are installed: qla23xx and qla2300. After startup, Yast.Hardware.DiskControllers shows Qlogic QLA2312 Fibre Channel Controller Yast.Hardware.Hardware Information.PCI shows 2 QLA2312 Fibre Channel Adapters However, Yast.System.Partioner does not recognise that storage is attached. Downloaded SanSurfer Linux Driver Installer (qlafc-linux-8.01.06-1install.tgz) from http://support.qlogic.com/support/os_detail.asp?productid=255&osid=126 Ran install as per instructions, resulting in the following output: <BOF> #*********************************************************# # SANsurfer Driver Installer for Linux # # Installer Version: 1.01.00pre14 # #*********************************************************# Kernel version: 2.6.18.2-34-bigsmp Distribution: openSUSE 10.2 (i586) Found QLogic Fibre Channel Adapter in the system 1. ISP2312 Installation will begin for following driver 1. qla2xxx version: v8.01.06 Preparing... ################################################## qla2xxx ################################################## QLA2XXX -- Building the qla2xxx driver, please wait... (bad exit status)make -j5 -C /lib/modules/2.6.18.2-34-bigsmp/source O=/lib/modules/2.6.18.2-34-bigsmp/build M=/usr/src/qlogic/v8.01.06-1/qla2xxx-8.01.06 modules >& /usr/src/qlogic/v8.01.06-1/build.log failed to execute QLA2XXX -- Installing the qla2xxx modules to /lib/modules/2.6.18.2-34-bigsmp/kernel/drivers/scsi/qla2xxx/... install: cannot stat `*.ko': No such file or directory Setting up QLogic HBA API library... Please make sure the /usr/lib/libqlsdm.so file is not in use. Installing ia32 api binary. Done. Unloading any loaded drivers Loading module qla2xxx_conf version: v8.01.06.... FATAL: Module qla2xxx_conf not found. Module qla2xxx_conf load failed Loading module qla2xxx version: v8.01.06.... FATAL: Module qla2xxx_conf not found. FATAL: Error inserting qla2xxx (/lib/modules/2.6.18.2-34-bigsmp/kernel/drivers/scsi/qla2xxx/qla2xxx.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error running install command for qla2xxx Module qla2xxx load failed Loading module qla2300 version: v8.01.06.... Module qla2300 load failed Unable to load new driver. Skipping persisten binding... Please use ./qlinstall -p -u to update persistent binding manually Saved copy of /etc/sysconfig/kernel as /usr/src/qlogic/v8.01.06-1/backup/kernel-2.6.18.2-34-bigsmp-011907-140809.bak Saved copy of /etc/modprobe.conf.local as /usr/src/qlogic/v8.01.06-1/backup/modprobe.conf.local-2.6.18.2-34-bigsmp-011907-140809.bak Saved copy of /boot/initrd-2.6.18.2-34-bigsmp as /usr/src/qlogic/v8.01.06-1/backup/initrd-2.6.18.2-34-bigsmp-011907-140809.bak QLA2XXX -- Rebuilding ramdisk image... Ramdisk created. Reloading the QLogic FC HBA drivers.... qla2300 module is not loaded Loading module qla2xxx_conf version: v8.01.06.... FATAL: Module qla2xxx_conf not found. Module qla2xxx_conf load failed Loading module qla2xxx version: v8.01.06.... FATAL: Module qla2xxx_conf not found. FATAL: Error inserting qla2xxx (/lib/modules/2.6.18.2-34-bigsmp/kernel/drivers/scsi/qla2xxx/qla2xxx.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error running install command for qla2xxx Module qla2xxx load failed Loading module qla2300 version: v8.01.06.... Module qla2300 load failed ERROR: qla2xxx installation failed <EOF> Downloaded source tarball for driver (qla2xxx-v8.01.06-dist.tgz) from http://support.qlogic.com/support/EULATemplate/Template.aspx?TemplateID=1&path=http://download.qlogic.com/drivers/48933/qla2xxx-v8.01.06-dist.tgz. Ran install as per instructions, resulting in the following output: <BOF> QLA2XXX -- Clean rebuild of the qla2xxx driver, please wait... make: Entering directory `/usr/src/linux-2.6.18.2-34' /usr/src/linux-2.6.18.2-34/scripts/Makefile.build:23: kbuild: /qlogic/qla2xxx-8.01.06/Makefile - Usage of host-progs is deprecated. Please replace with hostprogs-y! CC [M] /qlogic/qla2xxx-8.01.06/ql2100.o CC [M] /qlogic/qla2xxx-8.01.06/ql2100_fw.o CC [M] /qlogic/qla2xxx-8.01.06/ql2200.o CC [M] /qlogic/qla2xxx-8.01.06/ql2200_fw.o CC [M] /qlogic/qla2xxx-8.01.06/ql2300.o CC [M] /qlogic/qla2xxx-8.01.06/ql2300_fw.o CC [M] /qlogic/qla2xxx-8.01.06/ql2322.o CC [M] /qlogic/qla2xxx-8.01.06/ql2322_fw.o CC [M] /qlogic/qla2xxx-8.01.06/ql2400.o CC [M] /qlogic/qla2xxx-8.01.06/ql2400_fw.o CC [M] /qlogic/qla2xxx-8.01.06/qla_os.o CC [M] /qlogic/qla2xxx-8.01.06/qla_init.o CC [M] /qlogic/qla2xxx-8.01.06/qla_mbx.o CC [M] /qlogic/qla2xxx-8.01.06/qla_iocb.o CC [M] /qlogic/qla2xxx-8.01.06/qla_isr.o /qlogic/qla2xxx-8.01.06/qla_os.c: In function ƒ_~qla2x00_ioctl_error_recoveryƒ_T: /qlogic/qla2xxx-8.01.06/qla_os.c:5356: warning: unused variable ƒ_~flagsƒ_T /qlogic/qla2xxx-8.01.06/qla_os.c: In function ƒ_~qla2x00_cleanup_module_exitƒ_T: /qlogic/qla2xxx-8.01.06/qla_os.c:5392: error: implicit declaration of function ƒ_~inter_module_putƒ_T /qlogic/qla2xxx-8.01.06/qla_os.c: In function ƒ_~qla2x00_module_initƒ_T: /qlogic/qla2xxx-8.01.06/qla_os.c:5440: error: implicit declaration of function ƒ_~inter_module_get_requestƒ_T make[2]: *** [/qlogic/qla2xxx-8.01.06/qla_os.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [_module_/qlogic/qla2xxx-8.01.06] Error 2 make: *** [modules] Error 2 make: Leaving directory `/usr/src/linux-2.6.18.2-34' QLA2XXX -- Failed. <EOF> Any assistance in resolving this problem would be greatly appreciated. Cheers DeanM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
* Sandy Drobic
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
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
* Sandy Drobic
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
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
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
-----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
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
-----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
On 1/22/07, Sandy Drobic
Brian Blater wrote:
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'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.
Ok, the box was rebuilt last night and the transport file issues etc.
appear to be working correctly. So, let me go back to the issue above
and see if we can figure out what is happening here. When the maia
scripts run (as the vscan user) it tries to send an e-mail to vscan.
As can be seen in the log file below it changes the header from vscan
to vscan@mail.pure-energy.net with a relay of none. I have entries in
the virtual file as follows:
vscan@porsche.pure-energy.net bbl***@pure-energy.net
vscan@pure-energy.net bbl***@pure-energy.net
vscan@mail.pure-energy.net bbl***@pure-energy.net
How come postfix doesn't pick this up and send the file to my address?
Instead it tries to send it locally, but that is disabled. So, it then
sends the non-delivery notification to the vscan user and then
actually relays it to the correct virtual alias.
Any ideas on what I'm missing? Obviously I don't want any mail
delivered to this box since it is just a gateway. All mail should be
forwarded to the inside host to be delivered to a mailbox.
Jan 23 12:00:02 porsche postfix/pickup[6562]: 86755A3C3A: uid=65 from=<vscan>
Jan 23 12:00:02 porsche postfix/cleanup[6903]: 86755A3C3A:
message-id=<20070123170002.86755A3C3A@mail.pure-energy.net>
Jan 23 12:00:02 porsche postfix/qmgr[6563]: 86755A3C3A:
from=
Brian Blater wrote:
Can't help you here with incomplete und obfuscated data.
Ok, the box was rebuilt last night and the transport file issues etc. appear to be working correctly. So, let me go back to the issue above and see if we can figure out what is happening here. When the maia scripts run (as the vscan user) it tries to send an e-mail to vscan. As can be seen in the log file below it changes the header from vscan to vscan@mail.pure-energy.net with a relay of none. I have entries in the virtual file as follows:
vscan@porsche.pure-energy.net bbl***@pure-energy.net vscan@pure-energy.net bbl***@pure-energy.net vscan@mail.pure-energy.net bbl***@pure-energy.net
How come postfix doesn't pick this up and send the file to my address? Instead it tries to send it locally, but that is disabled. So, it then sends the non-delivery notification to the vscan user and then actually relays it to the correct virtual alias.
Any ideas on what I'm missing? Obviously I don't want any mail delivered to this box since it is just a gateway. All mail should be forwarded to the inside host to be delivered to a mailbox.
Jan 23 12:00:02 porsche postfix/pickup[6562]: 86755A3C3A: uid=65 from=<vscan> Jan 23 12:00:02 porsche postfix/cleanup[6903]: 86755A3C3A: message-id=<20070123170002.86755A3C3A@mail.pure-energy.net> Jan 23 12:00:02 porsche postfix/qmgr[6563]: 86755A3C3A: from=
, size=604, nrcpt=1 (queue active) Jan 23 12:00:02 porsche postfix/error[6907]: 86755A3C3A: to= , orig_to=<vscan>, relay=none, delay=0.37, delays=0.26/0.05/0/0.06, dsn=5.0.0, status=bounced (local mail delivery is disabled)
You should check if the domain mail.pure-energy.net is included in $mydestination. Please keep in mind that not to set a parameter does NOT mean the parameter will be empty. It means that the default value will be used. # postconf -d mydestination mydestination = $myhostname, localhost.$mydomain, localhost What does "postconf mydestination" say? Do you get warnings in your logfile? egrep 'fatal|panic|error|warning' /var/log/mail 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
On 1/23/07, Sandy Drobic
Brian Blater wrote: You should check if the domain mail.pure-energy.net is included in $mydestination. Please keep in mind that not to set a parameter does NOT mean the parameter will be empty. It means that the default value will be used.
# postconf -d mydestination mydestination = $myhostname, localhost.$mydomain, localhost
What does "postconf mydestination" say?
Do you get warnings in your logfile? egrep 'fatal|panic|error|warning' /var/log/mail
This is what postconf shows:
porsche:~ # postconf -n mydestination
mydestination = $myhostname, localhost.$mydomain
porsche:~ # postconf -n myhostname
myhostname = mail.pure-energy.net
The egrep of /var/log/mail only shows the bounces because the local
delivery failed error:
Jan 23 15:00:09 porsche postfix/error[7763]: 4AF0AA3C36:
to=
Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: Brian Blater wrote: You should check if the domain mail.pure-energy.net is included in $mydestination. Please keep in mind that not to set a parameter does NOT mean the parameter will be empty. It means that the default value will be used.
# postconf -d mydestination mydestination = $myhostname, localhost.$mydomain, localhost
What does "postconf mydestination" say?
Do you get warnings in your logfile? egrep 'fatal|panic|error|warning' /var/log/mail
This is what postconf shows: porsche:~ # postconf -n mydestination mydestination = $myhostname, localhost.$mydomain porsche:~ # postconf -n myhostname myhostname = mail.pure-energy.net
The egrep of /var/log/mail only shows the bounces because the local delivery failed error: Jan 23 15:00:09 porsche postfix/error[7763]: 4AF0AA3C36: to=
, orig_to=<vscan>, relay=none, delay=0.17, delays=0.16/0/0/0.01, dsn=5.0.0, status=bounced (local mail delivery is disabled)
In that case set $mydestination to an empty value: postconf -e "mydestination = " If mail.pure-energy.net is a relay_domain, set up the relay_recipient_maps with the table of valid recipient addresses. main.cf: relay_domains = mail.pure-energy.net relay_recipient_maps = hash:/etc/postfix/relay_recipients transport_maps = hash:/etc/postfix/transport /etc/postfix/relay_recipients: vscan@mail.pure-energy.net OK /etc/postfix/transport: mail.pure-energy.net relay:[1.2.3.4] postmap /etc/postfix/relay_recipients postmap /etc/postfix/transport postfix reload Then send another testmail, it should be sent to the server/ip address in /etc/postfix/transport 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
On 1/23/07, Sandy Drobic
Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: In that case set $mydestination to an empty value: postconf -e "mydestination = "
If mail.pure-energy.net is a relay_domain, set up the relay_recipient_maps with the table of valid recipient addresses.
main.cf: relay_domains = mail.pure-energy.net relay_recipient_maps = hash:/etc/postfix/relay_recipients transport_maps = hash:/etc/postfix/transport
/etc/postfix/relay_recipients: vscan@mail.pure-energy.net OK
/etc/postfix/transport: mail.pure-energy.net relay:[1.2.3.4]
postmap /etc/postfix/relay_recipients postmap /etc/postfix/transport postfix reload
Then send another testmail, it should be sent to the server/ip address in /etc/postfix/transport
Thanks for your help on this. Bear with me as I ask a few questions to get a better understanding. mail.pure-energy.net is the hostname. I already have pure-energy.net setup as a relay_domain. In the virtual file I have an alias for vscan@mail.pure-energy.net to bbl***@pure-energy.net. (Basically anything to "user"@mail.pure-energy.net should be aliased to something@pure-energy.net). so, how can I tell postfix that vscan@mail.pure-energy.net = vscan@pure-energy.net and to look in the virtual file to see that vscan@pure-energy.net = bbl***@pure-energy.net (or even that vscan@mail.pure-energy.net = bbl***@pure-energy.net? Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-01-23 at 17:40 -0500, Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: snip Thanks for your help on this. Bear with me as I ask a few questions to get a better understanding. mail.pure-energy.net is the hostname. I already have pure-energy.net setup as a relay_domain. In the virtual file I have an alias for vscan@mail.pure-energy.net to bbl***@pure-energy.net. (Basically anything to "user"@mail.pure-energy.net should be aliased to something@pure-energy.net). so, how can I tell postfix that vscan@mail.pure-energy.net = vscan@pure-energy.net and to look in the virtual file to see that vscan@pure-energy.net = bbl***@pure-energy.net (or even that vscan@mail.pure-energy.net = bbl***@pure-energy.net?
pure-energy.com should have the "A" record and mail.pure-energy.com can be a CNAME to it (alias) so that they both use the same IP address. You also need to make sure you have an MX record to handle the mail. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: In that case set $mydestination to an empty value: postconf -e "mydestination = "
If mail.pure-energy.net is a relay_domain, set up the relay_recipient_maps with the table of valid recipient addresses.
main.cf: relay_domains = mail.pure-energy.net relay_recipient_maps = hash:/etc/postfix/relay_recipients transport_maps = hash:/etc/postfix/transport
/etc/postfix/relay_recipients: vscan@mail.pure-energy.net OK
/etc/postfix/transport: mail.pure-energy.net relay:[1.2.3.4]
postmap /etc/postfix/relay_recipients postmap /etc/postfix/transport postfix reload
Then send another testmail, it should be sent to the server/ip address in /etc/postfix/transport
Thanks for your help on this. Bear with me as I ask a few questions to get a better understanding. mail.pure-energy.net is the hostname. I already have pure-energy.net setup as a relay_domain. In the virtual file I have an alias for vscan@mail.pure-energy.net to bbl***@pure-energy.net. (Basically anything to "user"@mail.pure-energy.net should be aliased to something@pure-energy.net). so, how can I tell postfix that vscan@mail.pure-energy.net = vscan@pure-energy.net and to look in the virtual file to see that vscan@pure-energy.net = bbl***@pure-energy.net (or even that vscan@mail.pure-energy.net = bbl***@pure-energy.net?
- do you actually want mail from/to the domain mail.pure-energy.net? Otherwise it it much simpler to just tell Postfix not to accept or generate mails to/from that domain. main.cf: mydomain = pure-energy.net myorigin = $mydomain relay_domains = pure-energy.net relay_recipient_maps = hash:/etc/postfix/relay_recipients transport_maps = hash:/etc/postfix/transport /etc/postfix/relay_recipients: vscan@pure-energy.net OK /etc/postfix/transport: pure-energy.net relay:[1.2.3.4] If you do want to rewrite addresses from one domain to another you can't do that with wildcard aliasing. Well, technically you can, but wildcard aliasing destroys recipient validation, so you'll become a backscatter source. So you need to alias each address to another address in /etc/postfix/virtual. If neccessary, use a script to generate the file. On our Postfix gateway a script is extracting the valid recipients from our domino server via ldap every few minutes. 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
Kenneth Schneider wrote:
On Tue, 2007-01-23 at 17:40 -0500, Brian Blater wrote:
On 1/23/07, Sandy Drobic
wrote: snip Thanks for your help on this. Bear with me as I ask a few questions to get a better understanding. mail.pure-energy.net is the hostname. I already have pure-energy.net setup as a relay_domain. In the virtual file I have an alias for vscan@mail.pure-energy.net to bbl***@pure-energy.net. (Basically anything to "user"@mail.pure-energy.net should be aliased to something@pure-energy.net). so, how can I tell postfix that vscan@mail.pure-energy.net = vscan@pure-energy.net and to look in the virtual file to see that vscan@pure-energy.net = bbl***@pure-energy.net (or even that vscan@mail.pure-energy.net = bbl***@pure-energy.net? pure-energy.com should have the "A" record and mail.pure-energy.com can be a CNAME to it (alias) so that they both use the same IP address. You also need to make sure you have an MX record to handle the mail.
This has nothing to do with the question. The question was about address rewriting. pure-energy.NET does not need an a record, just an mx record. Only if a mx record does not exist the a record will be used to determine the transport for a mail. If neither a or mx record exists mails will be bounce with "unknown recipient domain". As a general rule, better do not use CNAME in maildomains. They must resolve to an mx or a record anyway, so it's just one more dns lookup for the client. Much more important for a sending mailserver is to have a matching reverse dns record that points back to the a record. Otherwise the server is logged as the name of the reverse dns record or as unknown. A lot of servers refuse to accept mails from servers that do not have a matching reverse dns record. 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
On 1/24/07, Sandy Drobic
Brian Blater wrote: - do you actually want mail from/to the domain mail.pure-energy.net? Otherwise it it much simpler to just tell Postfix not to accept or generate mails to/from that domain.
Correct - I don't want mail from mail.pure-energy.net. It should be pure-energy.net
main.cf: mydomain = pure-energy.net
Already set
myorigin = $mydomain
This was set to $myhostname. I can't change myorigin via YAST so I tried to add the myorigin=$mydomain via the /etc/sysconfig/postfix file and it doesn't like the variable reference ($mydomain). It just strips it and leaves myorigin blank. So, I have to explicitly set myorigin = pure-energy.net in this file unless there is a way to set it in YAST and from the previous discuss about this it is either manually edit the main.cf file and no longer make the changes using YAST or remove the MD5 file it generates after manually editing the file. For now, I'll stick with YAST, but I may go back to the manual edits of postfix (as I did many moons ago).
relay_domains = pure-energy.net relay_recipient_maps = hash:/etc/postfix/relay_recipients transport_maps = hash:/etc/postfix/transport
Already set this way.
/etc/postfix/relay_recipients: vscan@pure-energy.net OK
I don't want outside mail addresses to vscan so I have not added this to the relay_recipients file.
/etc/postfix/transport: pure-energy.net relay:[1.2.3.4]
This is setup using smtp: instead of relay: Should it be changed to relay? It sounds like relay is the recommended transport to internal systems. Changes made and now working. Thank you, Thank you, Thank you! You are the queen of postfix in my book. myorigin was the kicker. I have now researched the myorigin option and have a much better understanding of what it does. One thing I did notice is that after postfix appends the myorigin setting to the vscan user, it doesn't look it up in the virtual file and use the alias. It just sends it directly to the inside mail server listed in the transport for the relay domain. No big deal I can handle that by a quick alias on the inside mail server, just wondering why it works that way. Thanks again for all your help. I now feel a little more comfortable with postfix. Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 24 Jan, 2007 at 10:45:26 -0500, Brian Blater wrote:
On 1/24/07, Sandy Drobic
wrote:
<snip>
myorigin = $mydomain
This was set to $myhostname. I can't change myorigin via YAST so I tried to add the myorigin=$mydomain via the /etc/sysconfig/postfix file and it doesn't like the variable reference ($mydomain). It just strips it and leaves myorigin blank.
This should definitely work.
From /etc/sysconfig/postfix:
# POSTFIX_ADD_* # You may add any existing postfix parameter here. Just execute the # postconf command to get a complete list. You then have to uppercase # the parameter and prepend POSTFIX_ADD_. - so it *should* work like this; POSTFIX_ADD_MYORIGIN="$mydomain" I've done stuff like that a number of times (albeit with other parameters) and it's always worked as advertised. Usually I add comments above the parameter, so everything looks good in YaST (System -> /etc/sysconfig editor -> Mail -> Postfix) afterwards; ## Type: string ## Default: none # Short explanation about *why* I added $some_variable POSTFIX_ADD_SOME_VARIABLE="some value or other" HTH /Jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 1/24/07, Jon Clausen
<snip> This should definitely work.
From /etc/sysconfig/postfix:
# POSTFIX_ADD_* # You may add any existing postfix parameter here. Just execute the # postconf command to get a complete list. You then have to uppercase # the parameter and prepend POSTFIX_ADD_.
- so it *should* work like this;
POSTFIX_ADD_MYORIGIN="$mydomain"
I've done stuff like that a number of times (albeit with other parameters) and it's always worked as advertised. Usually I add comments above the parameter, so everything looks good in YaST (System -> /etc/sysconfig editor -> Mail -> Postfix) afterwards;
## Type: string ## Default: none # Short explanation about *why* I added $some_variable POSTFIX_ADD_SOME_VARIABLE="some value or other"
That is exactly what I thought. Howerver, when I executed it and then ran SuSEconfig, postconf myorigin showed myorigin = . I then saw in /var/log/mail - fatal: bad string length 0 < 1: myorigin = . I promptly changed the POSTFIX_ADD_MYORIGIN="domain.com" and it worked. This is a 10.2 box postfix-2.3.2-28 if that changes anything. Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 24 Jan, 2007 at 12:01:17 -0500, Brian Blater wrote:
On 1/24/07, Jon Clausen
wrote:
POSTFIX_ADD_MYORIGIN="$mydomain"
DOH! POSTFIX_ADD_MYORIGIN="\$mydomain"
That is exactly what I thought. Howerver, when I executed it and then ran SuSEconfig, postconf myorigin showed myorigin = . I then saw in /var/log/mail - fatal: bad string length 0 < 1: myorigin = . I promptly changed the POSTFIX_ADD_MYORIGIN="domain.com" and it worked.
This is a 10.2 box postfix-2.3.2-28 if that changes anything.
I wouldn't expect that to matter much in this context... HTH /Jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 1/25/07, Jon Clausen
On Wed, 24 Jan, 2007 at 12:01:17 -0500, Brian Blater wrote:
On 1/24/07, Jon Clausen
wrote: POSTFIX_ADD_MYORIGIN="$mydomain"
DOH!
POSTFIX_ADD_MYORIGIN="\$mydomain"
That would do the trick. Not much of a programmer myself, so little things like that are often overlooked. Thanks, Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 25 Jan, 2007 at 12:21:33 -0500, Brian Blater wrote:
On 1/25/07, Jon Clausen
wrote:
DOH!
POSTFIX_ADD_MYORIGIN="\$mydomain"
That would do the trick. Not much of a programmer myself, so little things like that are often overlooked.
Indeed :P
Thanks, Brian
:) /Jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Brian Blater
-
Carlos E. R.
-
Dean.Maguire@L-3com.com
-
Joe Morris (NTM)
-
Jon Clausen
-
Kenneth Schneider
-
Patrick Shanahan
-
Sandy Drobic