Dave Gorman, [DG] wrote: DG> I was just wondering if TLS would be a way I could use MDaemon to DG> deliver directly instead of using the smarthost setting to deliver DG> through my ISP.
With direct delivery, MDaemon would have to interact with a lot of
different servers, some of which support TLS and others that don't.
DG> Usually my ISP does OK, but sometimes there are delays in delivery
DG> that I would rather avoid if possible.
MDaemon seems to use StartTLS for deliveries if the receiving server
supports it.
For example, I setup a smarthost for mail deliveries and entered the
name and password. When I check the logs, I see that mail is delivered
to the smarthost using StartTLS even thought I didn't specifically
configure MDaemon to use it.
If you can reliably do direct deliveries then go ahead.
I've converted to using a SmartHost exclusively since I've had problem
deliveries that didn't even result in a bounce or failed delivery. The
message sent simply disappeared and the recipient didn't get it.
Usually, this occurs when an anti-spam utility between you and the
recipient catches your mail before it reaches the recipient. Your mail
is subsequently deleted or placed in a spam bucket never to be seen by
who it was intended for.
--
-= allie_M =- | List Moderator
PGPKeys: http://key.ac-martin.com
____________________________________
Using SB! Lite v2.04.5 on WinXP Pro (SP1)
pgp00000.pgp
Description: PGP signature
________________________________________________ Current version is 2.04.04 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
