On Thu, 2011-10-20 at 11:07 +0200, Stefano Rivera wrote:
> Yes. But launchpad already requires credentials. Although now you
> mention it, I'm reminded of
> https://bugs.launchpad.net/launchpad/+bug/252368
> which would work for mail, but not the API.
Oh, I thought the mail interface wouldn't req
Hi Paul (2011.10.20_03:56:00_+0200)
> Will this require people to input their Launchpad credentials to submit
> sync requests? I guess many DDs will not have such credentials.
Yes. But launchpad already requires credentials. Although now you
mention it, I'm reminded of
https://bugs.launchpad.net/l
retitle 645762 requestsync: please use the Launchpad API by default
thanks
On Wed, 2011-10-19 at 23:14 +0200, Stefano Rivera wrote:
> requestsync can also use Launchpad's API, with the --lp flag (and in
> general, this will give a far better experience).
>
> This will use https (port 443), which
severity 645762 wishlist
thanks
> Many ISPs block the SMTP port (25) by default, I would suggest that
> requestsync should by default use the submission port (587) as codified
> in RFC4409. This would require the Launchpad to first accept mail
> destined for Launchpad on that port.
requestsync ca
Package: ubuntu-dev-tools
Version: 0.132
Severity: normal
File: /usr/bin/requestsync
Many ISPs block the SMTP port (25) by default, I would suggest that
requestsync should by default use the submission port (587) as codified
in RFC4409. This would require the Launchpad to first accept mail
destine
5 matches
Mail list logo
