TIP: Click on subject to list as thread! ANSI
echo: fmail_help
to: Wilfred van Velzen
from: Nicholas Boel
date: 2017-08-15 19:13:26
subject: New test..

Hello Wilfred,

On Tue Aug 15 2017 08:29:26, Wilfred van Velzen wrote to Nicholas Boel:

 WV> I never had a problem with it. But you can look inside it with any
 WV> editor before you run 'fmail scan'. It's just a plain txt file.

Sure. It just has the location and filename (minus the extension) of the
JAM message base, and then the message number after it. There's nothing
wrong with the output, just that FMail sees it and deletes it without any
other messages as to why nothing was scanned out of it.

 WV> -S should. That option ignores echomail.jam, and scans every area for
 WV> unsend messages front to back.

Yes. That works as expected. Unfortunately at the moment it's the only way
that's working.

 WV> Maybe I need to add some more logging? ;)

Very possible! ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
SEEN-BY: 154/10 20 30 40 700 203/0 124 221/1 6 229/426 230/0 249/303 261/38
SEEN-BY: 266/404 280/464 5003 5006 5555 292/789 310/31 320/219 340/800 423/81
SEEN-BY: 633/0 267 280 281 412 640/384 712/848 770/1 2320/100 3634/12 5019/40
@PATH: 154/10 203/0 280/5555 712/848 633/280 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™.