HIding Areas {02}
[email protected] (Ingo Brueckl) Mon, 23 Jun 2003 19:47:00 +0200
| Newsgroups | gmane.mail.bluemail |
|---|---|
| Message-ID | <[email protected]> |
Bob Swift <[email protected]> writes: BS> The problem here (and I suspect with Sean's system as well), is that the BS> BBS is carrying the complete echomail backbone (well over 400 message BS> areas), however there's only a few that I actually follow. I see. BS> In BBBS, each user is allowed to "subscribe" to selected message areas, BS> and only those areas are scanned for new mail and such. It would be BS> great if BlueMail would either read and honor this "subscription" BS> information from BBBS, blueMail does this for all services ... but mail files/databases like the BBBS Message Base (and Hudson Message Base as well). The idea behind this is that while reading a mail file or database, you get full access to the whole file/database - no restrictions apply. For BBBS, in specific, you get the sysop configuration, who should probably be subscribed to all areas. BS> or (preferred because it is more generic and can be universally applied) BS> allow a separate list of the areas which should be displayed. Any areas BS> not on the subscription list would not appear in the list of areas (or BS> be processed in any way via BlueMail). I'll see whether this can be done. (For a more generic solution, there should be area filter file possible for every "system", i.e. every mail something blueMail can open, so the area filter files (.aff ?) should be named like bbbs.aff, hudson.aff, soup.aff, and probably be stored either in the INF or a separate directory, or the INF file itself.) And, you probably only want these .aff to be applied while reading, not when using the reply manager, don't you? (Which may be confusing.) I think, it'd best (not for me, but the user) if this could be controlled from within blueMail, for example with a tri-state "long/short/custom" area list... BS> (unless I "bastardize" the message area titles on the BBS to provide BS> some unique filtering criteria just for this purpose). Nobody should do this. >> I already though about adding a few input box macros (\0 ... \9). BS> I usually forget about using the defined macros and retype all the stuff BS> each time. Maybe \0 should bring up a list of the definitions of \1 ... \9 for selection? (No idea at the moment whether this easily can be done...) Ingo --bluemail----------------------------------------------------------- Post to the list by email to [email protected] To unsubscribe email [email protected] --POWERED BY MDAEMON!------------------------------------------------