| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | msged feature :( |
Hi Kai! May 05 21:10 2015, Kai Richter wrote to Markus Reschke: KR> I noticed that because of your input to my netmail folder. ;-) Yep, it's really annoying. KR> Why do you want to move netmail to another area? KR> In most cases it's for archiving, not for processing. I got several netmail areas for different tasks, like areamgr for example. I've also set up a bunch of filter rules to sort incoming netmail to specific areas (similar to what procmail does for email). KR> So all archiv areas should have "LocalArea" as area definition. That would work for a archive type area. KR> I'd like to call it a configuration error of your destination mail KR> areas. ;-) Too simple ;) The current setup is intended. KR> Okok, now seriously. I think keeping flags as they are in any cases KR> is the best solution. They were sent into the network already and if KR> a resend in the destination area is wanted it could be done by the KR> areafix rescan function. I don't think that this would be a good idea when moving a message from a netmail area to an echomail area. The "crash" attribute wouldn't make much sense for an echomail. Therefor my idea was to keep the attributes when source and destination area are of the same type. Regards, Markus ---* Origin: *** theca tabellaria *** (2:240/1661) SEEN-BY: 11/201 34/999 90/1 116/18 120/331 123/500 128/187 135/364 140/1 SEEN-BY: 218/700 222/2 226/0 160 230/150 240/1120 249/303 250/1 261/38 100 SEEN-BY: 266/404 267/155 280/464 1027 282/1031 1056 292/907 908 320/119 SEEN-BY: 340/400 393/68 396/45 633/267 280 640/384 712/550 848 770/1 801/161 @PATH: 240/1661 1120 261/38 712/848 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™.