Re: Sending Unencrypted E-mails

Bs Serge <[email protected]>
Newsgroups gmane.comp.jakarta.james.user
Message-ID <CAO7MO+PSkVQ6-ko21Pw8XJ5auFOtcYvcK5n=Xs=xCdYqgwSoUA@mail.gmail.com>
It seems like your shared mailetcontainer.xml file is not of 3.6.0 version,

This is my RemoteDelivery mailet in mailetcontainer.xml and

<!-- Attempt remote delivery using the specified repository for the spool,
-->
       <!-- using delay time to retry delivery and the maximum number of
retries -->
       <mailet match="All" class="RemoteDelivery">
          <outgoing>outgoing</outgoing>

          <!-- Delivery Schedule based upon RFC 2821, 4.5.4.1 -->
          <!-- 5 day retry period, with 4 attempts in the first
                 hour, two more within the first 6 hours, and then
                 every 6 hours for the rest of the period.
          <delayTime>4 * 15 minutes, 2 * 3 hours, 18 * 6 hours</delayTime>
          -->
          <delayTime>5000, 100000, 500000</delayTime>
          <maxRetries>3</maxRetries>

          <!-- The max reties which will used if no A or MX record for the
domain was found. -->
          <!-- If 0 it will fail on first time -->
          <maxDnsProblemRetries>0</maxDnsProblemRetries>

          <!-- The number of threads that should be trying to deliver
outgoing messages -->
          <deliveryThreads>10</deliveryThreads>

          <!-- If false the message will not be sent to given server if any
recipients fail -->
          <sendpartial>true</sendpartial>

          <!-- By default we send bounces to the "bounce" processor -->
          <!-- By removing this configuration James will fallback to
hardcoded bounce -->
          <!-- notifications -->
          <bounceProcessor>bounces</bounceProcessor>

          <!-- A single mail server to deliver all outgoing messages. -->
          <!-- This is useful if this server is a backup or failover
machine, -->
          <!-- or if you want all messages to be routed through a
particular mail server, -->
          <!-- regardless of the email addresses specified in the message
-->
          <!-- -->
          <!-- The gateway element specifies the gateway SMTP server name.
-->
          <!-- If your gateway mail server is listening on a port other
than 25, -->
          <!-- you can set James to connect to it on that port using the
gatewayPort -->
          <!-- element. -->
          <!-- Although normally multiple addresses are implemented through
proper -->
          <!-- DNS configuration, the RemoteDelivery mail does allow
specifying -->
          <!-- multiple gateway elements, each of which may also have a
port -->
          <!-- e.g., mygateway:2525 -->
          <!-- the gatewayPort element is used as a default -->
          <!--
          <gateway>otherserver.mydomain.com</gateway>
          <gatewayPort>25</gatewayPort>
            -->
          <!-- If the gateway requires smtp authentication the following
directives -->
          <!-- (gatewayUsername/gatewayPassword) can be used. -->
          <!--
          <gatewayUsername>login</gatewayUsername>
          <gatewayPassword>pass</gatewayPassword>
            -->

          <!-- Set the HELO/EHLO name to use when connectiong to remote
SMTP-Server -->
          <!--
          <mail.smtp.localhost>myMailServer</mail.smtp.localhost>
            -->
       </mailet>


I added this last part :

<startTLS>true</startTLS>
<sslEnable>false</sslEnable>
<heloName>${env:OP_JAMES_REMOTE_DELIVERY_HELO}</heloName>

and James emails could not reach the destination,

I'm still looking
Regards,

On Thu, Dec 23, 2021 at 3:57 AM [email protected] <[email protected]>
wrote:

> <processor state="relay" enableJmx="true"> <mailet match="All"
> class="RemoteDelivery"> <outgoingQueue>outgoing</outgoingQueue>
> <delayTime>5000, 100000, 23*500000</delayTime>
> <maxRetries>25</maxRetries>
> <maxDnsProblemRetries>0</maxDnsProblemRetries>
> <deliveryThreads>10</deliveryThreads> <sendpartial>true</sendpartial>
> <bounceProcessor>bounces</bounceProcessor> <debug>true</debug>
> <startTLS>true</startTLS> <sslEnable>false</sslEnable>
> <heloName>${env:OP_JAMES_REMOTE_DELIVERY_HELO}</heloName> </mailet>
> </processor>
>
> (sample taken from mailetcontainer.xml of one of my environments.)
>
> The important thing here is startTLS true as it enable opportunistic
> connection upgrades.
>
> Your very next problem is GMail complaining about your self signed
> certificates used for RemoteDelivery: You need to set up javax.mail to
> use your regular certificates.
>
> Regards,
>
> Benoit
>
> On 22/12/2021 19:04, Bs Serge wrote:
> > Hi again,
> >
> > After configuring Reverse DNS PTR record, SPF, DKIM and DMARC, emails I
> > send are now out of spam and inside the inbox (of GMAIL, ...)
> >
> > But they are still marked as unencrypted as you can see here:
> > https://ibb.co/FsLF6Lr
> >
> > Even though I configured STARTTLS and generated an SSL certificate using
> > Letsencrypt (certbot)
> >
> > I have added screenshots of other checks as well  :
> >
> > - mxtoolbox.com : https://ibb.co/StSwwtP
> > - checktls.com : https://ibb.co/f8KHj0t
> > - GMAIL show original: https://ibb.co/jRwcs1w
> > - DMARC: https://ibb.co/VBJ0SZ1
> >
> > Kindly let me know what I might be missing.
> >
> > Any comments or thoughts would be appreciated.
> >
> > Best Regards,
> >
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.