Greetings from a listowner who is trained in networks, not mail lists;
I have a smartlist set up (sort of) and it's already production with members. The individual e-mails are flying nicely. Unfortunately, I have not been able to get the digest to work. I'm confused about a couple of things and find nothing in the FAQ or manual (yes, I really do read them)
In the digest directory rc.custom, the appropriate lines read:
#digest_flag digest_flag = yes # uncomment this if you want digests digest_age = 86400 # maximum age of a digest in seconds #digest_size = 32768 # maximum size of a digest in bytes #undigested_list = $list@$domain # Reply-To: address for digests
and in the digest-d directory rc.custom is:
#digest_flag digest_flag = yes # uncomment this if you want digests digest_age = 86400 # maximum age of a digest in seconds #digest_size = 32768 # maximum size of a digest in bytes undigested_list=911@$domain
but I get no digests. See anything wrong there? (I did set it up to release the digest every 86400 - 24 Hrs.)
Which rc.custom file gets edited for what?
Why do both directories contain archives?
At 6:18 PM -0500 2/18/01, Tom Mahoney is rumored to have typed:
but I get no digests. See anything wrong there? (I did set it up to release the digest every 86400 - 24 Hrs.)
The digest list isn't getting any mail.
Two ways to do this: 1) subscribe the digest list to the "main" list, and 2) manually inject mail to 'flist list-d' in the main list's rc.local.s20. It appears that the former method is "blessed," but I personally find the second much more flexible...for example, you can stuff the mail into the digest _before_ you hadd a header or footer to the email, making unnecessary the convoluted recipies usually require to _remove_ the header in the digest's rc.local.s00.
Which rc.custom file gets edited for what?
Er...huh? I mean, the rc.custom for the list-l affects the interactive list, and the list-d affects the digest.
Why do both directories contain archives?
Because the list-l list holds an archive of seperate messages, and the list-d holds an archive of digests? Makes sense to me, frankly, considering you can decide how large the archives may grow by adjusting the limits in the seperate rc.custom files.
Charlie
OK,now I have the digest going out - sort of. It was an attachment that included each digested message as a separate message - confirmed with Eudora and Outlook Express.
Yes, I read the FAQ, but I'm sorry, I don't accept the "get a new client" line in this case. Eudora (latest version) and Outlook Express both should be able to deal with PROPERLY formatted digests.
Is there something else going on here, or is SmartMail just that bad?
At 11:10 AM -0500 2/19/01, Tom Mahoney is rumored to have typed:
OK,now I have the digest going out - sort of. It was an attachment that included each digested message as a separate message - confirmed with Eudora and Outlook Express.
<snip>
Is there something else going on here, or is SmartMail just that bad?
(*sigh*) You mean, is SmartList just that good to default to sending digests using the correct MIME type, and your ability to set your preferences just that bad, I think. (Be a little careful assigning "fault" when you don't understand the _correct_ way to do things in the first place...it will not win you friends, but may influence people adversely.)
Look, in Eudora, it's simple enough to turn OFF "Receive MIME Digests as Attachments," and I'd imagine it can be done in Outlook Express as well (although every time I give OE credit for being a sensible email client, someone here proves me wrong so no bets). This allows the _user_ to make the decision on how to receive the digests, not the maintainer. Of course, when you deal with stupid users (and we all do) who blame you because they don't know how to run their own software, you need to be willing to take a hit or two for the benefit of the whole.
If you are absoutely determined to change that (and for the record, I've done it myself on a digest or two, so I don't claim there may not be valid reasons), you'll need to edit the .bin/digest shell script to change the content type of the mailed digest issues. If you don't understand what I'm talking about, PLEASE don't muck with it until you have a little time to read up on what MIME is, how it works, and the various content types allowed. (I'm honestly _not_ being a wise guy here, just telling you that all the cut-and-paste instructions in the WORLD won't do you any good if you don't understand what the heck you're doing. And you are now into an area where you NEED to understand what you're doing to properly perform the cost/benefit analysis as to whether or not you SHOULD do this. Otherwise, you might seriously give some thought to using Topica or YahooGroups for your mailing lists.)
Charlie (who wonders how long it'll take for you to run into the HTML problem after changing the content type...I'm putting money on one issue, myself...)
(*sigh*) You mean, is SmartList just that good to default to sending digests using the correct MIME type, and your ability to set your preferences just that bad, I think.
You were right on with your last help but, with all due respect, you think wrong in this case. I DO have the MIME digests as attachments turned off and,in fact, receive other digested lists that claim to be MIME quite well. Like I said in my original message, I admit to knowing almost nothing about SmartList (or programming), but, as a computer professional, I like to think I know a few things.
I think something else is going on (or NOT going on)
If you are absoutely determined to change that (and for the record, I've done it myself on a digest or two, so I don't claim there may not be valid reasons), you'll need to edit the .bin/digest shell script to change the content type of the mailed digest issues. If you don't understand what I'm talking about, PLEASE don't muck with it until you have a little time to read up on what MIME is, how it works, and the various content types allowed.
One of the things I like to think I know is when NOT to muck with things. <G>
Charlie (who wonders how long it'll take for you to run into the HTML problem after changing the content type...I'm putting money on one issue, myself...)
Tom (who read THAT part of the FAQ, too)
At 1:06 PM -0500 2/19/01, Tom Mahoney is rumored to have typed:
You were right on with your last help but, with all due respect, you think wrong in this case. I DO have the MIME digests as attachments turned off and,in fact, receive other digested lists that claim to be MIME quite well.
Please don't take this as anything but my usual curmudgeonly style, but have you actually read the _header fields_ of the email among the different lists, so you can verify that these "other" lists are indeed doing things "correctly?" SmartList defaults to a content type of multipart/digest with the appropriate boundary...I don't know what your "other digested lists" are sent as, but SmartList is certainly doing things correctly by default so far as I can see. (Please note I am refering to the defaults; I suppose it's possible if you didn't install SmartList yourself that the folks at behosting.com might have changed something. If _that's_ the case, and you did _not_ install it yourself, you might want to check with them for more information.)
Again, like I said before, before you can consider this, you need to understand the various acceptable general MIME types for email messages.
Like I said in my original message, I admit to knowing almost nothing about SmartList (or programming), but, as a computer professional, I like to think I know a few things.
I never meant to imply that you didn't. Your question shows pretty clearly that you do _not_ understand much about email is formatted, however. (This isn't a lack-of-knowledge about SmartList, but rather one about how email is supposed to be formatted. That is all I was implying when I suggested areas for you to suppliment your knowledge base, trying to gently tell you that this has nothing to do with your not understanding SmartList and pointing you in a different direction so you might learn constructively.)
I stand firmly by my contention that SmartList, by default, supplies the _correct_ MIME type. Anyone here is, of course, free to correct me if I am wrong. (Wouldn't be the first time...)
Charlie
---------------------------------------------------------------------- L.O.F. Communications sales@lofcom.com Visit The Nostalgia Pages: http://www.lofcom.com/nostalgia/ http://www.lofcom.com/
Did you read this:
http://www.hartzler.net/smartlist/SmartList-FAQ.html#Section_5.5
-ph
On Mon, 19 Feb 2001, Tom Mahoney wrote:
OK,now I have the digest going out - sort of. It was an attachment that included each digested message as a separate message - confirmed with Eudora and Outlook Express.
Yes, I read the FAQ, but I'm sorry, I don't accept the "get a new client" line in this case. Eudora (latest version) and Outlook Express both should be able to deal with PROPERLY formatted digests.
Is there something else going on here, or is SmartMail just that bad?
Tom Mahoney MERCHANT911.ORG Merchants uniting to protect themselves.
tom@merchant911.org http://www.merchant911.org _______________________________________________ Smartlist mailing list Smartlist@lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
Yep, see original msg. below.
Did you read this:
http://www.hartzler.net/smartlist/SmartList-FAQ.html#Section_5.5
-ph
On Mon, 19 Feb 2001, Tom Mahoney wrote:
OK,now I have the digest going out - sort of. It was an attachment that included each digested message as a separate message - confirmed with Eudora and Outlook Express.
Yes, I read the FAQ, but I'm sorry
smartlist@lists.rwth-aachen.de
-
Charlie Summers -
Peter Hartzler -
Tom Mahoney