Bug #953

dma.c: some errors

Added by dragonfly-bugs about 6 years ago. Updated about 1 month ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:tuxillo% Done:

0%

Category:Other
Target version:3.8.0

Description

1. According to the man page, -q does not take an argument (see
simple patch below).

2. dma sends EHLO without reading the server greeting first. This
causes rejections by some anti-spam measures, e.g., greet_pause in
sendmail 8, or "illegal pipelining" in some other MTAs.

3. dma does not read the server greeting to determine whether
STARTTLS or AUTH are available (minor problem as this probably is
just a configuration problem because only one "smarthost" is
contacted).

4. If you want to make this a "full blown" mail submission program,
you might want to merge some features from femail.c (written by
Henning Brauer) into it, e.g., to read recipients from the message
headers, or to add required headers. femail.c lacks queueing which
dma supports.

--- dma.c.orig Thu Feb 21 20:49:07 2008
+++ dma.c Thu Feb 21 15:29:35 2008
@@ -836,7 +836,7 @@
snprintf(tag, 254, "dma");

opterr = 0;
- while ((ch = getopt(argc, argv, "A:b:Df:iL:o:O:q:r:")) != -1) {
+ while ((ch = getopt(argc, argv, "A:b:Df:iL:o:O:qr:")) != -1) {
switch (ch) {
case 'A':
/* -AX is being ignored, except for -A{c,m} */

History

#1 Updated by matthias about 6 years ago

I'll take this one.

#2 Updated by matthias about 6 years ago

Hi,

That is a mistake in the man page :) -q takes arguments to make some
startup scripts happy.

Yup, I need to take care of that. Its on my TODO, but I'll be off for a
week (no network) and will have a look at it after that time.

Ack.

Never heard of femail.c. I'll have a look at it, thanks for the hint.

Regards

Matthias

#3 Updated by corecode over 4 years ago

I believe the issues have been addressed. Can you confirm?

#4 Updated by dragonfly-bugs over 4 years ago

On Sat, Dec 05, 2009, Simon 'corecode' Schubert (via DragonFly issue tracker) wrote:

> I believe the issues have been addressed. Can you confirm?

Yes, except for the minor item #3.

#5 Updated by tuxillo about 1 year ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee changed from corecode to tuxillo

Hi,

All points were handled but the third one. I've opened an issue in dma github's page: https://github.com/corecode/dma/issues/15
We're on dma 0.7 now, latest seems to be 0.8.

Once the bug is fixed, ideally we would bring latest stable version of dma.

Cheers,
Antonio Huete

#6 Updated by tuxillo 4 months ago

  • Description updated (diff)

Still no updates on this, but there is an update in the github's ticket:

bigon commented 6 months ago

Hi,

Just to add that regarding the detection of AUTH mechanisms, when CRAM-MD5 is not available on the server, dma is currently printing a quite scary (from a user point of view) in the logs

smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: no mechanism available

#7 Updated by tuxillo about 1 month ago

  • Category set to Other
  • Status changed from In Progress to Closed
  • Target version set to 3.8.0

Hi,

Since point 3 is the only remaining one and it's reported in https://github.com/corecode/dma/issues/15 , I'm closing this issue.

Cheers,
Antonio Huete

Also available in: Atom PDF