[Mailmunge] Mailmunge API discussion

Dianne Skoll dianne at skollsoft.com
Fri May 20 08:35:20 EDT 2022


On Fri, 20 May 2022 00:21:47 -0500
Richard Laager via Mailmunge <mailmunge at lists.mailmunge.org> wrote:

[...]

> I guess I was more-so asking why change and delete are 1-indexed (if
> I'm indeed correct in understanding that they are).

Because that's how the milter library implements it (or at least,
documents it) so I kept the API the same.

> > I don't think this is worthwhile.  Mailmunge makes no guarantee as
> > to which workers are handed which pieces of work

[...]

> I had to check to see if I was crazy. MIMEDefang 2.57-BETA-1 said:

>   * mimedefang-multiplexor: New scheduling algorithm tries to keep
>     commands "sticky".  For example, when looking for a worker to run
>     "recipok", we prefer to use a worker that recently ran "recipok".

The key phrase is "tries to".  It does its best, but makes no guarantees.
Mailmunge still works this way, btw.

Regards,

Dianne.


More information about the Mailmunge mailing list