On 2021-05-15 at 20:16:29 UTC-0400 (Sat, 15 May 2021 20:16:29 -0400)
J Doe
is rumored to have said:
As it stands right now I have not changed any of the milters to
examine the daemon name of "ORIGINATING" and everything is working.
Is this because I have separate flows - submission and smtpd
On 2021-05-16 02:21, J Doe wrote:
Hi Benny,
Thanks for your reply.
I haven't changed the OpenDKIM configuration script to have:
MTA=ORIGINATING and my mail flows still seem to work:
it depends :=)
1. Clients submitting e-mail via submission have their e-mail DKIM
signed.
if just
On 2021-05-15 12:08 a.m., Benny Pedersen wrote:
On 2021-05-15 04:30, J Doe wrote:
1. Why was the magic value of "ORIGINATING" used in the Digital
Ocean example ?
2. Can I allow the default value of: milter_macro_daemon_name to
be used _WITHOUT_ affecting OpenDKIM and ClamAV ?
in
On 2021-05-14 11:38 p.m., Bill Cole wrote:
On 2021-05-14 at 22:30:18 UTC-0400 (Fri, 14 May 2021 22:30:18 -0400)
J Doe
is rumored to have said:
My questions are:
1. Why was the magic value of "ORIGINATING" used in the Digital
Ocean example ?
It's not 'magic' but it is the value that
On 2021-05-15 04:30, J Doe wrote:
1. Why was the magic value of "ORIGINATING" used in the Digital
Ocean example ?
2. Can I allow the default value of: milter_macro_daemon_name to
be used _WITHOUT_ affecting OpenDKIM and ClamAV ?
in opendkim.conf use this in MTA
MTA=ORIGINATING
On 2021-05-14 at 22:30:18 UTC-0400 (Fri, 14 May 2021 22:30:18 -0400)
J Doe
is rumored to have said:
My questions are:
1. Why was the magic value of "ORIGINATING" used in the Digital
Ocean example ?
It's not 'magic' but it is the value that Postfix uses as an example in
master.cf.
Hello,
I have a question regarding configuring submission with Postfix.
I am dusting off a configuration for a server that has been functioning
well for the past three years. When I set up submission, I used the
example from Digital Ocean here:
