|
Grex > Coop7 > #117: mail abuse and membership | |
|
| Author |
Message |
| 23 new of 72 responses total. |
lilmo
|
|
response 50 of 72:
|
Nov 10 03:44 UTC 1995 |
Just so we're clear, srw, are you saying that TS is getting special treatment,
and his treatment should be changed to conform with the norm, or that the
treatment TS is receiving currently should become the norm?
|
srw
|
|
response 51 of 72:
|
Nov 10 06:31 UTC 1995 |
The former. We can't allow people to let their mailboxes get that large
until we repartition /var/spool/mail. THat will happen when we move to
the Sun-4, but until then mail will get moved out of the spool
when it gets too large. This policy applies to everyone. (or should)
|
scott
|
|
response 52 of 72:
|
Nov 10 12:13 UTC 1995 |
Hmm... Without being nosy, just how big is it?
|
remmers
|
|
response 53 of 72:
|
Nov 10 12:50 UTC 1995 |
Anybody can see the size of anybody else's incoming mailbox: Just
type
!ls -ln /var/spool/mail/LOGIN
replacing "LOGIN" by the login id of the user you're interested in.
The number in the 5th field is the number of characters in the
mailbox.
|
popcorn
|
|
response 54 of 72:
|
Nov 10 14:13 UTC 1995 |
TS's mailbox isn't on the list of top offenders right now. It was in the
650-800K range last time there was a problem.
|
tsty
|
|
response 55 of 72:
|
Nov 20 08:19 UTC 1995 |
it does get cleaned up. As the Internet "burps," shit happens. Some months
the bounces are huge; some months, minsicule. Same addresses, different
results - shit happens, i deal with it. Many time the bounces are larger
than the original (different email daemons, etc.).
scott's #45 is about right, as i see it.
i have NOT requested "special treatment," rather, i HAVE suggested a
different approach to the problem - and no one can say that +i+ don't
recognize the problem - what i don't want to recognize is the relatively
high-handed *approach* to the solution. I think the current *approach* to
the problem is NOT in the best interests of Grex's persona or reputation
or reputed civility.
the "preferred" approach, from my pov, IS going to take some more work than is
being invested at the moment. It's the same sort of difference as between
carving a cow with a scaple instead of a chain-saw. Better results; more
investment of skill(s).
chain-saw approaches ought to be reserved for a different level of grief, imo.
|
scg
|
|
response 56 of 72:
|
Nov 20 08:26 UTC 1995 |
Where do you propose that more staff time to handle this comes from.
|
popcorn
|
|
response 57 of 72:
|
Nov 20 11:40 UTC 1995 |
I still don't agree that moving big mail files from the mail spool to people's
home directories is a "chainsaw" type of approach. I *do* think it already
takes up too much staff time as it is.
|
davel
|
|
response 58 of 72:
|
Nov 20 22:13 UTC 1995 |
Agreed.
|
tsty
|
|
response 59 of 72:
|
Nov 21 07:09 UTC 1995 |
moving them FIRST and following upn with an "oh, by the way ..." is documented
as the "grex method." Never have i suggested that "moving" would not be
an appropriate action. However, as a FIRST action, it borders on uncivil and
my reaction (which probably generated some angst) was equal to the initiating
event. Some surprizes are extremely grief producing.
Shoot first and ask questions later is a close analogy. Gnu slingers
should be reserved for the greater level of system grief.
|
tsty
|
|
response 60 of 72:
|
Nov 21 07:12 UTC 1995 |
Oh, lilmo's question in #50 is good. I agree with the latter option. As
popcorn can relate, almost every time (?95%), upon some communication
i get the thing down within a few hours. I do appreciate the consideration
and i believe it should be the norm, notthe exception.
|
popcorn
|
|
response 61 of 72:
|
Nov 21 13:03 UTC 1995 |
When I move people's mail, it's because if I don't, the mail spool is going
to fill up within a few hours, causing *everybody's* mail to bounce. Most
people don't respond at all to a request to reduce their mail size. In my
experience, TS, it takes you between 3 days and a week from the time I send
you e-mail asking you to trim down your mailbox until the time you go ahead
and do it.
I don't see where moving big mail files is a drastic act. For one, that mail
is still available to you -- it's not like it's been deleted, just moved.
For another, most people who have 600K of mail dumped on them aren't going
to be able to read it all at once anyway. That's a *lot* of reading material!
I'd guess that most of it just gets deleted, unread, anyway.
|
tsty
|
|
response 62 of 72:
|
Nov 22 05:25 UTC 1995 |
Bad guess in my case - remember what i *have* to do with it, fix it. I ought
to be postmaster for all the work i do. It gets easier ...
It has also take n me les tahn 3 hours to cut it down. And ...you couldn't ever
se the the stuf i take care of before you take a peek. With the current
sitaution, most often i +know+ stuff is gonna happen adn get online to take
care of it almost in real time. Not always, but most of the ti.me.
|
scg
|
|
response 63 of 72:
|
Nov 24 03:26 UTC 1995 |
re 59:
I like the idea of "Gnu slingers." ;)
|
tsty
|
|
response 64 of 72:
|
Nov 24 07:33 UTC 1995 |
<< i wondered if anyone would catch that .....<g> >>
btw, the content had inadvertantly degenerated off topic, drift-bit by
drift-bit.
may we reset the bits here?
|
lilmo
|
|
response 65 of 72:
|
Nov 27 04:25 UTC 1995 |
would it be possible to set up a daemon that would send warnings as mail
spools reached some specified fraction of a given "acceptable" level?
|
robh
|
|
response 66 of 72:
|
Nov 27 11:29 UTC 1995 |
And how would it send the warnings? Send them more mail? >8)
|
lilmo
|
|
response 67 of 72:
|
Dec 1 17:53 UTC 1995 |
How much is a 2-line message going to build up the spool???
|
steve
|
|
response 68 of 72:
|
Dec 1 21:21 UTC 1995 |
Not much. But it could add up over time. I just sent a one byte
piece of mail to myself ("h"), and after the headers were inserted,
that mail became 330 bytes. So a single message isn't much. They do
add up over time.
|
popcorn
|
|
response 69 of 72:
|
Dec 3 17:28 UTC 1995 |
Of course, once Marcus's sendmail changes are added, this whole mail moving
thing should become unnecessary. I'm very much looking forward to that!
|
lilmo
|
|
response 70 of 72:
|
Dec 9 05:55 UTC 1995 |
Is there an ETA for these changes?
|
srw
|
|
response 71 of 72:
|
Dec 9 17:29 UTC 1995 |
He just needs to get the opportunity to do the work of installing the
modifications. We can't use an ETA, because it is a matter of freeing up the
time and having the priority be high enough.
|
lilmo
|
|
response 72 of 72:
|
Dec 11 06:43 UTC 1995 |
OK, just curious.
|