[opensuse] fetchmail logging
Hello, I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. Setting syslog in fetchmailrc is not the successfull way to get fetchmail log to syslog, it only produces this message: "fetchmail[3045]: syslog and logfile options are both set, ignoring syslog, and logging to /var/ log/fetchmail". Probably it is caused by systemd-fetchmail-exec in /usr/lib because of the option "-L /var/log/fechtmail". Commenting it out makes fetchmail logging to syslog which can be read by "journalctl -u fetchmail.service". Because I am DAU (with some experience) I wonder whether next update will overwrite my setting. And, of course, it may be big nonsense what I am doing. Any hints? TIA best regards Will -- openSUSE Tumbleweed 20170503 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-08-17 13:02]:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. Setting syslog in fetchmailrc is not the successfull way to get fetchmail log to syslog, it only produces this message: "fetchmail[3045]: syslog and logfile options are both set, ignoring syslog, and logging to /var/ log/fetchmail".
Probably it is caused by systemd-fetchmail-exec in /usr/lib because of the option "-L /var/log/fechtmail". Commenting it out makes fetchmail logging to syslog which can be read by "journalctl -u fetchmail.service".
Because I am DAU (with some experience) I wonder whether next update will overwrite my setting. And, of course, it may be big nonsense what I am doing. Any hints?
I don't run fetchmail as a system service but as a user, only one user on my system/server, and do not use systemd to control it but start the daemon via ~.bashrc. I do get "Mon May 8 16:04:06 EDT 2017" lines in the log where I direct it in ~/.fetchmailrc set logfile "/home/paka/.fetchmail/fetchmail.log" set daemon XXX set postmaster XXX set no bouncemail set no spambounce fetchmail-6.3.26-18.1.x86_64 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Patrick, Am Montag, 8. Mai 2017, 22:14:14 CEST schrieb Patrick Shanahan:
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-08-17 13:02]:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. [...] I don't run fetchmail as a system service but as a user, only one user on my system/server, and do not use systemd to control it but start the daemon via ~.bashrc.
I do get "Mon May 8 16:04:06 EDT 2017" lines in the log where I direct it in ~/.fetchmailrc set logfile "/home/paka/.fetchmail/fetchmail.log" set daemon XXX set postmaster XXX set no bouncemail set no spambounce
fetchmail-6.3.26-18.1.x86_64
thank you for your answer. Unfortunately that will not help much. Mail is delivered to my local dovecot, the idea is to have it for the family, that is für multiple user accounts. Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 00:44, Wilhelm Boltz wrote:
Hello Patrick,
Am Montag, 8. Mai 2017, 22:14:14 CEST schrieb Patrick Shanahan:
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-08-17 13:02]:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. [...] I don't run fetchmail as a system service but as a user, only one user on my system/server, and do not use systemd to control it but start the daemon via ~.bashrc.
I do get "Mon May 8 16:04:06 EDT 2017" lines in the log where I direct it in ~/.fetchmailrc set logfile "/home/paka/.fetchmail/fetchmail.log" set daemon XXX set postmaster XXX set no bouncemail set no spambounce
fetchmail-6.3.26-18.1.x86_64
thank you for your answer.
Unfortunately that will not help much. Mail is delivered to my local dovecot, the idea is to have it for the family, that is für multiple user accounts.
It doesn't matter. You can have fetchmail run from a user, yet mail will be distributed to all users correctly. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 08/05/17 06:44 PM, Wilhelm Boltz wrote:
Unfortunately that will not help much. Mail is delivered to my local dovecot, the idea is to have it for the family, that is für multiple user accounts.
As Carlos points out, that doesn't matter. A stanza in the script might read POLL sitename WITH PROTOTCOL POP USER famelymember1 THERE IS familaymember1 HERE WITH PASSWORD gobbldygoop mda "/usr/bin/procmail -f %F -d %T"; You can then have procmail pipeline into dovecot. That's what I do. You can have similar stanzas for each familymember. You can have similar stanzas for each ISP site OR you can have a MDA that goes via Postfix into procmail into dovecot. There are many examples of this kind of thing on the Net-of-a-Billion-Lies -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Carlos, Am Dienstag, 9. Mai 2017, 03:45:44 CEST schrieb Carlos E. R.:
On 2017-05-09 00:44, Wilhelm Boltz wrote:
[...] Unfortunately that will not help much. Mail is delivered to my local dovecot, the idea is to have it for the family, that is für multiple user accounts. It doesn't matter. You can have fetchmail run from a user, yet mail will be distributed to all users correctly.
Am Dienstag, 9. Mai 2017, 13:36:53 CEST schrieb Anton Aylward:
On 08/05/17 06:44 PM, Wilhelm Boltz wrote:
Unfortunately that will not help much. Mail is delivered to my local dovecot, the idea is to have it for the family, that is für multiple user accounts. As Carlos points out, that doesn't matter.
A stanza in the script might read
POLL sitename WITH PROTOTCOL POP USER famelymember1 THERE IS familaymember1 HERE WITH PASSWORD gobbldygoop mda "/usr/bin/procmail -f %F -d %T";
You can then have procmail pipeline into dovecot. That's what I do.
You can have similar stanzas for each familymember. You can have similar stanzas for each ISP site
OR you can have a MDA that goes via Postfix into procmail into dovecot.
thank you very much for your hints. First I'll try what Per Jessen recommended, but I will keep your proposals in mind. Kind regards Will -- openSUSE Tumbleweed 20170503 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-08 19:02, Wilhelm Boltz wrote:
Hello,
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. Setting syslog in fetchmailrc is not the successfull way to get fetchmail log to syslog, it only produces this message: "fetchmail[3045]: syslog and logfile options are both set, ignoring syslog, and logging to /var/ log/fetchmail".
Probably it is caused by systemd-fetchmail-exec in /usr/lib because of the option "-L /var/log/fechtmail". Commenting it out makes fetchmail logging to syslog which can be read by "journalctl -u fetchmail.service".
Because I am DAU (with some experience) I wonder whether next update will overwrite my setting. And, of course, it may be big nonsense what I am doing. Any hints?
Your assumptions are all correct. No nonsense at all. IMO, it is a bug that fetchmail service is set to log to a file, the default should be syslog. But the default syslog is not syslog at all, but systemd journal. The journal will fill up fast to a huge size with mail reports. You can of course start a standard syslog daemon (I recomend rsyslog), and limit the size of the systemd journal. You can, however, override a service with your own service with a file of the same name under /etc/systemd/system/, and this will not be overwritten. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2017-05-08 19:02, Wilhelm Boltz wrote:
Hello,
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. Setting syslog in fetchmailrc is not the successfull way to get fetchmail log to syslog, it only produces this message: "fetchmail[3045]: syslog and logfile options are both set, ignoring syslog, and logging to /var/ log/fetchmail".
Probably it is caused by systemd-fetchmail-exec in /usr/lib because of the option "-L /var/log/fechtmail". Commenting it out makes fetchmail logging to syslog which can be read by "journalctl -u fetchmail.service".
Because I am DAU (with some experience) I wonder whether next update will overwrite my setting. And, of course, it may be big nonsense what I am doing. Any hints?
Your assumptions are all correct. No nonsense at all. IMO, it is a bug that fetchmail service is set to log to a file, the default should be syslog.
But the default syslog is not syslog at all, but systemd journal. The journal will fill up fast to a huge size with mail reports. You can of course start a standard syslog daemon (I recomend rsyslog), and limit the size of the systemd journal.
You can, however, override a service with your own service with a file of the same name under /etc/systemd/system/, and this will not be overwritten.
The problem is that '-L /var/log/fetchmail' is hardcoded in the startup script. You can write another startup script, and override that in /etc/systemd/system/fetchmail.d/, but that does seem a bit much. The right thing to do would be to fix that startup helper script and move '-L /var/log/fetchmail' into the options so it may be changed by way of /etc/sysconfig/fetchmail. Still - copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script create /etc/systemd/system/fetchmail.service.d/wilhelm.conf: ------- [Service] ExecStart= ExecStart=/usr/local/bin/wilhelm-fetchmail-exec --------- systemctl daemon-reload -- Per Jessen, Zürich (7.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Carlos, hello Per, Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
Carlos E. R. wrote:
On 2017-05-08 19:02, Wilhelm Boltz wrote:
Hello,
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving the date & time. Setting syslog in fetchmailrc is not the successfull way to get fetchmail log to syslog, it only produces this message: "fetchmail[3045]: syslog and logfile options are both set, ignoring syslog, and logging to /var/ log/fetchmail".
Probably it is caused by systemd-fetchmail-exec in /usr/lib because of the option "-L /var/log/fechtmail". Commenting it out makes fetchmail logging to syslog which can be read by "journalctl -u fetchmail.service".
Because I am DAU (with some experience) I wonder whether next update will overwrite my setting. And, of course, it may be big nonsense what I am doing. Any hints?
Your assumptions are all correct. No nonsense at all. IMO, it is a bug that fetchmail service is set to log to a file, the default should be syslog.
But the default syslog is not syslog at all, but systemd journal. The journal will fill up fast to a huge size with mail reports. You can of course start a standard syslog daemon (I recomend rsyslog), and limit the size of the systemd journal.
You can, however, override a service with your own service with a file of the same name under /etc/systemd/system/, and this will not be overwritten.
The problem is that '-L /var/log/fetchmail' is hardcoded in the startup script. You can write another startup script, and override that in /etc/systemd/system/fetchmail.d/, but that does seem a bit much. The right thing to do would be to fix that startup helper script and move '-L /var/log/fetchmail' into the options so it may be changed by way of /etc/sysconfig/fetchmail.
Still -
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script create /etc/systemd/system/fetchmail.service.d/wilhelm.conf:
------- [Service] ExecStart= ExecStart=/usr/local/bin/wilhelm-fetchmail-exec ---------
systemctl daemon-reload
I followed Per's recommendation and it works well. Thank you very much for your help. And I agree to your statement, Carlos, that a separate logfile shouldn't be the default setting. I know logging goes now to systemctl journal, and it may increase. Do you think a separate logfile will be much smaller than the additional space on systemctl journal? Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-09-17 09:50]:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen: [...] And I agree to your statement, Carlos, that a separate logfile shouldn't be the default setting. I know logging goes now to systemctl journal, and it may increase. Do you think a separate logfile will be much smaller than the additional space on systemctl journal?
obviously not Carlos and only my opinion: {r}syslog text files are undoubtedly larger, easier to access (perhaps due to familiarity) and quicker to display. Also display format and recorded content easier to configure/control. I use both rsyslog and systemd-journal, but have limited systemd-journal severly space wise and seldom consult it. which is better is definitely a personal choice depending more on preference than fact. </opinion> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Patrick, hello Carlos, Am Dienstag, 9. Mai 2017, 16:10:57 CEST schrieb Patrick Shanahan:
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-09-17 09:50]:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen: [...]
And I agree to your statement, Carlos, that a separate logfile shouldn't be the default setting. I know logging goes now to systemctl journal, and it may increase. Do you think a separate logfile will be much smaller than the additional space on systemctl journal?
obviously not Carlos and only my opinion: {r}syslog text files are undoubtedly larger, easier to access (perhaps due to familiarity) and quicker to display. Also display format and recorded content easier to configure/control.
I use both rsyslog and systemd-journal, but have limited systemd-journal severly space wise and seldom consult it.
which is better is definitely a personal choice depending more on preference than fact. </opinion>
sorry that I confused that. For your setup logging via (r)syslog to a logfile in your home-directory seems to be logical. Complications to access systemd journal are well discussed. In fact a matter of taste. Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Wilhelm Boltz wrote:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
The problem is that '-L /var/log/fetchmail' is hardcoded in the startup script. You can write another startup script, and override that in /etc/systemd/system/fetchmail.d/, but that does seem a bit much. The right thing to do would be to fix that startup helper script and move '-L /var/log/fetchmail' into the options so it may be changed by way of /etc/sysconfig/fetchmail.
Still -
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script create /etc/systemd/system/fetchmail.service.d/wilhelm.conf:
------- [Service] ExecStart= ExecStart=/usr/local/bin/wilhelm-fetchmail-exec ---------
systemctl daemon-reload
I followed Per's recommendation and it works well. Thank you very much for your help.
That's great - you managed to work around all my typos. :-) -- Per Jessen, Zürich (13.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 15:49, Wilhelm Boltz wrote:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
Still -
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
create /etc/systemd/system/fetchmail.service.d/wilhelm.conf:
------- [Service] ExecStart= ExecStart=/usr/local/bin/wilhelm-fetchmail-exec ---------
systemctl daemon-reload
I followed Per's recommendation and it works well. Thank you very much for your help.
And I agree to your statement, Carlos, that a separate logfile shouldn't be the default setting. I know logging goes now to systemctl journal, and it may increase. Do you think a separate logfile will be much smaller than the additional space on systemctl journal?
Contrary to what Pattrick says, sorry, a year of syslog is much smaller than a month of journal storing the same data. Tested and proved. With any syslog daemon the traditional setup (and default in openSUSE) is to send all mail related entries to a different file. It is thus easy to track issues with mail this way: all postfix, fetchmail, amavis, dovecot things are logged and timestamped in the same text file. Not procmail, though. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
Still -
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
You have to modify your copy of the script to get rid of the logging option. -- Per Jessen, Zürich (14.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 18:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
Hello Carlos, hello Per,
Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
Still -
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
You have to modify your copy of the script to get rid of the logging option.
But the /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the ExecStart line, that should be enough :-? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Hello Carlos, Am Dienstag, 9. Mai 2017, 18:58:21 CEST schrieb Carlos E. R.:
On 2017-05-09 18:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
[...]
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
You have to modify your copy of the script to get rid of the logging option.
But the /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the ExecStart line, that should be enough :-?
Linux is miraculous, of course, but how could it know what to execute (as is told in wilhelm.conf) if wilhelm-fetchmail-exec does not exist in /usr/local/ bin? Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 19:24, Wilhelm Boltz wrote:
Hello Carlos,
Am Dienstag, 9. Mai 2017, 18:58:21 CEST schrieb Carlos E. R.:
On 2017-05-09 18:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
[...]
copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
You have to modify your copy of the script to get rid of the logging option.
But the /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the ExecStart line, that should be enough :-?
Linux is miraculous, of course, but how could it know what to execute (as is told in wilhelm.conf) if wilhelm-fetchmail-exec does not exist in /usr/local/ bin?
The idea is that the contents of /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the contents of same lines in /usr/lib/systemd/system/fetchmail.service. By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains: ExecStart=/usr/lib/fetchmail-systemd-exec so there is nothing to do. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-05-09 19:24, Wilhelm Boltz wrote:
Hello Carlos,
Am Dienstag, 9. Mai 2017, 18:58:21 CEST schrieb Carlos E. R.:
On 2017-05-09 18:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
[...] > copy /usr/lib/systemd-fetchmail-exec > to /usr/local/bin/wilhelm-fetchmail-exec > remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
You have to modify your copy of the script to get rid of the logging option.
But the /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the ExecStart line, that should be enough :-?
Linux is miraculous, of course, but how could it know what to execute (as is told in wilhelm.conf) if wilhelm-fetchmail-exec does not exist in /usr/local/ bin?
The idea is that the contents of /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the contents of same lines in /usr/lib/systemd/system/fetchmail.service.
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then? -- Per Jessen, Zürich (12.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 20:29, Per Jessen wrote:
Carlos E. R. wrote:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then?
It is disabled by default here. I didn't do it. cer@Telcontar:~> rpm -qV fetchmail cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Hello Carlos, Am Mittwoch, 10. Mai 2017, 00:25:16 CEST schrieb Carlos E. R.:
On 2017-05-09 20:29, Per Jessen wrote:
Carlos E. R. wrote:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then?
It is disabled by default here. I didn't do it.
cer@Telcontar:~> rpm -qV fetchmail cer@Telcontar:~>
of course disabled by default:
willi@saturn:~> sudo service fetchmail status ... * fetchmail.service - A remote-mail retrieval utility
Loaded: loaded (/usr/lib/systemd/system/fetchmail.service; enabled; vendor preset: disabled)> Drop-In: /etc/systemd/system/fetchmail.service.d
`-wilhelm.conf ...
but here running:
willi@saturn:~> sudo rpm -qV fetchmail .......T. /usr/lib/fetchmail-systemd-exec
Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-10 00:34, Wilhelm Boltz wrote:
Hello Carlos,
Am Mittwoch, 10. Mai 2017, 00:25:16 CEST schrieb Carlos E. R.:
On 2017-05-09 20:29, Per Jessen wrote:
Carlos E. R. wrote:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then?
It is disabled by default here. I didn't do it.
cer@Telcontar:~> rpm -qV fetchmail cer@Telcontar:~>
of course disabled by default:
willi@saturn:~> sudo service fetchmail status
No, I mean the log to file is disabled by default here. I don't have a "-L /var/log/fechtmail" option, and I didn't touch it.
but here running:
willi@saturn:~> sudo rpm -qV fetchmail .......T. /usr/lib/fetchmail-systemd-exec
Well, you edited it. You said so in the first post. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-05-09 20:29, Per Jessen wrote:
Carlos E. R. wrote:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then?
It is disabled by default here. I didn't do it.
Which version of fetchmail do you have installed then? On Leap422, I see fetchmail-6.3.26-18.1, and that one has the hardcoded logging option (in the helper script). -- Per Jessen, Zürich (4.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-10 07:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-05-09 20:29, Per Jessen wrote:
Carlos E. R. wrote:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
Where did you disable the logging option then?
It is disabled by default here. I didn't do it.
Which version of fetchmail do you have installed then? On Leap422, I see fetchmail-6.3.26-18.1, and that one has the hardcoded logging option (in the helper script).
The same version as you. Ah, you say in the service script! I was looking at the service file! Sorry for the confusion. Yes, I also have that -L in there. I think this is a bug, the -L option should be optional or none. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Hello Carlos, Am Dienstag, 9. Mai 2017, 19:52:44 CEST schrieb Carlos E. R.:
On 2017-05-09 19:24, Wilhelm Boltz wrote:
[...] The idea is that the contents of /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the contents of same lines in /usr/lib/systemd/system/fetchmail.service.
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
If fetchmail.service is still disabled, there is nothing to do in your case. So your fetchmail runs as a cron-job? Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-09-17 16:18]:
Hello Carlos,
Am Dienstag, 9. Mai 2017, 19:52:44 CEST schrieb Carlos E. R.:
On 2017-05-09 19:24, Wilhelm Boltz wrote:
[...] The idea is that the contents of /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the contents of same lines in /usr/lib/systemd/system/fetchmail.service.
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
If fetchmail.service is still disabled, there is nothing to do in your case. So your fetchmail runs as a cron-job?
why not run fetchmail as a daemon instead of a cron job and generating all the log entries from the cron job? the fetchmail daemon only generates a time-date line unless it downloads some mail or fails to access a site and then it reports that. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Patrick, Am Dienstag, 9. Mai 2017, 23:30:01 CEST schrieb Patrick Shanahan:
* Wilhelm Boltz <boltz.willi.list@gmail.com> [05-09-17 16:18]:
Hello Carlos,
Am Dienstag, 9. Mai 2017, 19:52:44 CEST schrieb Carlos E. R.:
On 2017-05-09 19:24, Wilhelm Boltz wrote:
[...]
The idea is that the contents of /etc/systemd/system/fetchmail.service.d/wilhelm.conf overrides the contents of same lines in /usr/lib/systemd/system/fetchmail.service.
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
If fetchmail.service is still disabled, there is nothing to do in your case. So your fetchmail runs as a cron-job?
why not run fetchmail as a daemon instead of a cron job and generating all the log entries from the cron job? the fetchmail daemon only generates a time-date line unless it downloads some mail or fails to access a site and then it reports that.
yes, of course, started by systemd as on my machine - or what did you mean? Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 22:17, Wilhelm Boltz wrote:
Hello Carlos,
Am Dienstag, 9. Mai 2017, 19:52:44 CEST schrieb Carlos E. R.:
By the way, my /usr/lib/systemd/system/fetchmail.service in Leap 42.2 contains:
ExecStart=/usr/lib/fetchmail-systemd-exec
so there is nothing to do.
If fetchmail.service is still disabled, there is nothing to do in your case.
No, my point is that in openSUSE Leap 42.2 fetchmail service has logging to syslog by default, not to file. Thus either you are not using Leap 42.2, or you got fetchmail from somewhere else, or you modified it, or we got different updates. In fact, we don't have the same version. I have fetchmail-6.3.26-18.1.x86_64, you have 6.3.26-14.1
So your fetchmail runs as a cron-job?
No, manually as user. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
In fact, we don't have the same version. I have fetchmail-6.3.26-18.1.x86_64, you have 6.3.26-14.1
Please post output from: tail -1 /usr/lib/fetchmail-systemd-exec
So your fetchmail runs as a cron-job?
No, manually as user.
So you're not running it via systemd? I think we're talking apples and oranges. -- Per Jessen, Zürich (4.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-10 07:20, Per Jessen wrote:
Carlos E. R. wrote:
In fact, we don't have the same version. I have fetchmail-6.3.26-18.1.x86_64, you have 6.3.26-14.1
Please post output from:
tail -1 /usr/lib/fetchmail-systemd-exec
So your fetchmail runs as a cron-job?
No, manually as user.
So you're not running it via systemd? I think we're talking apples and oranges.
No, I'm not running the systemd service; I was, I thought, comparing the contents of the files you and I have. I didn't notice you were talking about the service helper script. A confusion of mine. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Hello Carlos, Am Dienstag, 9. Mai 2017, 17:54:06 CEST schrieb Carlos E. R.:
On 2017-05-09 15:49, Wilhelm Boltz wrote:
[...] Am Dienstag, 9. Mai 2017, 07:48:27 CEST schrieb Per Jessen:
[...] copy /usr/lib/systemd-fetchmail-exec to /usr/local/bin/wilhelm-fetchmail-exec remove the '-L /var/log/fetchmail' from that script
This part is needed? Don't the below suffice?
Yes, as Per already wrote.
[...] And I agree to your statement, Carlos, that a separate logfile shouldn't be the default setting. I know logging goes now to systemctl journal, and it may increase. Do you think a separate logfile will be much smaller than the additional space on systemctl journal?
Contrary to what Pattrick says, sorry, a year of syslog is much smaller than a month of journal storing the same data. Tested and proved.
Okay.
With any syslog daemon the traditional setup (and default in openSUSE) is to send all mail related entries to a different file. It is thus easy to track issues with mail this way: all postfix, fetchmail, amavis, dovecot things are logged and timestamped in the same text file. Not procmail, though.
To have it that way again, it will be necessary to modify logging for postfix, amavis and dovecot as well? I never thought about that, but you can use "journalctl -u postfix.service -u amavis.service -u dovecot.service -u fetchmail.service" to see all these logs in systemd journal together as well. Kind regards Will -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-09 19:18, Wilhelm Boltz wrote:
Hello Carlos,
With any syslog daemon the traditional setup (and default in openSUSE) is to send all mail related entries to a different file. It is thus easy to track issues with mail this way: all postfix, fetchmail, amavis, dovecot things are logged and timestamped in the same text file. Not procmail, though.
To have it that way again, it will be necessary to modify logging for postfix, amavis and dovecot as well?
No. It is the default.
I never thought about that, but you can use "journalctl -u postfix.service -u amavis.service -u dovecot.service -u fetchmail.service" to see all these logs in systemd journal together as well.
Probably. I have not tried. [...] Produces 1200 lines in my system. Funny. Syslog orders of magnitude more of them for the same period. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-05-08 19:02, Wilhelm Boltz wrote:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving
Are you using Tumbleweed? I see 6.3.26-18 in Leap 42.2, and nothing in the update repo. I see 6.3.26-91 on OBS:server:mail. So I don't know where you got that -14.1 from. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-05-08 19:02, Wilhelm Boltz wrote:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving
Are you using Tumbleweed?
I see 6.3.26-18 in Leap 42.2, and nothing in the update repo. I see 6.3.26-91 on OBS:server:mail.
So I don't know where you got that -14.1 from.
It's from Leap421, the helper script is the same, also has the hardcoded logging option, just like in the later vewrsion in Leap422. -- Per Jessen, Zürich (4.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Carlos, Am Mittwoch, 10. Mai 2017, 01:08:49 CEST schrieb Carlos E. R.:
On 2017-05-08 19:02, Wilhelm Boltz wrote:
I don't like fetchmail (6.3.26-14.1) logging to an extra logfile without giving Are you using Tumbleweed?
I see 6.3.26-18 in Leap 42.2, and nothing in the update repo. I see 6.3.26-91 on OBS:server:mail.
So I don't know where you got that -14.1 from.
yes, I'm using Tumbleweed:
zypper info fetchmail Informationen zu Paket fetchmail: --------------------------------- Repository : tumbleweed-Oss Name : fetchmail Version : 6.3.26-14.1 Arch : x86_64 Anbieter : openSUSE Installierte Größe : 3,1 MiB Installiert : Ja Status : aktuell
Very strange thing: On opensuse build service you can see that fetchmail.exec changed 7 days ago (and sysconfig.fetchmail as well) including new lines and deleting hard coded option for logfile. Forced updating of fetchmail did not import that to my system. Only switching to repository server:mail installed these changes with a newer version of fetchmail.
zypper info fetchmail Informationen zu Paket fetchmail: --------------------------------- Repository : server_mail Name : fetchmail Version : 6.3.26-97.1 Arch : x86_64 Anbieter : obs://build.opensuse.org/server:mail
Switching back to tumbleweed version brought back hard coded option for logfile in fetchmail-systemd-exec. Using version from repo server:mail allows to control behaviour by settings in /etc/sysconfig/fetchmail. That is very nice, whoever had done it, thank you very much. Kind regards -- openSUSE Tumbleweed 20170505 GNU/Linux 4.10.13-1-default x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-05-10 18:29, Wilhelm Boltz wrote: ...
Using version from repo server:mail allows to control behaviour by settings in /etc/sysconfig/fetchmail. That is very nice, whoever had done it, thank you very much.
This is very nice to know :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (5)
-
Anton Aylward -
Carlos E. R. -
Patrick Shanahan -
Per Jessen -
Wilhelm Boltz