|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
postgrey - propagating fix for #504382 to lennyHello,
It seems that my upload of $SUBJECT to etch-volatile [1] was never processed, however I'd like to try and upload the fix to lenny-volatile. How about the following interdiff: --- postgrey-1.31/debian/postgrey_whitelist_clients.md5sum +++ postgrey-1.31/debian/postgrey_whitelist_clients.md5sum @@ -16,0 +17 @@ +2247add5c3a80cba6b97d44dc1c8635c 1.31-3.1/postgrey_whitelist_clients --- postgrey-1.31/postgrey_whitelist_clients +++ postgrey-1.31/postgrey_whitelist_clients @@ -12,8 +12,6 @@ # greylisting.org: Southwest Airlines (unique sender, no retry) southwest.com -# greylisting.org: Yahoo Groups servers (no retry) -scd.yahoo.com # greylisting.org: isp.belgacom.be (wierd retry pattern) isp.belgacom.be # greylisting.org: Ameritrade (no retry) @@ -158,6 +156,8 @@ registrarmail.net # google.com (big pool, reported by Matthias Dyer) /^.*-out-.*\.google\.com$/ +# see Debian #504382 (Marcin Owsiany) +/^mail.*\.google\.com$/ # orange.fr (big pool, reported by Lo�c Le Loarer) /^smtp\d+\.orange\.fr$/ # citigroup.com (slow retry, reported by Michael Monnerie) @@ -188,2 +188,16 @@ -# 2008-07-18: large pool, reported by Peter Samuelson -/^mxphxpool\d+\.ebay\.com$/ +# 2007-09-07: nrl.navy.mil (no retry, reported by Axel Beckert) +nrl.navy.mil +# 2007-10-18: aliplast.com (long retry, reported by Johannes Feigl) +mail.aliplast.com +# 2007-10-18: inode.at (long retry, reported by Johannes Feigl) +/^mx\d+\..*\.inode\.at$/ +# 2008-02-01: bol.com (no retry, reported by Frank Breedijk) +/^.*?.server.arvato-systems.de$/ +# 2008-06-05: registeredsite.com (no retry, reported by Fred Kilbourn) +/^(?:mail|fallback-mx)\d+.atl.registeredsite.com$/ +# 2008-07-17: mahidol.ac.th (no retry, reported by Alex Beckert) +saturn.mahidol.ac.th +# 2008-07-18: ebay.com (big pool, reported by Peter Samuelson) +ebay.com +# 2008-07-22: yahoo.com (big pool, reported by Juan Alonso) +yahoo.com --- postgrey-1.31/debian/changelog +++ postgrey-1.31/debian/changelog @@ -1,3 +1,13 @@ +postgrey (1.31-3.1) lenny-volatile; urgency=medium + + * updated whitelist by mostly taking it from 1.32-3. The differences from + upstream 1.32 are: + - the Debian-related entries + - widened google whitelist entry (closes: #504382) + * added the current whitelist hash to its md5sum file + + -- Marcin Owsiany <porridge@...> Sat, 06 Jun 2009 09:20:30 +0100 + postgrey (1.31-3) unstable; urgency=low * added eBay whitelist entry (reported by peterS) and the following VUA text: postgrey 1.31-3.1 provides an updated clients whitelist. Several new organizations' addresses were added, as well as updated entries for Google and Yahoo. Also, can someone confirm that I should build with "-sa" to get the orig tarball included in the upload? 1. http://lists.debian.org/debian-volatile/2009/01/msg00000.html -- Marcin Owsiany <porridge@...> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 |
|
|
Re: postgrey - propagating fix for #504382 to lennyHi Marcin,
Thanks for your efforts; sorry I let things slide recently wrt postgrey. I have recently decided to and postgrey over to a new packaging team which now forming on alioth. This is mostly FYI (and to get the new packagers in the loop on this); the upload to volatile is IMO not affected and should just be approved. cheers -- vbi On Saturday 06 June 2009 10.40:52 Marcin Owsiany wrote: > Hello, > > It seems that my upload of $SUBJECT to etch-volatile [1] was never > processed, however I'd like to try and upload the fix to lenny-volatile. > > How about the following interdiff: > > --- postgrey-1.31/debian/postgrey_whitelist_clients.md5sum > +++ postgrey-1.31/debian/postgrey_whitelist_clients.md5sum > @@ -16,0 +17 @@ > +2247add5c3a80cba6b97d44dc1c8635c 1.31-3.1/postgrey_whitelist_clients > --- postgrey-1.31/postgrey_whitelist_clients > +++ postgrey-1.31/postgrey_whitelist_clients > @@ -12,8 +12,6 @@ > > # greylisting.org: Southwest Airlines (unique sender, no retry) > southwest.com > -# greylisting.org: Yahoo Groups servers (no retry) > -scd.yahoo.com > # greylisting.org: isp.belgacom.be (wierd retry pattern) > isp.belgacom.be > # greylisting.org: Ameritrade (no retry) > @@ -158,6 +156,8 @@ > registrarmail.net > # google.com (big pool, reported by Matthias Dyer) > /^.*-out-.*\.google\.com$/ > +# see Debian #504382 (Marcin Owsiany) > +/^mail.*\.google\.com$/ > # orange.fr (big pool, reported by Lo�c Le Loarer) > /^smtp\d+\.orange\.fr$/ > # citigroup.com (slow retry, reported by Michael Monnerie) > @@ -188,2 +188,16 @@ > -# 2008-07-18: large pool, reported by Peter Samuelson > -/^mxphxpool\d+\.ebay\.com$/ > +# 2007-09-07: nrl.navy.mil (no retry, reported by Axel Beckert) > +nrl.navy.mil > +# 2007-10-18: aliplast.com (long retry, reported by Johannes Feigl) > +mail.aliplast.com > +# 2007-10-18: inode.at (long retry, reported by Johannes Feigl) > +/^mx\d+\..*\.inode\.at$/ > +# 2008-02-01: bol.com (no retry, reported by Frank Breedijk) > +/^.*?.server.arvato-systems.de$/ > +# 2008-06-05: registeredsite.com (no retry, reported by Fred Kilbourn) > +/^(?:mail|fallback-mx)\d+.atl.registeredsite.com$/ > +# 2008-07-17: mahidol.ac.th (no retry, reported by Alex Beckert) > +saturn.mahidol.ac.th > +# 2008-07-18: ebay.com (big pool, reported by Peter Samuelson) > +ebay.com > +# 2008-07-22: yahoo.com (big pool, reported by Juan Alonso) > +yahoo.com > --- postgrey-1.31/debian/changelog > +++ postgrey-1.31/debian/changelog > @@ -1,3 +1,13 @@ > +postgrey (1.31-3.1) lenny-volatile; urgency=medium > + > + * updated whitelist by mostly taking it from 1.32-3. The differences > from + upstream 1.32 are: > + - the Debian-related entries > + - widened google whitelist entry (closes: #504382) > + * added the current whitelist hash to its md5sum file > + > + -- Marcin Owsiany <porridge@...> Sat, 06 Jun 2009 09:20:30 > +0100 + > postgrey (1.31-3) unstable; urgency=low > > * added eBay whitelist entry (reported by peterS) > > and the following VUA text: > > postgrey 1.31-3.1 provides an updated clients whitelist. Several new > organizations' addresses were added, as well as updated entries for > Google and Yahoo. > > Also, can someone confirm that I should build with "-sa" to get the orig > tarball included in the upload? > > 1. http://lists.debian.org/debian-volatile/2009/01/msg00000.html [Patent attorney] Michael Muerer made the claim that almost every industry in the US would be better off if the patent system were to be abolished; in other words, patents serve as a net drain on the industry. -- http://lwn.net/Articles/324675/ |
|
|
Re: postgrey - propagating fix for #504382 to lennyOn Sat, Jun 06, 2009 at 09:40:52AM +0100, Marcin Owsiany wrote:
> It seems that my upload of $SUBJECT to etch-volatile [1] was never > processed, however I'd like to try and upload the fix to lenny-volatile. Ping! As per the package inclusion policy I'm still waiting for acceptance the debian-volatile list. -- Marcin Owsiany <porridge@...> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to debian-volatile-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: postgrey - propagating fix for #504382 to lennyOn Sat, Jun 06, 2009 at 09:40:52AM +0100, Marcin Owsiany wrote:
> It seems that my upload of $SUBJECT to etch-volatile [1] was never > processed, however I'd like to try and upload the fix to lenny-volatile. Please go ahead. I'd also say that it would make sense to fix this in a Lenny point release, no? > Also, can someone confirm that I should build with "-sa" to get the orig > tarball included in the upload? Yes. Kind regards, Philipp Kern -- .''`. Philipp Kern Debian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:phil@... Wanna-Build Admin `- finger pkern/key@... |
|
|
Re: postgrey - propagating fix for #504382 to lennyOn Sun, Jun 14, 2009 at 05:48:47PM +0200, Philipp Kern wrote:
> On Sat, Jun 06, 2009 at 09:40:52AM +0100, Marcin Owsiany wrote: > > It seems that my upload of $SUBJECT to etch-volatile [1] was never > > processed, however I'd like to try and upload the fix to lenny-volatile. > > Please go ahead. I'd also say that it would make sense to fix this in a > Lenny point release, no? Me too, not sure about the release team, though. It does not meet any of the criteria in http://www.debian.org/releases/proposed-updates... But I can do an upload if it will be accepted. Attaching the interdiff for release team's convenience. > > Also, can someone confirm that I should build with "-sa" to get the orig > > tarball included in the upload? > > Yes. OK, I have uploaded to lenny-volatile. -- Marcin Owsiany <porridge@...> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 diff -u postgrey-1.31/postgrey_whitelist_clients postgrey-1.31/postgrey_whitelist_clients --- postgrey-1.31/postgrey_whitelist_clients +++ postgrey-1.31/postgrey_whitelist_clients @@ -12,8 +12,6 @@ # greylisting.org: Southwest Airlines (unique sender, no retry) southwest.com -# greylisting.org: Yahoo Groups servers (no retry) -scd.yahoo.com # greylisting.org: isp.belgacom.be (wierd retry pattern) isp.belgacom.be # greylisting.org: Ameritrade (no retry) @@ -158,6 +156,8 @@ registrarmail.net # google.com (big pool, reported by Matthias Dyer) /^.*-out-.*\.google\.com$/ +# see Debian #504382 (Marcin Owsiany) +/^mail.*\.google\.com$/ # orange.fr (big pool, reported by Lo�c Le Loarer) /^smtp\d+\.orange\.fr$/ # citigroup.com (slow retry, reported by Michael Monnerie) @@ -188,2 +188,16 @@ -# 2008-07-18: large pool, reported by Peter Samuelson -/^mxphxpool\d+\.ebay\.com$/ +# 2007-09-07: nrl.navy.mil (no retry, reported by Axel Beckert) +nrl.navy.mil +# 2007-10-18: aliplast.com (long retry, reported by Johannes Feigl) +mail.aliplast.com +# 2007-10-18: inode.at (long retry, reported by Johannes Feigl) +/^mx\d+\..*\.inode\.at$/ +# 2008-02-01: bol.com (no retry, reported by Frank Breedijk) +/^.*?.server.arvato-systems.de$/ +# 2008-06-05: registeredsite.com (no retry, reported by Fred Kilbourn) +/^(?:mail|fallback-mx)\d+.atl.registeredsite.com$/ +# 2008-07-17: mahidol.ac.th (no retry, reported by Alex Beckert) +saturn.mahidol.ac.th +# 2008-07-18: ebay.com (big pool, reported by Peter Samuelson) +ebay.com +# 2008-07-22: yahoo.com (big pool, reported by Juan Alonso) +yahoo.com diff -u postgrey-1.31/debian/postgrey_whitelist_clients.md5sum postgrey-1.31/debian/postgrey_whitelist_clients.md5sum --- postgrey-1.31/debian/postgrey_whitelist_clients.md5sum +++ postgrey-1.31/debian/postgrey_whitelist_clients.md5sum @@ -16,0 +17 @@ +2247add5c3a80cba6b97d44dc1c8635c 1.31-3.1/postgrey_whitelist_clients diff -u postgrey-1.31/debian/changelog postgrey-1.31/debian/changelog --- postgrey-1.31/debian/changelog +++ postgrey-1.31/debian/changelog @@ -1,3 +1,13 @@ +postgrey (1.31-3.1) lenny-volatile; urgency=medium + + * updated whitelist by mostly taking it from 1.32-3. The differences from + upstream 1.32 are: + - the Debian-related entries + - widened google whitelist entry (closes: #504382) + * added the current whitelist hash to its md5sum file + + -- Marcin Owsiany <porridge@...> Sat, 06 Jun 2009 09:20:30 +0100 + postgrey (1.31-3) unstable; urgency=low * added eBay whitelist entry (reported by peterS) |
|
|
Re: postgrey - propagating fix for #504382 to lennyMarcin Owsiany wrote:
> On Sun, Jun 14, 2009 at 05:48:47PM +0200, Philipp Kern wrote: >> On Sat, Jun 06, 2009 at 09:40:52AM +0100, Marcin Owsiany wrote: >>> It seems that my upload of $SUBJECT to etch-volatile [1] was never >>> processed, however I'd like to try and upload the fix to lenny-volatile. >> Please go ahead. I'd also say that it would make sense to fix this in a >> Lenny point release, no? > > Me too, not sure about the release team, though. It does not meet any of > the criteria in http://www.debian.org/releases/proposed-updates... > But I can do an upload if it will be accepted. Hmm, you're replying to a Stable Release Manager... so please upload to proposed-updates. Cheers Luk -- To UNSUBSCRIBE, email to debian-volatile-request@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
| Free embeddable forum powered by Nabble | Forum Help |