gfengstad@laconn.fidonet.org (Grant Fengstad) (03/31/89)
* Original: FROM.....Grant Fengstad (134/104) * Original: TO.......All (134/104) * Forwarded by.......OPUS 134/104 I'm looking for assistance from anyone out there that has run into this problem before or that can assist me. I'm trying to compile a BBS program designed to run under Unix System V or SCO Xenix called XBBS. I'm running Unix System V 3.5 on an AT&T 3B1 and also have the Utilities/Developement Set V3.5. I've compiled the code (.c files) to object code. The problem appears to happen during the link phase. It aborts and give me this error: undefined symbol first referenced in file opendir bbscconf.o readdir bbscconf.o closedir bbscconf.o ld fatal: Symbol referencing errors. No output written to bbsc1 *** Error code 13 The problem as I understand it is correctable. The symbols are apparently a Berkley enhancement. It is also my understanding that there is a PD program for Unix System V to emulate/solve this problem. Can anyone help? Thanks Grant Fengstad -- Grant Fengstad - via FidoNet node 1:134/104 UUCP: ...!calgary!xenlink!laconn!gfengstad ARPA: gfengstad@laconn.fidonet.org
simstim@milton.acs.washington.edu ([]) (02/12/90)
I have been experiencing a little problem with various individuals sending me a substansial amount of unwanted email. Does anyone have a good hack to refuse email from particular users? The system is a Sequent S-81 running Dynix. I use the default BSD mail system. Please email me direct with the responses. Thanks. - Steve simstim@milton.u.washington.edu
jc@minya.UUCP (John Chambers) (02/13/90)
In article <1856@milton.acs.washington.edu>, simstim@milton.acs.washington.edu ([]) writes: > I have been experiencing a little problem with various individuals > sending me a substansial amount of unwanted email. Does anyone have > a good hack to refuse email from particular users? Some time ago I implemented a rather neat hack (if I may say so) that solved such problems in an interesting way. I converted incoming mail from several mailers into news, so that, for instance, my mail was sent to the to.jc newsgroup, which was at the head of my .newsrc file. The news directory was owned by the user, read/write by the user and the news group, and write-only to the rest of the world. The rn users especially liked this hack; it meant that their kill file could be used to ignore mail from known junk-mail sources, occasionally including much of the local bureaucracy. Of course, I didn't carry the code away with me. I've occasionally wished I had, given the klutzy mailers on most systems. On the other hand, it wouldn't be hard to do it again. Go ahead... (Let's see, there's gotta be some problem with this approach; else why are mailers and news kept apart everywhere? I assume someone will tell me why this is an idiotic idea. ;-) -- John Chambers ...!{harvard,ima,mit-eddie}!minya!jc [Sorry, no clever saying today.]
chip@tct.uucp (Chip Salzenberg) (02/15/90)
According to simstim@milton.acs.washington.edu ([]): >I have been experiencing a little problem with various individuals >sending me a substansial amount of unwanted email. Does anyone have >a good hack to refuse email from particular users? Sure. Use my Deliver program (currently at 2.0 patch 5; patch 6 out soon). Delivery files are shell scripts which control delivery of each message. A good one for filtering unwanted users is: : u="$1" from="`header -f from $HEADER`" # Kill mail from junk mail sources. case "$from" in *bozo@bozosite* ) echo DROP; exit ;; *kludge@hacksite* ) echo DROP; exit ;; esac # Oh goody, we keep it. echo "$u" Deliver 2.0, at finer archive sites everywhere. Not Just Another Deliver Hacker, -- Chip Salzenberg at ComDev/TCT <chip@tct.uucp>, <uunet!ateng!tct!chip> "The Usenet, in a very real sense, does not exist."