I have 4 Tw systems network locally and have main problems. Two, both desktops can send main to the network server, a fifth machine running openSUSE 13.1. The other two, both laptops (Tw) create "lost connection after EHLO from unknown" errors in /var/log/mail. With the exception of host names, <host-name>.wahoo.no-ip.org, all four /etc/postfix/maincf's are identical, and the problem is not firewall related as I tried with the firewall off getting the same error. I see nothing that helps on google and have lost myself in the postfix documentation. Does anyone have suggestion I can try? tks, ps: mostly just wanting to collect system logs in one place (mail). Also noticed that logrotate and logdigest were not installed nor are they when rsyslog is installed, nor is logrotate initiated on rsyslog install. journalctl is nice and not unhandy but a bear for any system with any amount of life-time. My i7 with ssd disks and raid 0 take FOREVER to parse thru any lengthy records. Not Good! -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2015 06:46 PM, Patrick Shanahan wrote:
I see nothing that helps on google and have lost myself in the postfix documentation.
Does anyone have suggestion I can try?
tks,
ps: mostly just wanting to collect system logs in one place (mail).
Its a long while since I had to do this, but I recall that Postfix has its own debugging and logging so you don't have to play games with journalctl, but do have to have a syslog of some form. The mail log is a higher level than the HELO/EHLO exchange but the Postfix internal logging level, when turned up to the right notch (no, not "11) will display that detail. BTDT once upon a time in a similar situation but don't recall the details. Policy on complex systems like Postix, with a gazillion options is to leave them alone once they work properly. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [01-10-15 11:18]:
On 01/09/2015 06:46 PM, Patrick Shanahan wrote:
I see nothing that helps on google and have lost myself in the postfix documentation.
Does anyone have suggestion I can try?
tks,
ps: mostly just wanting to collect system logs in one place (mail).
Its a long while since I had to do this, but I recall that Postfix has its own debugging and logging so you don't have to play games with journalctl, but do have to have a syslog of some form.
The mail log is a higher level than the HELO/EHLO exchange but the Postfix internal logging level, when turned up to the right notch (no, not "11) will display that detail. BTDT once upon a time in a similar situation but don't recall the details. Policy on complex systems like Postix, with a gazillion options is to leave them alone once they work properly.
I have had good luck with postfix and iirc, the only changes I have to make for local (non-server) systems is to add the hostname to main.cf. It works for two desktops but not for two laptops. :^( Thanks for mentioning debug within postfix. Will have a look at that and report. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-10 00:46, Patrick Shanahan wrote:
Does anyone have suggestion I can try?
About postfix debug logs. You need one of this, probably: debug_peer_level = 2 #debug_peer_level = 3 and then you define which conversations to log, if not all of them: debug_peer_list = mail.sourceforge.net #debug_peer_list = 127.0.0.1 Then, if the thing gets too complicated, there is a postfix help mail list.
ps: mostly just wanting to collect system logs in one place (mail). Also noticed that logrotate and logdigest were not installed nor are they when rsyslog is installed, nor is logrotate initiated on rsyslog install.
I think that 13.2 triggers logrotate via systemd timers. Besides syslog, there are other log files that need rotation, so even without syslog you need it.
journalctl is nice and not unhandy but a bear for any system with any amount of life-time. My i7 with ssd disks and raid 0 take FOREVER to parse thru any lengthy records. Not Good!
I thought it was fast with ssds. :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Patrick Shanahan <paka@opensuse.org> [01-09-15 18:48]:
I have 4 Tw systems network locally and have main problems. Two, both desktops can send main to the network server, a fifth machine running openSUSE 13.1. The other two, both laptops (Tw) create "lost connection after EHLO from unknown" errors in /var/log/mail. With the exception of host names, <host-name>.wahoo.no-ip.org, all four /etc/postfix/maincf's are identical, and the problem is not firewall related as I tried with the firewall off getting the same error.
I see nothing that helps on google and have lost myself in the postfix documentation.
Does anyone have suggestion I can try?
tks,
ps: mostly just wanting to collect system logs in one place (mail). Also noticed that logrotate and logdigest were not installed nor are they when rsyslog is installed, nor is logrotate initiated on rsyslog install.
journalctl is nice and not unhandy but a bear for any system with any amount of life-time. My i7 with ssd disks and raid 0 take FOREVER to parse thru any lengthy records. Not Good!
Solved: Ended up being an extra $mydomain in the "mydestination" line of /etc/postfix/main.cf. Go figger, and *difficult* to find :^(. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2015 03:19 PM, Patrick Shanahan wrote:
* Patrick Shanahan <paka@opensuse.org> [01-09-15 18:48]:
I have 4 Tw systems network locally and have main problems. Two, both desktops can send main to the network server, a fifth machine running openSUSE 13.1. The other two, both laptops (Tw) create "lost connection after EHLO from unknown" errors in /var/log/mail. With the exception of host names, <host-name>.wahoo.no-ip.org, all four /etc/postfix/maincf's are identical, and the problem is not firewall related as I tried with the firewall off getting the same error.
I see nothing that helps on google and have lost myself in the postfix documentation.
Does anyone have suggestion I can try?
tks,
ps: mostly just wanting to collect system logs in one place (mail). Also noticed that logrotate and logdigest were not installed nor are they when rsyslog is installed, nor is logrotate initiated on rsyslog install.
journalctl is nice and not unhandy but a bear for any system with any amount of life-time. My i7 with ssd disks and raid 0 take FOREVER to parse thru any lengthy records. Not Good!
Solved: Ended up being an extra $mydomain in the "mydestination" line of /etc/postfix/main.cf. Go figger, and *difficult* to find :^(.
If you think that is hard to find try looking for "extra" white space at the end of a line in a config file. New job, first time working with SCO and the box had an issue auto-mounting an nfs filesystem. After two months I stumbled accross the extra spaces, removed them all was well afterward. Sure made the boss and the admin of the Novell box happy. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jan 13, 2015 at 4:13 PM, Ken Schneider - openSUSE <suse-list3@bout-tyme.net> wrote:
If you think that is hard to find try looking for "extra" white space at the end of a line in a config file. New job, first time working with SCO and the box had an issue auto-mounting an nfs filesystem.
Customer had similar problem having something like extra character followed by backspace or cursor-left in the middle of string in fstab. When you simply dump it on screen (or used whatever pager was available at that time in that OS) string looked pretty normal. Fortunately I tend to use vi for it which immediately made it obvious. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/13/2015 05:13 AM, Ken Schneider - openSUSE wrote:
If you think that is hard to find try looking for "extra" white space at the end of a line in a config file. New job, first time working with SCO and the box had an issue auto-mounting an nfs filesystem. After two months I stumbled accross the extra spaces, removed them all was well afterward. Sure made the boss and the admin of the Novell box happy.
I've always appreciated editors that have an option to show white-space "characters". Its amazing to me that Kate does not support this, given that there are more than a few situations where white space matters in the linux world. I've been known to open such files with LibreOffice just to click on the Paragraph button which turns on white-space marks. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-13 21:46, John Andersen wrote:
On 01/13/2015 05:13 AM, Ken Schneider - openSUSE wrote:
If you think that is hard to find try looking for "extra" white space at the end of a line in a config file. New job, first time working with SCO and the box had an issue auto-mounting an nfs filesystem. After two months I stumbled accross the extra spaces, removed them all was well afterward. Sure made the boss and the admin of the Novell box happy.
I've always appreciated editors that have an option to show white-space "characters".
But that the parser of the config file, knowing how difficult is to find white space at the end of the line, has problems, may be also a bug.
Its amazing to me that Kate does not support this, given that there are more than a few situations where white space matters in the linux world.
On some editors you can see them by selecting several lines. They highlight till the actual endofline char, but others highlight the entire line (like kate), so they are not useful for this. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/13/2015 03:07 PM, Carlos E. R. wrote:
On 2015-01-13 21:46, John Andersen wrote:
On 01/13/2015 05:13 AM, Ken Schneider - openSUSE wrote:
If you think that is hard to find try looking for "extra" white space at the end of a line in a config file. New job, first time working with SCO and the box had an issue auto-mounting an nfs filesystem. After two months I stumbled accross the extra spaces, removed them all was well afterward. Sure made the boss and the admin of the Novell box happy.
I've always appreciated editors that have an option to show white-space "characters".
But that the parser of the config file, knowing how difficult is to find white space at the end of the line, has problems, may be also a bug.
Its amazing to me that Kate does not support this, given that there are more than a few situations where white space matters in the linux world.
On some editors you can see them by selecting several lines. They highlight till the actual endofline char, but others highlight the entire line (like kate), so they are not useful for this.
I files a bug report (wishlist item) on Kate. Pointed them at LibreOffice where they can steal the code. https://bugs.kde.org/show_bug.cgi?id=342811 If its like any of my other bug reports, it will get closed as obsolete with no action. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS1uHEACgkQv7M3G5+2DLIXqgCeJ26Yywu/X9j3/NplUAC75niG W80AnjJGNV4va2fUN/i94nMbPW+UsIJP =ino5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
John Andersen -
Ken Schneider - openSUSE -
Patrick Shanahan