home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 660 
 mark lewis to Roy Witt 
 Outbound not working... 
 01 Jan 70 00:00:00 
 
 MK>> It's possible that this has been answered already and I missed it.
 MK>> The only outbound that works with my irex and fastecho is netmail
 MK>> and mailbox directories.

 ml> ok... only outbound...

 RW> [????]

MK's second line quoted above... "the only outbound that works"...

 MK>> Everything else ends up in the appopriate directory but is never
 MK>> tossed.

 ml> hunh? tossed is for inbound traffic...

 RW> outbound doesn't get tossed? Really?

right... outbound is /scanned/ from the message bases... inbound is /tossed/
into the message bases...

 ml>  you were just talking about outbound... i'm confused :?

 MK>> I recieve just fine.  As a note, one of my email passwords was
 MK>> corrupted so I'm wondering if it would be a good idea to start
 MK>> from scratch.

 ml> irex has been known to get corrupted by looking at it sideways...

 RW> Could that be because it's the linux version? I've never seen a
 RW> corrupted windows version here and I've used Irex for at least 12,
 RW> maybe 15 years now. In fact, if you leave the configs alone once
 RW> they're working properly, Irex continues to run for weeks and
 RW> 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...

 ml> everyone i know that uses it gets their configs right and then makes
 ml> copies of them to put back in place the next time they get 
 ml> corrupted.

 RW> I don't, because there is no need.

hummm...

 ml> .. the real question is why do they get corrupted in the
 ml> first place... starting clean won't prevent the corruption from what
 ml> i've read over the years...

 RW> I had Irex stop working lately, but it was due to a switch being
 RW> changed that was the cause. It now sits in the 'tray' waiting for a
 RW> connect on the 24555 port that it is listening to. That won't
 RW> happen until I find the password to the router to make a change
 RW> there.

 :) good thing i changed it for ya, eh? O:)

)\/(ark

 * Origin:  (1:3634/12)

<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca