It seems like your shared mailetcontainer.xml file is not of 3.6.0 version,
This is my RemoteDelivery mailet in mailetcontainer.xml and
outgoing
5000, 10, 50
3
0
outgoing
5000, 10, 23*50
25
0
10 true
bounces true
true false
${env:OP_JAMES_REMOTE_DELIVERY_HELO}
(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
The “Learn more” link from GMAIL leads to this page :
https://support.google.com/mail/answer/6330403?visit_id=637757678589778136-970944847=tls=en=1#zippy=%2Cwhy-some-emails-might-not-be-encrypted
On Wed, Dec 22, 2021 at 2:04 PM Bs Serge wrote:
> Hi again,
>
> After configuring Reverse DNS PTR
Hi Benoit and David,
You are right,
Seems like I'm missing the Reverse DNS entry for my IP address as well as
SPF and DKIM configuration for my domain
Thank you very much I'll let you know how it goes
Best Regards,
On Sat, Dec 18, 2021 at 11:27 AM David Matthews
wrote:
>
Hi Benoit and David,
You are right,
Seems like I'm missing the Reverse DNS entry for my IP address as well as
SPF and DKIM configuration for my domain
Thank you very much I'll let you know how it goes
Best Regards,
On Sat, Dec 18, 2021 at 11:27 AM David Matthews
wrote:
>
>https://dmatthews.org/java_email.html
is out of date with James, but probably still ok DKIM wise
also
https://dmatthews.org/email_auth.html
My confident guess is if you do "Show original" on the message in the gmail
spam box, it will complain about SPF and/or DKIM. These days that's simply
Hello.
Incoming SMTP (receiving emails) is intrinsequely different from sending
emails.
Sending emails is govern by RemoteDelivery mailet within
mailetcontainer.xml. To get RemoteDelivery trusted by third parties you can:
- Enable optimistic STARTTLS upgrades - email relaying happens on port
