notify woes

[John Turner]

(apologies if this formats poorly - it's Outlook)

Many thanks Matt for the quick response - I'll try and track things down on the Exchange side and keep trying config options (username/password) as you suggest for [smtp] parameters in mercurial.ini

I love the version control, but this notify extension has been killing me today.  I now realize that debugging config settings are a good use case for version control!

As an aside, any ideas how/where to view the stdout file for debugging/testing in a Windows environment?

John J. Turner
Database Development Manager
Energi, Inc
Energi Insurance Services, Inc.
10 Centennial Drive, Suite 201
Peabody, MA 01960
Work: 978-531-1822, ext. 897



jturner at energi.com
www.energi.com
24 Hour Claims Reporting 1-888-CLAIM50

This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Energi, Inc., Energi Insurance Services, Inc. shall be understood to be neither given nor endorsed by the Company. Any information contained in this e-mail is subject to the terms and conditions in the governing client contract. Please note that insurance coverage cannot be bound, terminated, increased, decreased or otherwise modified by messages sent through electronic mail.
> -----Original Message-----
> From: Matt Mackall [mailto:mpm at selenic.com]
> Sent: Tuesday, November 25, 2014 5:01 PM
> To: John Turner
> Cc: mercurial at selenic.com
> Subject: Re: notify woes
>
> 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.
>
>
>
>
> Scanned with AppRiver SecureTide. Send suspected spam to
> spam at appriver.com