multimail-user Mailing List for MultiMail Offline Reader (Page 2)
Brought to you by:
wmcbrine
Menu
▾
▴
multimail-user
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
(2) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(1) |
Feb
(5) |
Mar
(1) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(13) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: William M. <wmc...@us...> - 2001-10-17 13:13:57
|
There's not a lot new in 0.41 (mostly bug fixes), but the command-line options are pretty interesting. Until now, it's been hard to change MultiMail options on a temporary basis -- you'd pretty much have to edit the config file each time. And it wasn't convenient to try and maintain multiple config files, since the only way to point mm at an alternate file was to set the MMAIL environment variable, which points at a directory rather than a file. Now, instead, if you just want to change a single option for a single session, it's easy. For example, to load a different color scheme: mm -colorfile c:\mmail\aqua.col (Note the use of the full path; this won't work without it.) Or to temporarily turn off *.NDX files for a troublesome QWK packet: mm -ignorendx yes badpacket.qwk You can also experiment more freely with all the options this way, before deciding on permanent settings. If you want multiple configurations, you can effectively do it via a batch file or script that calls mm with the appropriate options. For example, I have a script with options set for using MultiMail to post to binary newsgroups, which says, in part: mm --zipCompressCommand "zip -0jkq" --UseTaglines No --AutoSaveReplies No -- William McBrine <wmc...@us...> |
|
From: William M. <wmc...@us...> - 2001-08-08 18:24:26
|
Please don't post this sort of thing to the MultiMail discussion list. -- William McBrine <wmc...@us...> |
|
From: tony s. <tsu...@ho...> - 2001-08-08 11:20:18
|
>> > > > > > Subject: Small hole >> > > > > > > >> > > > > > > A guy walks in to a bar with his pet monkey. He >> > > >orders a drink >> > > >and >> > > >while >> > > > > > > >> > > > > > > he's drinking the monkey jumps all around the >> > > >place. >> > > > > > > >> > > > > > > The monkey grabs some olives off the bar and >> > > >eats them. Then he >> > > >grabs >> > > > > some >> > > > > > > sliced limes and eats them. Then he jumps onto >> > > >the pool table, >> > > > > > > grabs one of the billiard balls, sticks it in >> > > >his mouth and, to >> > > > > everyone's >> > > > > > > amazement, somehow swallows it whole. >> > > > > > > >> > > > > > > The bartender screams at the guy "Did you see >> > > >what your monkey >> > > >did?" >> > > > > > > >> > > > > > > The guy says "No what?" >> > > > > > > >> > > > > > > "He just ate the cue ball off my pool >> > > >table-whole!" >> > > > > > > >> > > > > > > "Yeah, that doesn't surprise me" replied the guy >> > > >"He eats >> > > >everything >> > > >in >> > > > > > > sight, the little bastard. Sorry. I'll pay for >> > > >everything." >> > > > > > > >> > > > > > > The man finishes his drink, pays his bill, pays >> > > >for the stuff the >> > > > > > > monkey ate and leaves. >> > > > > > > >> > > > > > > Two weeks later, he's in the bar again, and his >> > > >pet monkey is >> > > >with >> > > >him. >> > > > > He >> > > > > > > orders a drink and the monkey starts running >> > > >around the bar >> > > >again. >> > > >While >> > > > > > > the man is finishing his drink, the monkey finds >> > > >a maraschino >> > > >cherry >> > > >on >> > > > > the >> > > > > > > >> > > > > > > bar. He grabs it, sticks it up his ass, pulls it >> > > >out and eats it. >> > > >The >> > > > > > > bartender is disgusted. >> > > > > > > >> > > > > > > "Did you see what your monkey did now?" he asks. >> > > > > > > "No what?"replied the guy. >> > > > > > > >> > > > > > > "Well, he stuck a maraschino cherry up his ass, >> > > >pulled >> > > > > > > it out and ate it!" said the bartender. >> > > > > > > >> > > > > > > "Yeah, that doesn't surprise me," replied the >> > > >guy. He still eats >> > > > > everything >> > > > > > > >> > > > > > > in sight but, ever since he swallowed that cue >> > > >ball, he measures >> > > > > everything >> > > > > > > >> > > > > > > first. .t telnet://ventedspleen.dyndns.org http://members.home.net/tsummerfelt1 |
|
From: William M. <wmc...@us...> - 2001-08-02 10:57:16
|
On Wed, 1 Aug 2001, Dane Beko wrote:
> Anyway, I just realized, unless I'm missing something, that there's no
> way in MultiMail, while in SOUP mode, to enter/send an email unless
> you're reading a SOUP packet that has email in it. Pressing the "E"
> results in MM prompting you for a newgroup (conference in this case)
> into which to place the message/email.
If you expand the area list ('L'), the Email area will appear, and you can
then Enter a message into it.
SOUP packets, like QWK packets, have no method of indicating the
subscribed area list. Hence, the default is the Active area list, and the
Email area doesn't appear unless it contains messages, or you switch to
the full list. I fixed this at one point by forcing Email to be included
in the Subscribed list, regardless of whether it contained messages; but I
broke it again in 0.38 when I made Active the default for those packet
types (like QWK and SOUP) which lacked an authoritative Subscribed list. I
could perhaps flag SOUP packets as having a Subscribed list, but that
would be misleading, and might break something (though I'm a bit vague on
that point).
--
William McBrine <wmc...@us...>
|
|
From: <db...@ea...> - 2001-08-02 03:27:54
|
I just realized something, William. Hope you're doing well; it's been a while since I've been active anywhere (FidoNet, here, etc.). Too busy nowadays. Anyway, I just realized, unless I'm missing something, that there's no way in MultiMail, while in SOUP mode, to enter/send an email unless you're reading a SOUP packet that has email in it. Pressing the "E" results in MM prompting you for a newgroup (conference in this case) into which to place the message/email. |
|
From: William M. <wmc...@us...> - 2001-04-18 01:17:40
|
For Unix users only: There's a little piece of code in the last two versions of MultiMail to display the contents of "X-Face" headers in SOUP packets. It's a bit crude, so it's off by default, and not documented. You have to define XFACE when compiling (see the #ifdef XFACE section in interfac/letterw.cc), and you need uncompface: ftp://syseng.anu.edu.au/pub/jaa/compface.tar.gz and a viewer that can handle xpm images (currently hard-wired to xv). The X-Faces pop up whenever you open a message with one, but then you have to manually close the viewer. Like I said, crude. :-) -- William McBrine <wmc...@us...> |
|
From: Adrián J. P. <ap...@pr...> - 2001-04-04 23:47:05
|
El mi=E9, 04 abr 2001, escribiste: > The next version of MultiMail will have mouse support, but so far, it's > only on certain platforms: X, the Linux console (with gpm), and Win32. > Or to put it another way: ncurses, and the X and Win32 PDCurses ports. = For > the other PDCurses-based ports (DOS and OS/2), I'll have to add low-lev= el > mouse support to PDCurses on those platforms. Should I wait until that'= s > done, or go ahead and release 0.39 as it is? Go ahead!!!=20 Best regards, --=20 *Adri=E1n Javier Prado =09 *E-Address:ap...@pr... * E-House:www.pradopaladino.com.ar *Linux Registered User 112529-99299 * LUG-Ar Registered Member 66 |
|
From: William M. <wmc...@us...> - 2001-04-04 17:21:02
|
On Wed, 4 Apr 2001, Robert Todd wrote: > Will it still compile ok with Borland C++ 5.5.1 and DJGPP Of course. What else would I be compiling it on? :-) > Also noticed that the DOS version of MMail would refuse to run and > give me an "Out of Memory Error" until I ran UPX on the EXE and > compressed it -- after which it works fine. That's bizarre. It doesn't happen for me. What version of DJGPP are you using? Hmm... How big is the executable? Make sure you strip it. In what environment is this happening? Specifically, what are you using for DPMI? -- William McBrine <wmc...@us...> |
|
From: William M. <wmc...@us...> - 2001-04-04 17:14:34
|
On Wed, 4 Apr 2001, Jim Hanoian wrote: > Worse is the flakiness in Win32... what's up with that? It's also flaky in XCurses, the X-based PDCurses port. (Not to be confused with running MultiMail in an xterm, which is what most X users do -- the XCurses port isn't particularly useful, it's just there for completeness.) My first attempt to utilize the mouse support in PDCurses didn't work at all, because it wasn't reporting single-click events. When I tried to fix this in PDCurses, it only got worse. :-( So I changed the model in MultiMail instead, to check for press events rather than single clicks, when linked with PDCurses. This does what I want most of the time, but not 100%; and when it doesn't, I'm not sure why. Worse yet is that, skimming through the Windows .h files (that came with the compiler, not PDCurses), I saw that double-click events were defined for the console, but not single-click events; so I'm not sure how fixable this is. With XCurses, at least, I know that it can be fixed (in theory) because it works correctly in a xterm. But the Win32 console may be a tougher nut. I already know that it's limited in many ways. But I don't have good documentation on it... anyone else? -- William McBrine <wmc...@us...> |
|
From: Jim H. <jha...@ka...> - 2001-04-04 11:06:17
|
wmc...@us... writes: >The next version of MultiMail will have mouse support, but so far, it's >only on certain platforms: X, the Linux console (with gpm), and Win32. >Or to put it another way: ncurses, and the X and Win32 PDCurses ports. For >the other PDCurses-based ports (DOS and OS/2), I'll have to add low-level >mouse support to PDCurses on those platforms. Should I wait until that's >done, or go ahead and release 0.39 as it is? > >BTW, the mouse support is flaky on Win32, and that's not likely to change. Bummer that it doesn't work yet on all ports. That's tolerable, though. Worse is the flakiness in Win32... what's up with that? Jim |
|
From: William M. <wmc...@us...> - 2001-04-04 04:49:09
|
The next version of MultiMail will have mouse support, but so far, it's only on certain platforms: X, the Linux console (with gpm), and Win32. Or to put it another way: ncurses, and the X and Win32 PDCurses ports. For the other PDCurses-based ports (DOS and OS/2), I'll have to add low-level mouse support to PDCurses on those platforms. Should I wait until that's done, or go ahead and release 0.39 as it is? BTW, the mouse support is flaky on Win32, and that's not likely to change. -- William McBrine <wmc...@us...> |
|
From: Jim H. <jha...@ka...> - 2001-04-01 00:58:38
|
gr...@ne... writes: >Hello everyone... just joining the list for the first time. Enjoy the >software tremendously... anyone know if it's possible to have multiple >signatures (i.e. different ones for different message bases)? Using the >DOS >32-bit version under Windows 98 SE. Some echomail conferences have >different sig requirements than others.... that's why I'm asking. :-) Welcome, George. Good to see a developer on the bandwagon <grin>. Jim |
|
From: William M. <wmc...@us...> - 2001-04-01 00:55:54
|
On Sat, 31 Mar 2001, George A. Roberts IV wrote: > anyone know if it's possible to have multiple signatures (i.e. > different ones for different message bases)? Using the DOS 32-bit > version under Windows 98 SE. There's no specific feature to support this yet. -- William McBrine <wmc...@us...> |
|
From: George A. R. I. <gr...@ne...> - 2001-03-31 22:06:59
|
Hello everyone... just joining the list for the first time. Enjoy the software tremendously... anyone know if it's possible to have multiple signatures (i.e. different ones for different message bases)? Using the DOS 32-bit version under Windows 98 SE. Some echomail conferences have different sig requirements than others.... that's why I'm asking. :-) Take care all! Regards, George A. Roberts IV Developer, Nexus Bulletin Board System http://www.nexusbbs.net/ ~ mailto:gro...@ne... telnet://bbs.nexusbbs.net |
|
From: Jim H. <jha...@ka...> - 2001-02-24 19:59:27
|
wmc...@us... writes: >> I know that v0.38 dropped automatic updating of the QWK packet >> date/time, and I guess this change affected the REP packet stamping? > >It's more correct to say that v0.38 _added_ preservation of the old >date/time; i.e., updating is what happens with normal file access, and >preservation requires extra steps. Ah. OK, just so long as we understood eachother <g>. Jim |
|
From: William M. <wmc...@us...> - 2001-02-24 19:31:06
|
On Fri, 23 Feb 2001, Jim Hanoian wrote: > I know that v0.38 dropped automatic updating of the QWK packet > date/time, and I guess this change affected the REP packet stamping? It's more correct to say that v0.38 _added_ preservation of the old date/time; i.e., updating is what happens with normal file access, and preservation requires extra steps. -- William McBrine <wmc...@us...> |
|
From: William M. <wmc...@us...> - 2001-02-24 19:27:20
|
On Fri, 23 Feb 2001 rel...@ju... wrote: > My reply isn't timestamping correctly. Thanks, I'm aware of this bug and I've fixed it for the next version. It's a side effect of the date-retention-for-packets feature. I was restoring the old date after every call to compressAddFile(), but in the case of replies, there was no old date to restore, so they were being set to -1 (which represents an error condition, though it's often interpreted as Dec. 31, 1969). Oops! > It doesn't seem to hinder the uploading of it though. Right; that's why I didn't rush out a fix. :-) -- William McBrine <wmc...@us...> |
|
From: Jim H. <jha...@ka...> - 2001-02-23 18:11:20
|
rel...@ju... writes: >My reply isn't timestamping correctly. > Although I haven't seen a problem with packets, I checked out a REP on my hard drive and found that MMDOS v0.38 leaves a blank date/time for creation. Then I fired up MMDOS v0.37, made a change, saved the packet, and saw a valid date. Then I opened with MMDOS v0.38, made another change, saved, and saw it revert to a blank date/time. I know that v0.38 dropped automatic updating of the QWK packet date/time, and I guess this change affected the REP packet stamping? Jim |
|
From: <rel...@ju...> - 2001-02-23 14:35:19
|
Hello Bill. Hope everything's good with ya. My reply isn't timestamping correctly. In win explorer i get nothing listed for the date of the reply packet. In DOS using the DIR command I get a timestamp of 6-30-00. But using DF (Directory Freedom), I get a date of 2-7-:6 with a wrong time of day also. Don't have a clue. Just thought I'd write and tell you. It doesn't seem to hinder the uploading of it though. I haven't tried a message with it like this. I just uploaded a packet that had add- delete areas info in it. But that worked. -greg ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj. |
|
From: <db...@ea...> - 2001-01-12 03:51:58
|
I haven't been very active in the conferences as of late. Too much work, not enough time. :( Anything going on with MultiMail? |
|
From: William M. <wmc...@us...> - 2000-12-26 07:57:21
|
This shows the filename in the description: ln -s $1 000000.MSG echo -e "000000\t$1\tmn" > AREAS -- William McBrine <wmc...@us...> |
|
From: William M. <wmc...@us...> - 2000-12-26 07:11:02
|
I've sometimes been asked about using MultiMail as a standard Internet email client. Much of the support is there already in the SOUP module, but it doesn't work directly with a mail spool file yet. However, I just came up with an interesting kludge for Unix users... Create an "xxuncompress" script as follows: ln -s $1 000000.MSG echo -e "000000\tMail\tmn" > AREAS With this, you can select any file in standard mailbox format, and read it in MultiMail. Replies won't work, nor will marking messages as read or deleting them. I accompanied this with an empty "xxcompress" to supress the error message when it attempts to save the read markers. -- William McBrine <wmc...@us...> |
|
From: William M. <wmc...@us...> - 2000-11-05 04:12:13
|
On Sat, 4 Nov 2000, Dane Beko wrote: > It's been crazy here for quite a few months and I'm now getting a > breather. :) Same here actually... To tell the truth, I've scarcely worked on MultiMail since 0.37. (I've made a total of two changes, and had one contribued.) But I'm about ready to pick it up again. I just need to get all my compile environments in order on my new computers... -- William McBrine <wmc...@us...> |
|
From: <db...@ea...> - 2000-11-04 21:52:56
|
It's been crazy here for quite a few months and I'm now getting a breather. :) I've been grabbing BW packets from Bob Juge's computer but I've only been glancing over them. What's going on with .38? |
|
From: Russell T. <ru...@ru...> - 2000-09-06 16:40:20
|
Hi, I compiled MultiMail 0.37 on FreeBSD without problems after realising that I needed to use gmake instead of make and gave an full path to the curses.h files. works great! Also the Linux version runs fine with Linux binary inferace?? if that is what it is called. Go well, Russell Russell Tiedt E-mail: ru...@ru... P.O.Box 7844 FidoNet: 5:7106/23 Bloemfontein FamilyNet: 8:7905/1 9300 CCCNet: 220:27/5 South Africa |
