On 3/22/08, Rich Kulawiec wrote:
> My experience matches yours: I think we're all walking around with various
> (differing) lists of role mailbox names that we picked up over time.
> Do you think it'd be worth the effort to attempt to bring all those
> together, figure out which ones are worth
On Thu, Mar 20, 2008 at 10:56:07PM -0500, Brad Knowles wrote:
> On 3/20/08, Rich Kulawiec wrote:
>
> > (Incidentally, I'm not aware of any current effort to update RFC 2142.)
>
> Not any current efforts to update 2142, no. But there are other
> standard role mailbox names that I've seen used a
On 3/20/08, Rich Kulawiec wrote:
> (Incidentally, I'm not aware of any current effort to update RFC 2142.)
Not any current efforts to update 2142, no. But there are other
standard role mailbox names that I've seen used and recommended,
although I have not yet been able to locate a source for
On Wed, Mar 19, 2008 at 05:34:18PM -0500, Barry Warsaw wrote:
> On python.org this is postmaster. Do many sites split the
> responsibilities between mail and list care and feeding?
I know that some do, some don't; but beyond that, I don't have
much of a feel for how it's done across the 'net.
On 3/19/08, Rich Kulawiec wrote:
> While I'm blabbing about this, I'd like to float another idea
> related to RFC 2142. We have postmaster (mail), webmaster (web)
> and quite often hostmaster (DNS).
There's a hell of a lot more than that, and 2142 is not the only RFC
to be looking at for thi
On 3/19/08, Barry Warsaw wrote:
> On python.org this is postmaster. Do many sites split the
> responsibilities between mail and list care and feeding?
Some sites do, but on the ones I run I usually have a separate
listmaster and postmaster address anyway.
--
Brad Knowles <[EMAIL PROTECTED]>
Barry Warsaw writes:
> Do many sites split the responsibilities between mail and list
> care and feeding?
I suspect that it's pretty common in cases where people get a VMware
guest OS or soemthing like that. The hosting company / ISP is going
to want to keep close watch on port 25, but list an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 19, 2008, at 4:56 PM, Rich Kulawiec wrote:
> While I'm blabbing about this, I'd like to float another idea
> related to RFC 2142. We have postmaster (mail), webmaster (web)
> and quite often hostmaster (DNS). How about listmaster, which
> wou
On Mon, Mar 17, 2008 at 07:10:30PM -0700, Kenneth Porter wrote:
> Ok, thanks. It sounds like I can safely prune admin, subscribe,
> unsubscribe, join, and leave. That leaves bounces, confirm, owner, and
> request, which I can tolerate dealing with manually.
I certainly agree with keeping -reques
--On Monday, March 17, 2008 6:53 PM -0700 Mark Sapiro <[EMAIL PROTECTED]>
wrote:
> 'join' and 'leave' are synonyms for 'subscribe' and 'unsubscribe'. Jo
> Rhett would say you don't need any of these because nearly everyone
> uses the web. He might also say you don't need/want 'request' and
> 'con
Kenneth Porter wrote:
>I want to remove aliases from my mailman installation to avoid spam
>backscatter. Which aliases do I absolutely need?
>
>Here's a list from mm-handler:
>
>@ValidActions = qw(admin bounces confirm join leave
> owner request subscribe unsubscribe);
You do
I want to remove aliases from my mailman installation to avoid spam
backscatter. Which aliases do I absolutely need?
Here's a list from mm-handler:
@ValidActions = qw(admin bounces confirm join leave
owner request subscribe unsubscribe);
--
12 matches
Mail list logo
