You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-170    
 
Author Message
21 new of 170 responses total.
keesan
response 150 of 170: Mark Unseen   Dec 8 14:59 UTC 2001

For at least two days now it has been taking about 15 seconds or longer to
send mail with Pine, instead of the usual 1-2 seconds.  I get similar effects
when the internet connection is lost, but this time it is not lost.  Is this
something to do with the squid (proxy server)?
keesan
response 151 of 170: Mark Unseen   Dec 8 15:05 UTC 2001

Sending mail with mail takes 1/2 sec or less.  The Pine mails were replies,
which included headers of the received mails.  The mail mail was not.
keesan
response 152 of 170: Mark Unseen   Dec 8 18:44 UTC 2001

A mail sent with Pine that was not a reply also took about 15 seconds.
keesan
response 153 of 170: Mark Unseen   Dec 10 16:27 UTC 2001

Is there some way to access the PINE address book when using mail?
Or to send binary attachments without first having to manually run
them through uuencode?  This 15 sec delay per mail with PINE is rather
a waste of time.  
blaise
response 154 of 170: Mark Unseen   Dec 10 17:10 UTC 2001

The delay occurs with MUTT as well. No, there's no way to do either of those
with mail; mail is intentionally very featureless.  (Well, for the second,
you could write a script like: ~/bin/uumail
uuencode | mail -s "$2*" $1

Then you can use "uumail recipient subject of email < binaryfile" to send
binaryfile to recipient with a subject line of "subject of email".
gull
response 155 of 170: Mark Unseen   Dec 10 18:34 UTC 2001

You might try turning on the enable-background-sending option in Pine's 
configuration menu, if you're trying to speed up mail sending.
keesan
response 156 of 170: Mark Unseen   Dec 11 02:10 UTC 2001

Would that let me read the next mail while this one is waiting to be sent?
Anyone know why this problem (the 15 sec wait) just recently developed?
Where do I look for the option?
keesan
response 157 of 170: Mark Unseen   Dec 11 02:43 UTC 2001

I found the option but it does not seem to help - do I do anything other than
enable background sending?   If all else fails I may switch to m-net for my
mail ;=( as this is wasting quite a bit of time.
gull
response 158 of 170: Mark Unseen   Dec 11 04:19 UTC 2001

I wonder if DNS lookups are slow for some reason.  That would probably 
do it.  Maybe there's a nameserver not responding?
keesan
response 159 of 170: Mark Unseen   Dec 11 04:40 UTC 2001

Pine just now started sending things at normal speed again.  Why would mail
not also use a DNS lookup like Pine?
rcurl
response 160 of 170: Mark Unseen   Dec 11 06:08 UTC 2001

Strange that Sindi would be complaining about a leasurely e-mail service,
with her preferences for low tech.....  8^}
mooncat
response 161 of 170: Mark Unseen   Dec 11 13:30 UTC 2001

Is 15 seconds really that long of a time?
keesan
response 162 of 170: Mark Unseen   Dec 11 16:25 UTC 2001

When you are answering 5-10 emails in a row, yes, as it means you cannot do
anything else online while waiting.
Regarding speed, I would bet that the time from when I turn on my computer
to when I can read an email is shorter than it is for people using the latest
hardware and software to load Windows, dial their ISP, connect, and read an
email at 56K (or telnet to grex to read an email).   I dial in at 14.4K (when
are those faster modems likely to be installed?).  Our older computers with
less hardware and RAM boot faster than our newer ones.  What would speed
things up is tone instead of pulse dial ;=)
rcurl
response 163 of 170: Mark Unseen   Dec 11 17:08 UTC 2001

There are lots of things you can do while waiting on line. Read, draw,
cook, think.... I use two e-mail accounts and have them both open and
deal with them in turn (only one is on grex, and I  use them for
different parts of my life). In any case, compare that 15 seconds with
writing a letter with pen and paper.....
gelinas
response 164 of 170: Mark Unseen   Dec 11 19:08 UTC 2001

Re 157:  Sometimes, one must exit and restart pine for changes to take
effect.  I never remember when it is necessary and when it is not.
davel
response 165 of 170: Mark Unseen   Dec 13 23:47 UTC 2001

I'm sure by the time any staff person reads this it will be fixed, but I can't
look up any site outside Grex, & Grex is not very busy:
> Ok: !w
>   6:42pm  up 11 days, 19:41,  1 user,  load average: 0.24, 0.14, 0.02
> User     tty       login@  idle   JCPU   PCPU  what
> davel    ttyq9     6:36pm            3         w
> !

(In fact, I don't think I've ***ever*** seen Grex that unbusy.)     8-{)]
keesan
response 166 of 170: Mark Unseen   Dec 13 23:50 UTC 2001

I could not telnet for the past hour or so.
gelinas
response 167 of 170: Mark Unseen   Dec 14 00:24 UTC 2001

The Internet connection has been up and down since yestereve.  I don't know
why, of course.
jor
response 168 of 170: Mark Unseen   Dec 14 19:19 UTC 2001


/tmp: write failed, file system is full
Reading in /var/spool/mail/j/o/jor, message: 0
Write to "/tmp/mbox.jor" failed! [No space left on device]

janc
response 169 of 170: Mark Unseen   Dec 14 19:56 UTC 2001

Some dope was putting big files in /tmp and /d to fill them up.
gull
response 170 of 170: Mark Unseen   Dec 14 20:14 UTC 2001

I trust you dope slapped him/her?
 0-24   25-49   50-74   75-99   100-124   125-149   150-170    
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss