On May 18, 2016, at 3:36 PM, Brent Hetland <[log in to unmask]> wrote:

> Thanks Ben, but if I understood it correctly, the values in the listserv table are stored as a bit mask, so what I was looking for a quick way to take a value of 736094 and break it down to all the different settings in the page that you mentioned.

Assuming you don’t want to write a script or do something like that, but just use resources already available on the web, then here’s one approach.  This will look better if viewed in a monospace font, so that everything lines up nicely.

If you convert the number you’re interested in, say 5243904, into binary using Google or Wolfram Alpha:

https://www.google.com/search?client=safari&rls=en&q=5243904+in+binary
https://www.wolframalpha.com/input/?i=5243904+in+binary

10100000000010000000000 

then list the possible bitmask values in binary:

                      1 = 1 / ACK
                     10 = 2 / MSGACK
                    100 = 4 / NOACK
                   1000 = 8 / NOMAIL
                  10000 = 16 / DIGEST
                 100000 = 32 / INDEX
                1000000 = 64 / NOFILES
               10000000 = 128 / REPRO
              100000000 = 256 / IETFHDR
             1000000000 = 512 / DUALHDR
            10000000000 = 1024 / FULLHDR
           100000000000 = 2048 / xxx822HDR
          1000000000000 = 4096 / NORENEW
         10000000000000 = 8192 / reserved
        100000000000000 = 16384 / CONCEAL
       1000000000000000 = 32768 / EDITOR
      10000000000000000 = 65536 / REVIEW
     100000000000000000 = 131072 / NOPOST
    1000000000000000000 = 262144 / MIME
   10000000000000000000 = 524288 / SUBJHDR
  100000000000000000000 = 1048576 / reserved
 1000000000000000000000 = 2097152 / HTML
10000000000000000000000 = 4194304 / reserved

Then you can see where the ones fall in the number and extract the meaning from that.

10100000000010000000000 = 
10000000000000000000000 + 
  100000000000000000000 +
            10000000000

= 4194304 / reserved + 1048576 / reserved + 1024 / FULLHDR

The two ‘reserved’ items are described in the documentation in this way: 'Bit positions marked as "reserved" must be left unchanged if updating an existing entry, and set to zero when creating a new entry. They do not correspond to subscription options and are used for internal book-keeping purposes.'


You mentioned 736094 previously, which I assume you got from the fourth and fifth parameters in the sample OPTIONS value you quoted earlier:

> 4;5243904;0;736094;736096;16777215


Those parameters aren’t bitmasks, and don’t contribute to the subscription options.  The fifth number is the date the subscriber joined the list, measured by the number of complete days elapsed since and including January 1, 0001.  The fourth number isn’t documented, but looks like it’s another date — perhaps the date since the subscription was last active (posted to the mailing list, or changed its subscription settings, or some similar thing) — though I don’t know that definitively.

-jwgh

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1