On 17-09-2025 15:27, Haines Brown via Dng wrote:
> I've given up at present trying to migrate from exim to dma,
> altough will try again
>
> Purged exim4 and installled the dma. this time from my machine's
> repository. While this is a very old version at least it nicely
> created the dma configuration files. I set SMARTHOST to the correct
> address with a ::587 appended. But my ISP neverteless rejected mails
> seng by means of dma because it mail uses port 25.
>
> In the configuration I eneterd PORT 587, but that didn't help.
>
> Strangly, when I do $ telnet localhost 25 I get connection
> refused. But when I replace dma with exim4, telnet has no
> problem. Is dma imposing local port 25 even though I specify my
> ISP's port to be 587 on the PORT line? Am I missing someting in
> the configuration?
>
> So I'm now back running exim4. If I fetch mail with the fetchmail
> command rather that run fetchmail as a daemon, the problematic
> messaage have ended. Perhaps pruring exim did the trick, but I
> thought I had done that originally.
>
> So problem apparently over, but will try to to migrate to dma
> again at some point.
>
If you are using  a SMARTHOST you have besides PORT to set this too:

      *SECURETRANSFER*  (boolean, default=commented)
            Uncomment if you want TLS/SSL secured transfer.

Set this to true for both port 465 and 587.

      *STARTTLS*  (boolean, default=commented)
            Uncomment if you want to use STARTTLS.  Only useful together with
            `SECURETRANSFER'.

STARTTLS is default for port 587 and should be true when using 587. It
will not work for port 465.


And maybe depending on your ISP:

      *OPPORTUNISTIC*/_/*TLS*  (boolean, default=commented)
            Uncomment if you want to allow the STARTTLS negotiation to fail.
            Most useful when*dma*  is used without a smarthost, delivering remote
            messages directly to the outside mail exchangers; in opportunistic
            TLS mode, the connection will be encrypted if the remote server
            supports STARTTLS, but an unencrypted delivery will still be made
            if the negotiation fails.  Only useful together with
            `SECURETRANSFER' and `STARTTLS'.