| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Trialing FMail/lnx status check-in |
Hi Paul, On 07 Sep 17 12:21, Paul Quinn wrote to Wilfred Van Velzen: about: "Re: Trialing FMail/lnx status check-in": PQ>>>> Ooh, ooh... now I have to do something... oh, no...! WvV>>> I'll stay tuned! ;) PQ> Well, I managed to screw up even some of the simplest things but PQ> eventually got something like a normal echomail scan out... PQ> GoldEd created the expected echomail.jam file, containing... PQ> --- 8< --- PQ> /opt/ftn/fido/msgbase/fec1e5dd 8020 PQ> --- 8< --- Is that the name of the jam area filenames (without the extensions)? Mine have more readable names. For instance when I reply to this message echomail.jam contains: /home/fido/jam/fido/fmailhelp 998 PQ> In the areas.bbs file that file is identified as... PQ> --- 8< --- PQ> !/opt/ftn/fido/msgbase/fec1e5dd WIN95 3:640/384 PQ> --- 8< --- PQ> Then a sendmail script called for a 'fmail scan' which scanned _every_ PQ> message area: netmail, HMB & then JAM. It seemed to completely ignore the PQ> echomail.jam file except when it came time to delete it. PQ> This was kinda awkward so I re-ran the same actions. Same result. Oops. PQ> ;-) PQ> There must have been something else that I missed? Do you have any PQ> suggestions, please? Do you run Golded and the sendmail script as the same linux user? Is that user also the owner of the echomail.jam file and the jam area files? What does the log say? Wilfred. --- FMail-W32 2.0.1.4* Origin: point{at}work (2:280/464.112) SEEN-BY: 103/705 154/10 203/0 229/426 240/5832 249/303 261/38 280/464 5003 SEEN-BY: 280/5555 292/624 854 310/31 423/120 633/0 267 280 281 412 640/384 SEEN-BY: 712/848 770/1 2320/100 @PATH: 280/464 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™.