On Sun, Jul 14, 2024 at 7:55 AM Anthony Howe via mailop
wrote:
> Umm. Which unmaintained milters?
>
> If you have a problem with one of my milters or BarricadeMX let me know and
> I'll
> address it. Most of my work is now available on GitHub (12 milters and
> BarricadeMX aka smtpf).
I was look
On 2024-07-13 01:33, ml+mailop--- via mailop wrote:
On Fri, Jul 12, 2024, Jesse Hathaway via mailop wrote:
I am a little wary of standing it up, given the lack of maintained open
source milters.
If a program just works, why should it be updated?
Umm. Which unmaintained milters?
If you ha
Pete Long said:
> Great answer. I'd add that no computer code is ever free of bugs; these
> might not be immediately obvious but they're likely to be found and not
> always by the 'good guys'.
> Plus features. ;)
New features add new bugs. If you don't add new features, you reduce the
need fo
> On 13 Jul 2024, at 18:36, Grant Taylor via mailop wrote:
>
> On 7/13/24 00:33, ml+mailop--- via mailop wrote:
>> If a program just works, why should it be updated?
>
> I've seen two reasons that working code needs to be updated:
>
> 1) Moving targets for compiler and tool chain. E.g. cont
On 7/13/24 00:33, ml+mailop--- via mailop wrote:
If a program just works, why should it be updated?
I've seen two reasons that working code needs to be updated:
1) Moving targets for compiler and tool chain. E.g. contemporary
compiler tool chain can get quite unhappy with sufficiently old c
On Fri, Jul 12, 2024, Jesse Hathaway via mailop wrote:
> I am a little wary of standing it up, given the lack of maintained open
> source milters.
If a program just works, why should it be updated?
--
Please don't Cc: me, use only the list for replies, even if the
mailing list software screws u
