On 01 Jan 70 00:00, mark lewis wrote to Roy Witt:
It's possible that this has been answered already and I missed it.
The only outbound that works with my irex and fastecho is netmail
and mailbox directories.
ok... only outbound...
[????]
MK's second line quoted above... "the only outbound that works"...
Everything else ends up in the appopriate directory but is never
tossed.
hunh? tossed is for inbound traffic...
outbound doesn't get tossed? Really?
right... outbound is /scanned/ from the message bases... inbound is /tossed/ into the message bases...
Outbound is scanned and then 'tossed' into a zipped file here. Ok packed.
you were just talking about outbound... i'm confused :?
I recieve just fine. As a note, one of my email passwords was
corrupted so I'm wondering if it would be a good idea to start
from scratch.
irex has been known to get corrupted by looking at it sideways...
Could that be because it's the linux version? I've never seen a
corrupted windows version here and I've used Irex for at least 12,
maybe 15 years now. In fact, if you leave the configs alone once
they're working properly, Irex continues to run for weeks and
months without interuption.
i don't know what flavors the hundreds of complaints over the years
have spoken about... i do seem to recall you having problems at one
point and having to put a backup of your configs in place...
I don't keep backups...never have. Sometimes I wish that I had, but
chasing the problem and fixing it makes for more familiarity with the program...I did have to re-install it once, but that was due to a HD
crash. Fortunately, I had a tendency to keep links and passwords in a text
file for just such a purpose.
everyone i know that uses it gets their configs right and then makes
copies of them to put back in place the next time they get
corrupted.
I don't, because there is no need.
hummm...
.. the real question is why do they get corrupted in the
first place... starting clean won't prevent the corruption from what
i've read over the years...
I had Irex stop working lately, but it was due to a switch being
changed that was the cause. It now sits in the 'tray' waiting for a
connect on the 24555 port that it is listening to. That won't
happen until I find the password to the router to make a change
there.
:) good thing i changed it for ya, eh? O:)
Nobody could have done that. That password is tucked away in a secure and encrypted file and only the re-installation of the program that wrote it
can bring it back. I'm debating that, since the only need for it now is to
look up those websites and passwords and write them into a text file. The program was incompatable and obsoleted by Firefox over two years ago.
Hate mongers and morons, get your coffee and keyboards ready. -- R\%/itt
--- GoldED+/W32
* Origin: Texas Lone-Star - Texan, American, USAian (1:387/22)