Re: [PLUG] SMTP communications question

[Rich Shepard]

On Thu, 23 Nov 2017, Mke C> wrote:


I'd say start at the OpenDKIM SoureForge Project page. From their Support
tab, "opendkim says the best way to get help with its software is by using
its ticket tracker: Support Requests." 
https://sourceforge.net/projects/opendkim/support


Mike,

  I think I saw a reference to that somewhere but there's also supposed to
be a mail list except the subscription page won't load. I much prefer mail
lists to web fora.

  I'm in contact with the SlackBuilds.org package maintainer and will see if
he can help resolve this.


Happy Thanksgiving!


  And the same to you, too.

Regards,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[Mke C>]

On 11/21/2017 03:16 PM, plug-requ...@pdxlinux.org wrote:

  BTW, if you can suggest a mail list or web forum for openDKIM assistance
I'd appreciate it.

Happy Thanksgiving,
Hey Rich - I'd say start at the OpenDKIM SoureForge Project page. From 
their Support tab, "opendkim says the best way to get help with its 
software is by using its ticket tracker: Support Requests."  
https://sourceforge.net/projects/opendkim/support


HtH.

Happy Thanksgiving!
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[Rich Shepard]

On Tue, 21 Nov 2017, Rich Shepard wrote:


    To improve your emails deliverability, your MTA-EHLO/PTR/MX hostnames
should all match. If you use an inbound/cloud filtering service, the
hostname in your DNS MX record doesn't need to match, but the MTA EHLO
and PTR/reverse DNS should match.


 They'll all match.


  Hadn't thought of this since I set up postfix ~20 years ago. In main.cf
the myhostname variable was set to salmo.appl-ecosys.com so I just changed
it to mail.appl-ecosys.com. They are aliased to each other in /etc/hosts.

Thanks again, Alex,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[wes]

>
>
>   BTW, if you can suggest a mail list or web forum for openDKIM assistance
> I'd appreciate it.
>
>
I gave up on trying to make mail work a long time ago. In fact, now that I
think of it, I believe it was trying to get DKIM to work that finally
pushed me over the edge to giving up.

-wes
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[Rich Shepard]

On Tue, 21 Nov 2017, Alexandre Bedard wrote:


    Your EHLO hostname is controlled by your MTA (Postfix, Sendmail,qmail,
etc), not the MUA. Most MTA's have a configuration option to specify your
mail server's EHLO hostname. Most Linux distros/MTA's will default to the
contents of /etc/mailname.


Alex,

  Ah, I didn't remember this. I'll go look for it in master.cf or main.cf
and change it from 'salmo' to 'mail.' Then, ...


    To improve your emails deliverability, your MTA-EHLO/PTR/MX hostnames
should all match.  If you use an inbound/cloud filtering service, the
hostname in your DNS MX record doesn't need to match, but the MTA EHLO and
PTR/reverse DNS should match.


  They'll all match.

Happy Thanksgiving,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[Rich Shepard]

On Tue, 21 Nov 2017, wes wrote:


This is up to the administrator of the recipient MTA. They can decide
whether to reject mail from senders who claim to be host x in their HELO,
but have a different name in their PTR record. In my experience, most of
them simply check that a PTR record exists at all, as it used to be hard
to get them.


Wes,

  And I just found an answer on the web:

"Although email servers can (by RFC) accept connections that have a poorly
formatted HELO or server identification string sent during email
transmission dialogue (eg MTA to MTA communications) most Best Practises
documents insist that all identifiers are correctly used, and in the case of
HELO (or EHLO) this applies as well. The principal is that the HELO should
identify the sending server in such a way that it can be used to identify
servers with problems, such as leaking Spam or incorrectly formatted
emails."


It's postfix (in your case) that adds the hostname, not alpine.


  I should have realized this.

  BTW, if you can suggest a mail list or web forum for openDKIM assistance
I'd appreciate it.

Happy Thanksgiving,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] SMTP communications question

[wes]

This is up to the administrator of the recipient MTA. They can decide
whether to reject mail from senders who claim to be host x in their HELO,
but have a different name in their PTR record. In my experience, most of
them simply check that a PTR record exists at all, as it used to be hard to
get them.

It's postfix (in your case) that adds the hostname, not alpine.

-wes

On Tue, Nov 21, 2017 at 2:44 PM, Rich Shepard 
wrote:

>   I understand that when an e-mail message is sent the client MTA initiates
> communications with the receiving/relaying server MTA with a HELO or EHLO
> command. The recipient MTA is identified by its DNS MX record. Both
> HELO/EHLO and MX have a host name prefixed to the domain name.
>
>   Does it matter if the sending MTA host name differs from the PTR host
> name? The Frontier DNS tech told me that the PTR host name needed to match
> the DNS A record for the sending host (which is mail.)
>
>   My PTR and DNS A records have been set to mail.appl-ecosys.com. When an
> outbound message is queued by the recipient MTA's greylisting process I can
> see in the postfix queue that the HELO host is salmo.appl-ecosys.com. I
> think that the MUA (alpine) adds the host name, but I'm not sure of this.
>
> Rich
>
>
>
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug