On 10/14/19 2:17 AM, Ken Moffat via blfs-dev wrote:
For a long time, fetchmail has warned about running as root. For
6.4.1 I'm inclined to try running it as user fetchmail and group
nogroup. But that raises the question of which uid to assign.
Looking at /postlfs/users.html (or postlfs/config/users.xml) I can
see there are gaps:
from 10 to 15, at 24,29,30,38,39,44,49, from 52 to 55, from 58 to
59, from 66 to 69, from 80 to 82, at 89, from 91 to 96.
I'm sure that the organization made sense, but not convinced that
most of these are now other than random choices. So, is there any
logic which escapes me, or else any preference for where fetchmail
would best fit ?
NB I have not yet attempted to run fetchmail as other than root (or
as my normal user), it might be that I eventually decide the change
is "too hard for a bear of little brain".
I also note that Arch (AUR) picked up 6.4.1 not very long ago, and
for that they provide a fetchmail.service file (the daemon runs every
900 seconds which to me seems "not very often"). Should we offer
something similar, and a sysvinit bootscript ? I'm currently
running my own bootscript at S38 in runlevels 3,4,5 and at K27 in
the other runlevels.
Haven't really thought about that, I'm running fetchmail per cron job
every three minutes, doing an su to the relevant mail user, so never as
root.
But as getting mails by pop3/imap and forwarding them per smtp could be
done by a single user for multiple users, having a separate fetchmail
user might be a good idea. I'd go for nobody/nogroup, as this is already
present and I don't really see the point in having a seperate user for
every single program.
I will however keep my "su $USER -c fetchmail" mode, as that seems to be
the proper way to get mails and allows for a fallback to procmail, if
an smtp daemon is not available.
ĸen
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
