[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: master's mail backlog and upgrade time



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 15 Nov 2005, at 2:34 pm, Steve Langasek wrote:

 * The mail backlog that `will never be able to be delivered' was
   (as far as I can tell) all spam that chiark has been properly
   rejecting.


No: there is nothing "proper" about rejecting mail from a host that you have
configured to forward mail for you.

I can see where you're coming from, but it's unavoidable, isn't it? Most of us probably have "accounts" which forward email to us, and over which we have no control; for example in my case I have two, one at debian.org, and one at Cambridge University (cantab.net), as well as any number of mailing lists. If those upstream sources are more lax about spam than the downstream SMTP receiver (whether chiark or something else) then this sort of thing is inevitable.

I happen to have a chiark account, and my chiark address is the primary one I use for Debian development (see the maintainer field for any of my packages, or indeed the address from which I post to Debian mailing lists like this one) so I have some personal interest in this particular issue.

It does seem it was a little hasty to have blanket-banned chiark- bound email, especially when it is well known that there are a significant number of DD's that use the machine.

I specifically use chiark for things as publicly visible as my Debian package maintenance address, news and mailing list postings, precisely *because* of its somewhat draconian anti-spam measures.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iQEVAwUBQ3tHZRypeFo2odvPAQKRoggAtoiXmeOkePAFtBsP8LDpniinK9a88VEx
OBrZtpk+yWmbMAX6y8Rifq2df62HDy4d2hTlBg26/bPXckhZiWhbIuJL8Ev1VxmI
hggQ1knqgUyKCuiEXmuLO/ueH2wCN+mzc9coFN+Nu4cVp6QQuuYZAP4Yz8oIm3DO
mFEw8N2lDRLJIbxg2RNHD71hkOtpHu9AGal1k0+GwDbLeVni4Wx4TxKXsRxD5bLV
D1bruCihwtXJIhHK2CornOW9fljsOc8IipO/43Rt3tB+ks+3g89LPZQVcCu8ZbWK
7Bx2EheaWC0STqSpJRGqMTCH2oxnS0PfPFsRf/i3zMS5YX+usuzBbA==
=9LTp
-----END PGP SIGNATURE-----



Reply to: