Article View: uk.comp.sys.mac
Article #374Re: Someone's using my address for spam
From: bogus address
Date: Thu, 09 Nov 2000 00:00
Date: Thu, 09 Nov 2000 00:00
58 lines
3431 bytes
3431 bytes
>> There is no >> way in Demon's present setup that I can bounce any message from a user >> who sent more than 1000 messages to the Demon server on the same day, >> for example. > And there's no way I'd want to, I don't give a fuck what *you* want, this is what *I* want out of a mail service. If you don't want to filter your mail nobody's forcing you to. > one of the mailing lists I use often has ~250 messages/day, and there > are a few other Demon users. This is nothing like any of the mailing lists I use, so your usage pattern is totally irrelevant to *my* requirements. > Since you're already rejecting mail to the most likely address > to be garnered from news at a minimal cost in bandwidth/CPU > what's the problem? I've been using mail and news since 1984, that's the problem. The toothpaste was already out of the tube before Canter & Siegel came along. > Remember to figure in the cost of designing, writing, testing and > implementing this extremely vague user requirement. User access to procmail is vague???? (The server site might want to put quotas on CPU used for filtering, or on access to security-sensitive data, but that's about the limit of their required involvement). > And the amount of hassle the helpdesk will get trying to get people > to configure it correctly, especially when someone ends up bouncing > all the mail they really want. This is a power-user feature. No helpdesk should be expected to support it. Since when did any sysadmin help people debug shell scripts? > I've posted to a fair miscellany of text newsgroups with basically > the same username for many years now, I only have to bounce a > handful of emails per day - and about half of them aren't to > the address that appears in my posts (hence auto-bounce), they're > either grabbed from the website, or are old addresses (a few > one-offs for particular purposes and a couple that have never been > used - unless someone forged it). All of which slow down your mail delivery with protocol overheads when you bounce them, and in Demon's case the delay can be dire. ========> Email to "jc" at this site; email to "bogus" will bounce. <======== Jack Campin: 11 Third Street, Newtongrange, Midlothian EH22 4PU; 0131 6604760 http://www.purr.demon.co.uk/purrhome.html food intolerance data and recipes, freeware logic fonts for the Macintosh, and Scots traditional music resources
Technical Details
Message-ID:
<6808@purr.demon.co.uk>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<021120000903373203%andy@dance.demon.co.uk> <6766@purr.demon.co.uk> <B627B4789668161576@cara.demon.co.uk> <01c04976$ab8a25a0$0500000a@nick> <slrn90jj01.dk3.news1@polka.redowa.co.uk> <6805@purr.demon.co.uk> <20001109.195011.9E9801DE.OBaa@pierrot.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc20b,f2cb002bbe07b056 X-Google-Attributes: gidfc20b,public X-Google-Thread: fad9d,6f04be2e26fee8d1 X-Google-Attributes: gidfad9d,public From: bogus@purr.demon.co.uk (bogus address) Subject: Re: Someone's using my address for spam Date: 2000/11/09 Message-ID: <6808@purr.demon.co.uk> X-Deja-AN: 691815866 Distribution: world X-NNTP-Posting-Host: purr.demon.co.uk:194.222.239.177 References: <021120000903373203%andy@dance.demon.co.uk> <6766@purr.demon.co.uk> <B627B4789668161576@cara.demon.co.uk> <01c04976$ab8a25a0$0500000a@nick> <slrn90jj01.dk3.news1@polka.redowa.co.uk> <6805@purr.demon.co.uk> <20001109.195011.9E9801DE.OBaa@pierrot.co.uk> X-Posting-Agent: MacSlurp 1.6d8 X-Complaints-To: abuse@demon.net X-Trace: news.demon.co.uk 973812396 nnrp-14:2655 NO-IDENT purr.demon.co.uk:194.222.239.177 Organization: The Biggest Fluff Mine in Midlothian Newsgroups: uk.comp.sys.mac,demon.service