Re: [opensuse] Help - Update from 10.3 > 11.0 broke postfix
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.1005040055340.26376@nimrodel.valinor> El 2010-05-03 a las 17:44 -0500, Jim Flanagan escribió:
On Mon, May 3, 2010 at 1:37 PM, Carlos E. R. <> wrote:
Please reply on the list, so that others can comment.
Are you aware that 11.0 is going to be out of support in about two months? I hope you did not buy that DVD just now, because the currently sold one should be 11.2.
Yes I do know. I am updating this server one step at a time. Will probably go to 11.1 staying with KDE3. I don't think this old box can handle KDE4 with the plasma stuff. I bought the 11.0 when it was released.
Just type "date" as root on an xterm, and see if the timezone and hour/date is correct.
typing date shows system time to be what it shows on my desktop, i.e. correct local time.
If you leave the 000 part out, google finds many entries.
I'll look for more there, thanks.
Read Sandy Drobic comment, he's usually right when postfix is concerned :-)
That's output from SuSEconfig script. You can run it manually on an xterm as root and check. It is related to the script managing or not the postfix configuration because it was changed manually at some time.
Haven't run that yet. Will try it after I attempt a few other corrections first.
SuSEconfig will not change things unless you change the configuration in /etc/sysconfig first. It simply applies your changes. - -- Saludos Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkvfVl0ACgkQtTMYHG2NR9WJowCfZWGfGDj5uazDZ5caXisVsKKL fvAAnRU0H05TAyxCLvFuVW4jko8lOghk =b3ZI -----END PGP SIGNATURE-----
On Mon, May 3, 2010 at 6:03 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LSU.2.00.1005040055340.26376@nimrodel.valinor>
El 2010-05-03 a las 17:44 -0500, Jim Flanagan escribió:
On Mon, May 3, 2010 at 1:37 PM, Carlos E. R. <> wrote:
Please reply on the list, so that others can comment.
Sorry, I realized I did that just after I sent it to you. I'm just getting used to the gmail web interface. I did re-post this to the list, sorry again, these crossed in route. Thanks for the help. Read Sandy Drobic comment, he's usually right when postfix is concerned :-)
SuSEconfig will not change things unless you change the configuration in /etc/sysconfig first. It simply applies your changes.
Ok understood. That may fix things. I'll wait a bit first though to see what Sandy might come up with. Saludos, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, May 3, 2010 at 6:03 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
That's output from SuSEconfig script. You can run it manually on an xterm as root and check. It is related to the script managing or not the postfix configuration because it was changed manually at some time.
Haven't run that yet. Will try it after I attempt a few other corrections first.
SuSEconfig will not change things unless you change the configuration in /etc/sysconfig first. It simply applies your changes.
I ran SuSEconfig which returned the following (partial) Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING *** The two original errors are still persistent in mail log. Some google results have other looking in /etc/services to resolve similar issues, but they don't seem to be related to smtps, but other issues, with the same error message. One said to set the time zone for postfix there, but I did not follow that explanation. Is there a way to set, or reset the postfix time zone. It is 5 hours ahead of my local time, which is the difference between my local time DST and GMT. Thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-04 04:14, Jim Flanagan wrote:
On Mon, May 3, 2010 at 6:03 PM, Carlos E. R. <> wrote:
[sent later]
I ran SuSEconfig which returned the following (partial)
Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING ***
The two original errors are still persistent in mail log.
Well, that means that the "new" configuration was not applied, but rather, that you have the same postfix files you had in your previous (10.3?) install. Which means that, if there were changes in how things are done in postfix, you get a problem. Or maybe not. The way SuSEconfig works is, that it reads the configuration in /etc/sysconfig/postfix (and the rest, but we don't care now) and generates new files in /etc/postfix. It also stores a md5 checksum in /var/adm/SuSEconfig/md5/etc/postfix/* of what it does, so that if you (or something) changes postfix configuration, SuSEconfig (and thus YaST) will from then on refuse to change postfix. This is for your safety, so that you can manually configure postfix without fear of YaST destroying your changes. But it also means that in case of system updates, the config (your config) is not updated, you have to do it manually. What I do sometimes is that I make a backup of postfix config files, and create a new one using YaST (you have to delete the config and suseconfig backups in /etc/postfix, or perhaps delete the md5 files, or mv the config*suseconfig files to primaries), and then manually reapply my own configs after reading manuals again.
Is there a way to set, or reset the postfix time zone. It is 5 hours ahead of my local time, which is the difference between my local time DST and GMT.
There is no such thing as postfix time zone. Perhaps what you see is that postfix is logging things in UTC. Can you post examples? - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvfv9QACgkQja8UbcUWM1xWlwD/VKu87KWTc428ux0tBFLrN/RJ JtxNKS6mOa0bTaj+GPcA/iTFHqMmFX6R6s5l36/BQMndU5s3i+yqtMiGd63nvq2R =1JhS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, May 4, 2010 at 1:33 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2010-05-04 04:14, Jim Flanagan wrote:
On Mon, May 3, 2010 at 6:03 PM, Carlos E. R. <> wrote:
[sent later]
I ran SuSEconfig which returned the following (partial)
Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING ***
The two original errors are still persistent in mail log.
Well, that means that the "new" configuration was not applied, but rather, that you have the same postfix files you had in your previous (10.3?) install. Which means that, if there were changes in how things are done in postfix, you get a problem. Or maybe not.
The way SuSEconfig works is, that it reads the configuration in /etc/sysconfig/postfix (and the rest, but we don't care now) and generates new files in /etc/postfix. It also stores a md5 checksum in /var/adm/SuSEconfig/md5/etc/postfix/* of what it does, so that if you (or something) changes postfix configuration, SuSEconfig (and thus YaST) will from then on refuse to change postfix. This is for your safety, so that you can manually configure postfix without fear of YaST destroying your changes.
But it also means that in case of system updates, the config (your config) is not updated, you have to do it manually.
What I do sometimes is that I make a backup of postfix config files, and create a new one using YaST (you have to delete the config and suseconfig backups in /etc/postfix, or perhaps delete the md5 files, or mv the config*suseconfig files to primaries), and then manually reapply my own configs after reading manuals again.
Understood. Thanks. In the case of postfix, I have tried numerous times to set main.cf up using YaST, but never got even the basics to work. Add to that small adjustments, such as allowing or blocking certain clients that are producing errors, for example, and I don't see how to successfully use YaST to configure postfix. This most probably due to my ignorance or impatience. But I do see the advantage of using YaST whenever possible to make these types of adjustments.
Is there a way to set, or reset the postfix time zone. It is 5 hours ahead of my local time, which is the difference between my local time DST and GMT.
There is no such thing as postfix time zone. Perhaps what you see is that postfix is logging things in UTC. Can you post examples?
It looks like this is the case. I never noticed before (doh...) that some postfix log entries are shown in UTC. In any case it is working now. See my other post in reply to Sandy. Hopefully I can leave the settings as they are now, or perhaps Sandy will have another adjustment or two to recommend. But for now things are working seemingly OK. Now I can get back to my own email server and usual client. This gmail web interface has some interesting subtleties that for me make using it for a mailing list such as this one, difficult. Many thanks for your help. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-05 06:25, Jim Flanagan wrote:
On Tue, May 4, 2010 at 1:33 AM, Carlos E. R. <> wrote:
[Sent later] [suseconfig, yast]
Understood. Thanks. In the case of postfix, I have tried numerous times to set main.cf up using YaST, but never got even the basics to work. Add to that small adjustments, such as allowing or blocking certain clients that are producing errors, for example, and I don't see how to successfully use YaST to configure postfix. This most probably due to my ignorance or impatience. But I do see the advantage of using YaST whenever possible to make these types of adjustments.
It is possible that you can not adjust everything in yast. I simply get it working, then adjust things manually in postfix. But the starting point is a working, simple, postfix install. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvhDVUACgkQja8UbcUWM1ySTAD/UuekKCIUejOVU3QgKab1ZY0v R+EJnAkcsmgwCXMqcEoA/1uiDmfX1jyVxTpL7Hx5VAdEMTR3guPwt6C39nJ9SoIm =Vc7V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
It is possible that you can not adjust everything in yast. I simply get it working, then adjust things manually in postfix. But the starting point is a working, simple, postfix install.
Anything that is related to main.cf can be adjusted/created via /etc/sysconfig/postfix and running Suseconfig -module postfix. No need to manually adjust the main.cf Unfortunately the same is not true for master.cf Togan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/03/2010 06:03 PM, Carlos E. R. wrote:
Read Sandy Drobic comment, he's usually right when postfix is concerned :-)
+1 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
David C. Rankin -
Jim Flanagan -
Togan Muftuoglu