| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Crunged ! |
-=> Quoting Dan Ceppa to Jean Parrot <=- JP> to an observant eye, I remembered that this is when that JP> happened before and NOT doing it now, saves my precious JP> replies. Since I deviated from that procedure, I have not had a JP> crunged packet again, in the last week or so. DC> Good! It's strange why it occurs when you edit your replies, DC> though. I know I've done that without a problem. JP> We are having fun. Even if I see no reason why this deleting JP> the mail would damage the replies. Things happen. ;-) DC> Could it be something that is supposed to delete your DC> messages when set that is causing the problem? DC> I know that when I send my messages that my *REP pack is DC> automatically deleted. Dan Having not used the OMX that you use I do not understand it's total function so do you use that to send your packets much like I use a comm program? I assume that you have closed BW before using this to transmit your mail reply (*.new in BW format) packet. Now I know your setup is different than getting and sending messages to a door like I do but I was just trying to compare the two ways. At one time I had a batch file that did my mail run. It was setup to move the reply packet and keep the last few until I could see that they made it out to the FIDO world. I was on a BBS at one time that sometimes did not do a good job of getting the reply packets processed thus my keeping them for retransmit if they did not get out. ... Ben ... Everytime I make my mark somebody paints the wall. ___ Blue Wave/DOS v2.30 --- Platinum Xpress/Win/WINServer v3.0pr5* Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140) SEEN-BY: 633/267 270 @PATH: 123/140 500 106/1 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.