Wichert Akkerman writes ("Re: debian-ctte mailing list and spam"):
> It runs from procmail, so basically:
> * receive the post on stdin
> * return accept/bounce flag via returncode
Blars Blarson writes ("Re: debian-ctte mailing list and spam"):
> * the system being used is heavily overloaded, so f
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>Previously Ian Jackson wrote:
>> As I say, I'm quite willing to help write/maintain software for this
>> kind of thing. If you tell me what the interface should look like
>> (ie, how it should expect to receive incoming mails and how it sho
Previously Ian Jackson wrote:
> As I say, I'm quite willing to help write/maintain software for this
> kind of thing. If you tell me what the interface should look like
> (ie, how it should expect to receive incoming mails and how it should
> send them on for actual posting) I'll get started strai
Pascal Hakim writes ("Re: debian-ctte mailing list and spam"):
> I take back what I said actually. The signature checker is very brittle,
> and it already stops a number of valid messages from people who want to
> post on the gpg-restricted lists such as debian-devel-annouce or
> debian-security-an
Pascal Hakim writes ("Re: debian-ctte mailing list and spam"):
> I still fail to see why this list needs different rules than all the
> others.
To put it most bluntly: the other lists have a bad situation too.
Speaking for myself, though, I don't have to follow all of those other
lists and read th
5 matches
Mail list logo
