|
|
| Author |
Message |
| 25 new of 215 responses total. |
gelinas
|
|
response 125 of 215:
| 
May 5 02:56 UTC 2002 |
*three*? I'd be glad to get so few each day.
No, I can't upgade the Pine here; I've made no progress on procmail, either.
It looks like filtering was added by version 4.33, but I don't know when.
|
oval
|
|
response 126 of 215:
|
May 5 09:02 UTC 2002 |
but of you use procmail .. you CAN
|
remmers
|
|
response 127 of 215:
|
May 5 12:29 UTC 2002 |
Grex uses a non-standard hierarchical system for the location of
inboxes, and the version of procmail installed here isn't smart
enough to figure it out. But you can get procmail to work by
setting the MAIL variable explicitly in the .procmailrc file:
for example
MAIL=/var/spool/mail/g/e/gelinas
|
keesan
|
|
response 128 of 215:
|
May 5 14:05 UTC 2002 |
Remmers or oval, can you post a quick explanation of how to use procmail at
grex? I thought it was something I had to download. Do I have a .procmailrc
file? I would like to filter out anything coming from *stayhard@hotmail.com
as I got cstayhard and astayhard in the past 24 hours (with predictable
subject line). Is that possible?
|
jmsaul
|
|
response 129 of 215:
|
May 5 14:10 UTC 2002 |
It's even simple once you know how to use procmail.
|
rcurl
|
|
response 130 of 215:
|
May 5 18:43 UTC 2002 |
Is there a down side to using procmail?
|
keesan
|
|
response 131 of 215:
|
May 5 20:38 UTC 2002 |
Can procmail filter out any address that has stayhard@hotmail.com? Such as
astayhard, cstayhard, and today stayhdard? s?t?a?y?h?a?r?d?
The down side would be that you could not report this spam to hotmail.com as
you would never see it.
|
oval
|
|
response 132 of 215:
|
May 5 21:15 UTC 2002 |
you need to make these 2 files named .procmailrc and .forward in your home
directory.
the .procmailrc file could look like this:
MAILDIR=$HOME/mail
DEFAULT=$HOME/mail
SHELL=/bin/sh
LINEBUF=4096
LOGFILE=$HOME/.procmail/procmail.log (mkdir .procmail, touch
.procmail/procmail.log - CLEAN IT ONCE A MONTH)
LOG="--- Logging ${LOGFILE} 4 ${LOGNAME}, " (WILL GIVE add info procmail.log
file)
VERBOSE=off
PATH=(could someone fill this in?)
FORMAIL=/usr/local/bin/formail
SENDMAIL=/usr/lib/sendmail
* ^From.*stayhard@hotmail.com
/dev/null
look at the LOGFILE line. you will need to create the .procmail directory,
then touch the procmail.log file, the 2 commands are listed in parenthesis.
do not include them in you .procmailrc file. don't include any comments in
parenthesis. this will filter anything that says 'stayhard@hotmail.com' to
a blackhole of nothingness. you make one for the subject line too, and can
specify a 'spam' folder or something if you prefer that over /dev/null.
the .forward file i *think* will look like this:
"|IFS =' ';exec /usr/local/bin/procmail #[login name]" (include the quotes;
[login name] is your login name)
could someone fill in the PATH line above? i will test this out later. you
could also do a 'man procmail'.
welcome to the world of linux sindi! :) heh
|
keesan
|
|
response 133 of 215:
|
May 5 22:12 UTC 2002 |
I will try to extract this response and make it into a file, thanks.
What do you mean by 'touch'?
To also exclude stayhdard do I put *stay*h*a*r*d? The latest was trying to
sell something 'legal'.
So this will send spam to a folder that I clean out once in a while?
What is dev/nul?
|
gelinas
|
|
response 134 of 215:
|
May 6 00:16 UTC 2002 |
The latest version of procmail *does* understand grex's heirarchical mail
spool, and I've volunteered to build it, I just haven't yet. A few other
projects are beginning to come together, so I should be able to get back to
procmail RSN.
|
keesan
|
|
response 135 of 215:
|
May 6 00:57 UTC 2002 |
So I should wait until the latest version is at grex? Thanks for volunteering
- wish you could also upgrade PINE to filter mail as it sounds simpler.
MSN writes back that astayhard@msn.com is a forged address and they will
prosecute.
|
oval
|
|
response 136 of 215:
|
May 6 03:38 UTC 2002 |
sindi, you could put just *stayhard if you want.
touch will just make the procmail.log file. try it.
mkdir .procmail
touch .procmail/procmail.log
it's not even neccessary if you don't want a log..
/dev/null is the blackhole of nothingness.
|
keesan
|
|
response 137 of 215:
|
May 6 15:27 UTC 2002 |
So touch sends all the spam to one place where I can look at it?
I cannot just do *stayhard. Today I got satayhard@yahoo.com and also
stayhahrd@excite.com. Some are for Viagra, some for legal stuff, and they
are being routed through Poland and Korea. This is getting to be a sport,
maybe I don't want to filter them. Except I do get some normal mail
which I would like to read without being swamped by three spams
for each real mail (the recent ratio is gettin worse).
I think I still need PATH. Perhaps someone could post, in some readily
accessible file at grex, templates for creating the two needed files,
that everyone could use. Or even a little program that steers the user
through the needed changes (make it part of the Change program, like
password?).
Thanks for all the help and I hope I can take advantage of it soon.
|
remmers
|
|
response 138 of 215:
|
May 6 17:10 UTC 2002 |
Hm, incorporating procmail setup into "change" is a nice idea!
|
gull
|
|
response 139 of 215:
|
May 6 18:49 UTC 2002 |
Re #137: 'touch' is a program that creates zero-length files, or changes the
modification time of an existing file. That's all it does. In this case,
it's being used to create a logfile for procmail to append to, if I
understand correctly.
|
keesan
|
|
response 140 of 215:
|
May 6 19:10 UTC 2002 |
Remmers, do I hear you volunteering?
|
gull
|
|
response 141 of 215:
|
May 6 20:57 UTC 2002 |
Things are really slow, at the moment. Especially logins via ssh.
Load average is around 30, which is high, but I've seen it that high
without this kind of slowdown before.
|
gull
|
|
response 142 of 215:
|
May 6 21:02 UTC 2002 |
Also...and maybe this is a feature I just never noticed before...when I
telnetted in from my FreeBSD machine, Grex didn't ask for my username,
just my password. (It skipped straight to "gull's Password:") My
username is also 'gull' on that machine -- is telnet passing it
through, somehow?
|
remmers
|
|
response 143 of 215:
|
May 7 00:06 UTC 2002 |
Hm. That's standard behavior with ssh, but I've never encountered
it with telnet.
|
mdw
|
|
response 144 of 215:
|
May 7 00:48 UTC 2002 |
Some versions of telnet can do that. Most modern versions have a "-a"
flag that turns it on, or "set autologin" in .telnetrc can also turn it
on. I've also found versions where it defaults on - in theory it should
be possible to turn that *off*...
|
gelinas
|
|
response 145 of 215:
|
May 7 02:14 UTC 2002 |
I've only seen it with kerberised telnet.
|
mdw
|
|
response 146 of 215:
|
May 7 02:44 UTC 2002 |
I found it in debian telnet the other day. Luckily I had a k5 telnet
client that didn't have this annoying behavior.
|
mcnally
|
|
response 147 of 215:
|
May 7 03:33 UTC 2002 |
Was the spam from "satayhard" tips on how to cook Malaysian style?
|
mooncat
|
|
response 148 of 215:
|
May 7 17:44 UTC 2002 |
re #115- I chastised my cat about sending spam and Sasha has promised
not to send you, or anyone else, any more mail. Though, she's not sure
what all the fascination is about the whole internet thing, she just
likes the mice. ;)
re #117- Well, you should come meet my cat... she's a bit too fluffy to
be successfully creepy.
|
oval
|
|
response 149 of 215:
|
May 7 18:29 UTC 2002 |
good idea remmers.
i think you're not understanding me. i have yet to test what i posted, but
once i finally get around to it, i will email you the two text files. that's
all they are. 2 text file i will omit the logfile to simplify things.
|
