Project

General

Profile

Actions

Bug #953

closed

dma.c: some errors

Added by dragonfly-bugs almost 17 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Other
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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} */
Actions #1

Updated by matthias almost 17 years ago

I'll take this one.

Actions #2

Updated by matthias almost 17 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
Actions #3

Updated by corecode about 15 years ago

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

Actions #4

Updated by dragonfly-bugs about 15 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.

Actions #5

Updated by tuxillo almost 12 years 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

Actions #6

Updated by tuxillo about 11 years 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

Actions #7

Updated by tuxillo almost 11 years ago

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

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

Actions

Also available in: Atom PDF