From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: [PATCH] dma: Update to 0.13 Date: Sat, 30 Jan 2021 12:47:47 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7808682979435071167==" List-Id: --===============7808682979435071167== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, hello Adolf, hello development folks, thanks for your replies. I completely agree to our MTA needing to be smarter than /usr/bin/sendmail; b= ack then, nullmailer seemed to be an alternative to me. However, as Michael mentioned, it has no s= ignificant benefits over DMA (apart from hopefully being maintained more active, but I have not c= hecked that), and behaves RFC-ignorant at some other points. Today, replacing DMA with nullmailer thereof does not seem to be worth the ef= fort to me. Aside from Postfix (and perhaps Exim), there are few open source MTAs left, a= nd none of them is known to me to be RFC-compliant. Further, I agree on Postfix being too heavy = for an IPFire machine which is just spewing out some notification mails every now and then. I have no solution to this problem, yet I think we can agree on the current s= ituation not being optimal. Because of this, accepting Adolf's patch makes sense to me. Reviewed-by: Peter M=C3=BCller Thanks, and best regards, Peter M=C3=BCller > Hello Peter, >=20 > We know about your personal hatred for dma. >=20 > I do agree though. A couple of years you proposed replacing it with nullmai= ler which didn=E2=80=99t look too much better after a quick glance over the c= ode. >=20 > I still stand by the fact that we need something that does more than a =E2= =80=9Cfire and forget=E2=80=9D email. If it cannot be sent immediately, the e= mail needs to be spooled somewhere and tried again later. >=20 > dma is a very simple implementation that did this job. I agree with the bad= patches that are being accepted right now and that make the whole software p= otentially vulnerable. The maintainer has confirmed to me that he has no inte= rest in continuing development of dma and that he might consider a rewrite in= Go or Rust or any other =E2=80=9Cmodern=E2=80=9D =E2=80=9Cprogramming=E2=80= =9D language. >=20 > Therefore I would like to ask if you still want to replace dma by nullmaile= r or something else? >=20 > -Michael >=20 >> On 28 Jan 2021, at 20:36, Peter M=C3=BCller w= rote: >> >> Good evening Adolf, >> good evening *, >> >> while you neither are responsible for nor can change anything to it, I mus= t say missing changelogs >> are not a good sign to me. Referring to https://github.com/corecode/dma/co= mmits/master, there were >> four commits to the source code since version 0.12: >> >> 1. Make MASQUERADE config setting override -f >> 2. add support for RFC976 From_ lines >> 3. add option to verify server certificate fingerprint >> 4. Change RCPT TO to split up multiple addresses >> >> The latter is especially - um - interesting as the full commit message (av= ailable online at >> https://github.com/corecode/dma/commit/450d4b68d3295d2ef50fa5c9576f5c4e043= c0c80) states: >> >>> RFC5321 section 4.1.1.3 states that RCPT TO only takes one address at a t= ime. >> >> Seriously?! Not even an MTA programmer is reading most basic mail RFCs any= more?!?! >> >> Yes, DMA might be a lightweight replacement for Postfix on machines just n= eeding a better smarthost. >> However, the commit above means DMA behaved RFC-ignorant as soon as a mess= age had more than one >> recipient - which apparently does not seem to happen that often to DMA use= rs. >> >> RFC 5321 is not about rocket science or some exotic corner cases at all, i= t is one of the most basic >> internet standards regarding e-mail communication. We have lost the comple= xity battle years ago, >> apparently, we cannot count on application programmers to have a slightest= clue about what they are >> doing as well. >> >> I am shocked about the quality of that piece of software. >> >> Embittered, >> Peter M=C3=BCller >> >>> - Update dma from 0.12 to 0.13 >>> - No changelog information available >>> - No change to the rootfile >>> >>> Signed-off-by: Adolf Belka >>> --- >>> lfs/dma | 4 ++-- >>> 1 file changed, 2 insertions(+), 2 deletions(-) >>> >>> diff --git a/lfs/dma b/lfs/dma >>> index aceb2704e..78bb6465f 100644 >>> --- a/lfs/dma >>> +++ b/lfs/dma >>> @@ -24,7 +24,7 @@ >>> >>> include Config >>> >>> -VER =3D 0.12 >>> +VER =3D 0.13 >>> >>> THISAPP =3D dma-$(VER) >>> DL_FILE =3D $(THISAPP).tar.gz >>> @@ -40,7 +40,7 @@ objects =3D $(DL_FILE) >>> >>> $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE) >>> >>> -$(DL_FILE)_MD5 =3D 58cb2a286995381c92dc557e639622d6 >>> +$(DL_FILE)_MD5 =3D 8bf824b065295a594f399c8b96663673 >>> >>> install : $(TARGET) >>> >>> >=20 --===============7808682979435071167==--