On Mon, 5 Feb 2024, Jeremy Harris via Exim-users wrote:
On 2/5/24 15:01, graeme vetterlein via Exim-users wrote:
But it occurs to me I'm rather "living on the edge" here I have multiple
cronjobs an I guess with a single edit I could end up with multiple
writers. So I guess I need to ensure mai
On 2/5/24 15:01, graeme vetterlein via Exim-users wrote:
But it occurs to me I'm rather "living on the edge" here I have multiple
cronjobs an I guess with a single edit I could end up with multiple writers. So I guess I
need to ensure maildrop and exim4 share a single view of locking .
Exim's
On Mon, Feb 05, 2024 at 03:01:03PM +, graeme vetterlein via Exim-users
wrote:
> BTW this came to my attention while debugging a maildrop setup I noted it
> using flock(2) I also note it can use dot-lock files. Now fetchmail,
> maildrop, exmim4, procmail etc all work together in many combinatio
Hi all,
I get my mail via *fetchmail*(1), which then invokes some convoluted
rules in *maildrop*(1) ... eventually maildrop usually passed the mail
to *sendmail*(1) (AKA *exim4*) *or writes it into a mailbox.*
*
*
Now, to some extent, I'm in a simplified position as maildrop runs
sequentia
