notify woes

Matt Mackall mpm at selenic.com
Tue Nov 25 22:01:20 UTC 2014


On Tue, 2014-11-25 at 16:09 -0500, John Turner wrote:
> I looked through 2 years of archives here to no avail, so here goes:

> When I execute a Push from testhg-clone --> testhg, the notify extension is throwing the smtp error:
> 5.7.1 Unable to relay for jturner at mydomain.com<mailto:jturner at mydomain.com>

If you've gotten this far, the problem is not in Mercurial (it's
successfully sent the mail) and entirely in your mail server (it's
rejected the mail due to policy).

Ages ago, it was standard policy for SMTP servers to accept mail from
any machine claiming to be from any user and deliver it to any user
without any form of authentication. This is what was called an "open
relay":

https://en.wikipedia.org/wiki/Open_mail_relay

Now it is common for mail servers out of the box to be much more
paranoid and only accept mail from machines that it knows to be valid
sources for the mail addresses they're sending. In your case, your
Mercurial server is apparently not a trusted source for mail claiming to
be from somewhere in your company. So you might need to either:

a) fix your SMTP server to trust your Mercurial server
b) provide appropriate credentials (see [smtp]username/password)

-- 
Mathematics is the supreme nostalgia of our time.





More information about the Mercurial mailing list