Freron MailMate

Comments and changes to this ticket

• 

  benny May 9th, 2014 @ 12:56 PM

  • State changed from “new” to “fixcommitted”

  I'm actually not quite sure what the best behavior would be. I've tried to follow the standards, but I'm not sure it really does any good to use a meaningful IP address in the EHLO anymore. Especially not when most SMTP servers already require authentication before allowing a user to send messages.

  For now I've added the following hidden preference (untested though):

  defaults write com.freron.MailMate MmSMTPFixedIP -string "127.0.0.1"
  

  Note that [] should not be included.

  I've closed the ticket, but if anyone has an opinion (references) on the subject of default behavior then they are welcome.

• 

  benny October 15th, 2014 @ 03:32 PM

  • State changed from “fixcommitted” to “fixreleased”

  [bulk edit]

• You flagged this item as spam.
  

  Bill Cole April 25th, 2016 @ 10:16 PM

  • Tag set to “ehlo, hostname, smtp”

  RFC5321 and its recent ancestors allow [bracketed] IP literals in EHLO/HELO arguments when a client hostname that would be correctly meaningful to the server is unknown, but there's a clear preference for a name over an IP literal in the RFCs. Operationally, there are some mail severs which treat mail with greater distrust when it is offered on a session with an IP literal HELO argument because empirically the only SMTP clients that use IP literals are MUAs like MailMate (which usually mitigate the issue by authenticating) and spambots. While the most common use cases for MailMate do make an IP literal the best choice, it would be helpful to support the use of a proper hostname, either by allowing the user to set it explicitly with a special preference like MmSMTPFixedIP and/or by detecting when the system has a reasonable FQDN configured as its hostname, e.g. a name which doesn't end in an invalid or reserved TLD (e.g. .local, .test, etc) and resolves to an IP address that either matches an IP on a network interface OR is a public IP while the machine's network interfaces only have RFC1918 addresses (i.e. is likely to be the name of a NAT address.)

• You flagged this item as spam.
  

  Bill Cole October 22nd, 2016 @ 02:47 AM

  • Tag set to “ehlo, hostname, smtp”

  Maybe my last comment was too verbose, as it didn't spur any response.

  Short form: It would be helpful to be able to set the HELO argument to a hostname because that is both the formally preferred behavior AND it can allow a single setting to be correct across all accounts, even when network circumstances make the client appear at different IPs to different outbound servers.

  The simplest way to do this would be to detect whether MmSMTPFixedIP is an IP address or a hostname, and if it's not an IP, skip putting the [] around it.

• 

  benny October 27th, 2016 @ 01:25 PM

  Here you go:

  defaults write com.freron.MailMate MmSMTPFixedHostname -string "example.com"
  

  This takes precedence over MmSMTPFixedIP (and it could replace it by manually adding [...]). I didn't want to add IPv4/IPv6 address recognition if I didn't have to.

  It's not released yet, but it should work in r5293+.