transport-email unable to send to GMail recipient

CJ

@Andrew @olivierlambert If anyone can provide me with the proper place to look for logs, etc, I can attempt to determine what's going on. My XOA is a source install as well.

Also, now that I know what's causing the problem, I can use my own domain to review the test messages as they still work.

olivierlambert

So if XO from sources it's NOT XOA (XOA is only meant for the virtual appliance we deliver). I'll be curious to see if you have the same issue with XOA, that would help to rule out a XO-related issue

CJ

@olivierlambert Sorry, didn't realize.

How can I test it in XOA? I don't have the transport-email plugin.

CJ

This post is deleted!

CJ

@Andrew I think I figured out why it's happening. It looks like NodeMailer is getting the hostname and because mine isn't a FQDN then it sets the default hostname to 127.0.0.1

https://github.com/nodemailer/nodemailer/blob/master/lib/smtp-connection/index.js#L1788

Is your hostname a FQDN?

Apparently Debian thinks hostname should not return a FQDN. https://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_the_hostname

CJ

@olivierlambert @Andrew That did it. If the hostname of the machine doesn't contain a . then NodeMailer sets it to 127.0.0.1 and therefore sends helo 127.0.0.1 when it connects to the SMTP server.

It looks like if a client name is passed to NodeMailer it skips this check, so would it be possible for XO to expose the field as an optional parameter?

olivierlambert

Thanks for your feedback, let me add @julien-f in the convo

julien-f

@CJ Which field would you want to be optional?

CJ

@julien-f The client hostname, although I don't know that that's really the best solution. This seems like a weird edge case that doesn't seem to affect most people.

Right now I've added the domain to my /etc/hostname file even though it's against Debian convention.

julien-f

@CJ Please test the branch email-local-hostname which make the local hostname configurable and keep me posted.