response 731 of 870:

Feb 14 17:51 UTC 2005

Any about cumshot refinancing?

response 733 of 870:

Feb 15 23:03 UTC 2005

I got there today.

My Cat5 cable contained two eight-conductor cables: one blue and one yellow.
I put an RJ-11 connector at each end of each of them (leaving four wires
unused in each cable) and put that in place of the separate telephone cords
we had been using.  So that part of the problem should be fixed.

I also plugged a telepone directly into the test jacks: one (0512) was dead,
and the other (0513) was so noisy that the telephone wouldn't dial through.
I called SBC from another line in the facility to report the problem.  They
promised by repair by tomorrow evening.  That should take care of the second
part of the problem.

Since only one line was working, 0513, and only tty00 has been used, I changed
the order of the modems so that 0512 would be on tty00 and 0513 would be on
tty01.  Now we wait for the lines to be fixed to see if I fixed that part of
the problem, as well.

response 735 of 870:

Feb 15 23:45 UTC 2005

My experience with SBC is that you should expect it to take several
tries to get a reliable line. Hopefully they'll do a better job for you,
though.

response 737 of 870:

Feb 16 00:09 UTC 2005

I've been out of town, and unable to telnet in, for several days.
Just now, when I logged in, I was told (quite understandably) that
my mailbox was full, and that I would not be able to receive any
more mail until I removed some of it.

So - wait for it - I tried to read my mail and was told that /tmp
was full, and my quota was exceeded!  

There is no way I can read any mail.

Would someone with a clue *puh-leez* increase the disk quotas for
mail so that I (and others) can read it?  Thanx!

response 739 of 870:

Feb 16 06:19 UTC 2005

Thanks Mark!

response 741 of 870:

Feb 16 18:04 UTC 2005

dpc is suffering the same thing I went through, until my /tmp quota was
increased.  Is this how it's going to be - one by one, affected users have
to ask for help to solve something they could have solved for themselves?

response 743 of 870:

Feb 16 18:33 UTC 2005

A short spam filter that catches about 75% of my spam - 
delete lines starting in #, which I put in for information only.

.forward (in home directory):

|/usr/local/bin/procmail

.procmailrc  (in home directory):

MAIL=/var/mail/yourlogin                ##change this!!!
LOGFILE=$HOME/mail/from 
VERBOSE=on

##The above sets your mail directory and produces a logfile
##with a list of what mail went where and why -- ~/mail/from
##which you can read with pine, L, as 'from'.  You can see if
##the filter caught a real mail and why, then either put the
##mailer on your white list or remove the filter that caught it.

## This first filter forwards mails over 100K to my other address.
:0:
* >100000
! keesan@myotheraddress.org

#The next two are 'white list', mail to be let through:
#Change from carole to the names of people who write you 
#if your filter catches their mail.  
:0:
* ^From:.*carole
$MAIL

#Change to subjects that you want to be sure not to accidentally filter
:0:
* ^Subject:.*ebay
$MAIL

#This filter lets through mail from people using pine.
:0:
* ^References:.*pine
$MAIL

#The following is a sample of how to filter on mails with word 
# 'filter' in message body and send them to mail folder filter.
# Useful if you want to save mail from a list.
:0B:
* ^*filter
${HOME}/mail/filter

#The rest of this throws out (to /dev/null) spam.

#All mail with java in it is spam.
:0:
* ^Content-type:.*java
/dev/null

#I don't know what this is, but it is always spam.
:0:
* ^X-Message-Info:
/dev/null

#All mail with embedded images is spam.
:0B:
* ^.*img.src
/dev/null

#All mail sent to these characters is spam, unless you are carson.
:0:
* ^To:.*benny
/dev/null

:0:
* ^To:.*carson
/dev/null

:0:
* ^From:.*carson
/dev/null

:0:
* ^To:.*cme
/dev/null

:0:
* ^To:.*gmike
/dev/null

:0:
* ^To:.*hal9000
/dev/null

:0:
* ^To:.*krex
/dev/null

:0:
* ^To:.*makji
/dev/null

:0:
* ^To:.*pez
/dev/null

:0:
* ^Cc:.*true
/dev/null

:0:
* ^Subject:.*medication
/dev/null

#perscription, prescripiton
:0:
* ^Subject:.*p..scrip..on
/dev/null

:0:
* ^Subject:.*\|
/dev/null

## The following lines (0B) filter on message bodies only:
##The first will catch cialis, c!ial1s, etc.

:0B:
* ^.*c.al.s
/dev/null

:0B:
* ^.*deals
/dev/null

:0B:
* ^.*medication
/dev/null

:0B:
* ^.*meds
/dev/null

#the . is any character, the ? means character before it is optional
# so this catches mortgage, mor.tg.agge etc.
:0B:
* ^*mor.?tg.?agg?e
/dev/null

:0B:
* ^.*pills
/dev/null

:0B:
* ^.*\%.rate
/dev/null

:0B:
* ^.*refinance
/dev/null

:0B:
* ^.*rx
/dev/null

:0B:
* ^.*s0ft
/dev/null


#leave the next line so real mail will arrive safely

:0:
$MAIL

response 745 of 870:

Feb 16 18:47 UTC 2005

That is why I started the filter with a section that forwards large mails to
some other address.  You could also just set the filter to send the large
mails to /dev/null if you don't have a forwarding address.  I added this
filter (with much help from mcnally) after a friend sent me a 700K photo
(which she following with 1.3 and 1.4MB).  See the line with 1000 in it.

response 747 of 870:

Feb 16 21:41 UTC 2005

SBC is at Provide.Net working on the lines now.  Apparently, the problem is
extensive; they hope to get it fixed tonight, but if they can't, they'll be
back on it first thing in the morning.

Right now, the lines are ringing open.

response 749 of 870:

Feb 16 22:45 UTC 2005

"Bad dates"

response 751 of 870:

Feb 17 01:42 UTC 2005

Thanks to whoever fixed my /tmp quota!

response 753 of 870:

Feb 17 04:43 UTC 2005

I note that there were a couple of connections on tty01 today, before SBC
took the lines down for repair.  So I did get the modems connected to the
'right' lines this time. :)