Bug#645762: requestsync: uses SMTP port (25) instead of submission port (587)
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/launchpad/+bug/252368 which would work for mail, but not the API. I'll bring this up at the Debian Health check at UDS, next month. https://blueprints.launchpad.net/ubuntu/+spec/community-p-debian SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645762: requestsync: uses SMTP port (25) instead of submission port (587)
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 require an account. I'll bring this up at the Debian Health check at UDS, next month. https://blueprints.launchpad.net/ubuntu/+spec/community-p-debian Thanks for that. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#645762: requestsync: uses SMTP port (25) instead of submission port (587)
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 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 is almost universally unblocked. I think the right answer is to make --lp the default. I don't see any particularly good reason for them to listen on the submission port. requestsync is probably the only tool that mails launchpad directly. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645762: requestsync: uses SMTP port (25) instead of submission port (587)
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 is almost universally unblocked. I think the right answer is to make --lp the default. I don't see any particularly good reason for them to listen on the submission port. requestsync is probably the only tool that mails launchpad directly. I think that is a much better idea indeed. Will this require people to input their Launchpad credentials to submit sync requests? I guess many DDs will not have such credentials. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#645762: requestsync: uses SMTP port (25) instead of submission port (587)
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 destined for Launchpad on that port. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ubuntu-dev-tools depends on: ii binutils 2.21.90.20111004-2 ii dctrl-tools2.18 ii devscripts 2.11.1 ii diffstat 1.54-1 ii distro-info0.2.1 ii dpkg-dev 1.16.1 ii lsb-release3.2-28 ii perl 5.12.4-4 ii python 2.7.2-8 ii python-apt 0.8.0 ii python-debian 0.1.21 ii python-launchpadlib1.9.9-2 ii python-lazr.restfulclient 0.12.0-1 ii python2.6 2.6.7-3 ii python2.7 2.7.2-5 ii sudo 1.8.2-2 Versions of packages ubuntu-dev-tools recommends: ii bzr 2.3.1-2 ii bzr-builddebnone ii ca-certificates 20110502+nmu1 ii cowdancer 0.65 ii debian-archive-keyring 2010.08.28 ii debian-keyring 2011.08.07 ii debootstrap 1.0.37 ii genisoimage 9:1.1.11-2 ii libwww-perl 6.02-1 ii pbuilder0.203 ii perl-modules5.12.4-4 ii python-dns 2.3.5-3 ii python-gnupginterface 0.3.2-9.1 ii python-soappy 0.12.0-4 ii reportbug 6.2.1 ii sbuild 0.62.5-1 Versions of packages ubuntu-dev-tools suggests: ii ipython0.10.2-1 ii python 2.7.2-8 ii python-simplejson 2.2.0-1 ii qemu-user-static 0.14.1+dfsg-3 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
