Bug#979965: milter-greylist exits after running for a few minutes
On Tue, Jan 12, 2021 at 05:43:07PM -0500, Michael Grant wrote:
> On Tue, Jan 12, 2021 at 10:02:19PM +0000, Sudip Mukherjee wrote:
> > On Tue, Jan 12, 2021 at 9:36 PM Michael Grant <mgrant@grant.org> wrote:
> > >
> > > I have made this change:
> > >
> > >
> > >
<snip>
>
> I could probably send you my config files. I do have a fairly large database of grey listed hosts. I probably don't want to post that in the bug tracking database!
>
> For me, it runs for a while in side sendmail as a milter, I get a few messages, then it restarts.
>
> The journalctl is huge, I will forward it to you after. It doesn't seem to have any extra info.
Thanks Michael for helping to test and debug this.
To summarise, the latest update has completely changed the runtime behaviour of milter-greylist.
1) milter-greylist now runs as user 'smmsp' instead of 'greylist'.
2) As a result of (1) it now fails to open, read and write the db file which can only be read and written by 'greylist'.
3) It now runs as a foregound process instead of a daemon.
4) /var/run/milter-greylist is now created as user/group 'root' instead of 'greylist'
5) /var/run/milter-greylist.pid is now created as user 'smmsp' instead of 'greylist'.
The error seen by Michael was mainly for (1) and (2) as the program will exit with OSERR when it fails to open the db file.
Any, new install will also see (4) and (5).
imho, the severity of this bug should have been 'serious' as it made the package unusable.
The changes I suggested seems to have fixed the problem, I will now create a package with the modification and send it to Michael for a final test.
--
Regards
Sudip
Reply to: