← Back to team overview

launchpad-dev team mailing list archive

Re: Can't seem to 'ec2 land' a merge proposal


On Thu, 2010-03-18 at 10:31 -0400, James Westby wrote:
> On Thu, 18 Mar 2010 11:27:51 +0000, Jelmer Vernooij <jelmer@xxxxxxxxxxxxx> wrote:
> > On Fri, 2010-03-12 at 09:11 -0300, Guilherme Salgado wrote:
> > > I've tried to land one of Adi's MP[1] for 3 times but it didn't reach
> > > PQM and Adi didn't get any failure emails.  Is that a known issue?  If
> > > not, how would I go about debugging it?
> > At least one of the reasons for this was that "ec2 land" specifies all
> > of the stakeholders for a merge proposal to "ec2 test" using --email and
> > "ec2 test" uses the first email address specified for the "From:"
> > header. It uses the SMTP server configured in Bazaar to send email.
> > 
> > The smtp server configured in bazaar.conf doesn't necessarily allow
> > relaying email for that email address - in my case the Canonical SMTP
> > server didn't allow relaying for my preferred Launchpad email address
> > (jelmer@xxxxxxxxx). 
> I found another issue yesterday.
> My bazaar configuration uses localhost:25 as the mail server, and the
> script checks if it is == 'localhost' and complains as that won't work
> on the instance.
> I didn't see any errors related to it failing to send mail when watching
> the output, but if I log in and run the same command it tracebacks.
> It can be made to drop any port specification, but I think that it
> using the local configuration in ec2 is always going to hit problems
> like the one Jelmer mentioned.
The issue I hit was related to the SMTP server in bazaar.conf not
matching the email address that was being used. That should no longer be
an issue now that we're using both settings from the Bazaar

> Why not install postfix on the instance and use localhost for mail
> delivery always? That will avoid issues with having to have an open
> relay or distributing passwords to an authenticated relay.
This might not be as reliable because of SPAM filtering. There are no MX
records for EC2 hosts, reverse hostname lookups don't work, and because
of other users sending SPAM the IP ranges may be blacklisted.



Attachment: signature.asc
Description: This is a digitally signed message part