|
|
| Author |
Message |
| 25 new of 293 responses total. |
mdw
|
|
response 84 of 293:
| 
Jan 17 22:02 UTC 2002 |
The mail forwarding was an unlucky combination of spam & anti-spam
duelling it out, with grex's mqueue being the battle ground. People
regularly set up giant mailing lists and forward them through grex, and
we delete them almost as regularly when we notice them -- usually
network lag gives them away. Lynx breaking is because I had to reboot
the machine the web proxy was running on, in order to get grex running
again, and didn't know that the web proxy doesn't (or didn't)
automatically restart. I understand it's fixed now, and it's not really
related to the e-mail fit, it was just there lurking to strike when
least expected, and I walked into it. I'm not sure why other ran out of
filespace; doesn't seem to be shortage just now and certainly /etc/motd
isn't that big.
|
janc
|
|
response 85 of 293:
|
Jan 18 01:10 UTC 2002 |
Re 83: Oops, I installed a new version of Backtalk today and didn't copy
over all the Grex configurations. I'll fix it.
|
other
|
|
response 86 of 293:
|
Jan 18 02:28 UTC 2002 |
Now getting a [ Cannot open file for writing ] error when updating /etc/motd.
|
gelinas
|
|
response 87 of 293:
|
Jan 18 04:52 UTC 2002 |
Uuhh...
} Respond, pass, forget, quit, or ? for more options? !ls -alF /etc/motd
} -rw-rw-r-- 1 mdw staff 421 Jan 17 23:05 /etc/motd
}
} Respond, pass, forget, quit, or ? for more options? !groups other
} other : people motd members voters usenet internet
Perhaps the 'group' of /etc/motd is wrong?
|
aruba
|
|
response 88 of 293:
|
Jan 18 05:56 UTC 2002 |
I think that's right. I put the board officers in the MOTD. I'm currently
in group staff, though, which is why I could do that.
|
other
|
|
response 89 of 293:
|
Jan 18 06:21 UTC 2002 |
Isn't /etc/motd supposed to be owned by group motd so that members of
group motd have write access to it?
|
gelinas
|
|
response 90 of 293:
|
Jan 18 06:23 UTC 2002 |
Which is right? That the wrong group is associated with /etc/motd, or that
the 'staff' group is associated with /etc/motd?
If 'staff' is the right group for /etc/motd, then what is the motd group for?
(Just out of curiousity, mind you. ;)
|
other
|
|
response 91 of 293:
|
Jan 18 06:41 UTC 2002 |
Well, the motd group is supposed to be the group of people who have write
access to /etc/motd. This group, for various reasons, is not equivalent to
staff.
|
gelinas
|
|
response 92 of 293:
|
Jan 18 06:46 UTC 2002 |
(#90 was in reply to #88; I didn't see #89 until after reading #91.)
|
slynne
|
|
response 93 of 293:
|
Jan 18 14:57 UTC 2002 |
re#85 Thanks man!
|
aruba
|
|
response 94 of 293:
|
Jan 18 15:20 UTC 2002 |
I believe /etc/motd should be owned by group motd. I will send mail to
staff about it.
|
remmers
|
|
response 95 of 293:
|
Jan 18 17:05 UTC 2002 |
Hm, I see that /etc/motd is now owned by group motd and writeable
by group, so somebody fixed it. Possibly Marcus, since mdw seems
to be the file owner now...
|
aruba
|
|
response 96 of 293:
|
Jan 18 23:44 UTC 2002 |
I sent mail to staff about it, and Valerie fixed it.
|
carson
|
|
response 97 of 293:
|
Jan 19 05:12 UTC 2002 |
I am curious to know if anyone else has been receiving multiple
unsolicited e-mail from a "Free Stuff Queens" list at this host.
Although I have indicated a willingness to file suit against the
owner of the domain, developingdots.com, and also have received
notice indicating my address has been unsubscribed, I continue
to receive multiple copies of the same unsolicited mail.
|
anderyn
|
|
response 98 of 293:
|
Jan 20 01:27 UTC 2002 |
This response has been erased.
|
tsty
|
|
response 99 of 293:
|
Jan 22 02:26 UTC 2002 |
pine config question ... while i prefer mail to pine (or
outlook express, eudora, etc.) there are times when attachments
are sent adn i use pine to handle that.
so, i created a different directory into which to send email that
needs pine's attention.
although pine does what i want, it starts with an error message
pine
bad context no '[' in context: /path/to/inbox
from setup (reflected in .pinerc)
personal-name = <No Value Set: using "TS Taylor">
user-domain = <Value is Fixed>
smtp-server = <No Value Set>
nntp-server = <No Value Set>
inbox-path = /a/t/s/tsty/pine/INBOX
folder-collections = /a/t/s/tsty/pine/
news-collections = <No Value Set>
incoming-archive-folders = <No Value Set>
pruned-folders = <No Value Set>
default-fcc = <No Value Set: using "">
default-saved-msg-folder = <No Value Set: using "saved-messages">
postponed-folder = <No Value Set: using "postponed-msgs">
read-message-folder = <No Value Set>
so, what is 'context' wehre is there aupposed to be '[' (the
open bracket) and how do i "set values" coreectly to change
(i guess) system defaults where 'using' "whatver" is not explicit?
|
gelinas
|
|
response 100 of 293:
|
Jan 22 02:33 UTC 2002 |
Well, here is what I see in my .pinerc:
} # List of directories where saved-message folders may be. First one is
} # the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
} # Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
} folder-collections=IMAP Server {g.imap.itd.umich.edu}mail/[],
} IFS home directory mail/[]
}
} # List, only needed if nntp-server not set, or news is on a different host
} # than used for NNTP posting. Examples: News *[] or News *{host3/nntp}[]
} # Syntax: optnl-label *{news-host/protocol}[]
} news-collections=
However, I don't see a way to set the [] in Config/Setup. Could be because
I'm looking at Pine 4.33
|
gelinas
|
|
response 101 of 293:
|
Jan 22 02:41 UTC 2002 |
TS, look at your .pinerc with less and with Pine's config
|
keesan
|
|
response 102 of 293:
|
Jan 22 21:16 UTC 2002 |
Why so slow right now?
|
gelinas
|
|
response 103 of 293:
|
Jan 22 22:19 UTC 2002 |
The usual culprits are 'load', which can be checked with the "uptime" command
(in picospan, !uptime at the nearest prompt), and 'network traffic', which
I've not found a way to check from grex (the usual tools are
disabled/restricted because of their usefulness to Bad Guys (TM)).
|
keesan
|
|
response 104 of 293:
|
Jan 22 22:50 UTC 2002 |
Fixed.
|
tsty
|
|
response 105 of 293:
|
Jan 23 16:31 UTC 2002 |
uhhh, re 100, 101 ... that looks like the um pine stuff although there
is some similarity. and , i *have* looked with both less and setup
NumerousTimes (tm) trying to figure this out.
does your .pinerc explicitly state:
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=IMAP Server {g.imap.itd.umich.edu}mail/[],
IFS home directory mail/[]
(the first-column braces are indent chars, i presume)
|
tsty
|
|
response 106 of 293:
|
Jan 23 16:34 UTC 2002 |
for the record, .pinerc states:
# Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
# Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
inbox-path=/a/t/s/tsty/pine/INBOX
###################### Collections, Folders, and Files #####################
# List of incoming msg folders besides INBOX, e.g. ={host2}inbox, {host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=
and there are no [] indicated anywhere ???????????????????
|
gelinas
|
|
response 107 of 293:
|
Jan 23 18:27 UTC 2002 |
Yup; that's a copy-and-paste from my current .pinerc. Here's what shows
on grex:
:r ~/.pinerc
# Updated by Pine(tm) 3.96, copyright 1989-1996 University of Washington.
#
# Pine configuration file -- customize as needed.
{Ellipsis. JLG.}
########################### Essential Parameters ###########################
# Over-rides your full name from Unix password file. Required for PC-Pine.
personal-name=
{Ellipsis. JLG.}
# Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
# Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
inbox-path=
###################### Collections, Folders, and Files #####################
# List of incoming msg folders besides INBOX, e.g. ={host2}inbox, {host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=
# List of directories where saved-message folders may be. First one is
# the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=
{Ellipsis. JLG.}
# List of context and folder pairs, delimited by a space, to be offered for
# pruning each month. For example: {host1}mail/[] mumble
pruned-folders=
# Over-rides default path for sent-mail folder, e.g. =old-mail (using first
# folder collection dir) or ={host2}sent-mail or ="" (to suppress saving).
# Default: sent-mail (Unix) or SENTMAIL.MTX (PC) in default folder collection.
default-fcc=
{Elision of remainder. JLG.}
That's all I know.
|
tsty
|
|
response 108 of 293:
|
Jan 24 04:45 UTC 2002 |
yeh, right, tha's how my grex pine STARTED. then i added the
explicit stuff ... adn get teh errors. your grex pine has NO customization.
was teh first example from um's pine?
|
