The Fine Print: The following comments are owned by whoever posted them.
( Reply )
|
Re: Mail Notification
by on Tuesday October 24, 06:04AM, 2000
|
Hacking always gets my interest up. Anyway, to start answering my own question, a gross hack solution (plug ugly) would be to send the notification message to the admin_address as usual, and then, on the admin's machine (i.e., my machine), write an Outlook script to trigger on, say, "Squishdot" in the subject line, and then copy and forward the message to all members of an Outlook mailing list. The only real issue with that would be keeping the list in Outlook in sync with Squishdot. Otherwise, no one would be the wiser. On the incoming side, it's tougher. There, I could write a script again to flag things with a certain subject line, and then write it out as a separate file to a specified Squishdot (or Zope) directory. Then, in Squishdot, write dtml code for index_html (or something included in it) that goes out and reads whatever's in the specified directory. The problem is what to do with it then. This will make it automatically visible on the site, but it won't be worked into the main posts or any of the threads. Basically, we'd need somthing to periodically "spool" these posts, figure out what thread, if any, they belong to, and then put them through the standard posting_html routines.
|
[ Reply to this ]
|
-
Re: Mail Notification
by on Tuesday October 24, 07:49PM, 2000
|
Hmm...well, one could also set up some mailing list software, then tell squishdot to email all new posts to this mailing list so that they get rebroadcast to subscribers. One could even set up a MailHost script that would allow subscription/unsubscription via a web form; we at Thibsdot track users by their email addresses, so this isn't a big problem. I don't think that part would be too difficult...
But reading stuff in might be a tad more difficult. I guess you could set up a procmail script to automatically invoke some program which would parse the incoming message then simulate the POST to thibsdot. I would, of course, verify that the post is coming from a real Thibsdot user or change the name to "Anonymous Coward" before hand...which means that I'd have to figure out how to generate the user login cookies. I'm not that familiar with the internal workings of majordomo et. al., so I have no clue whether or not this makes sense or is pure rubbish.
Guess I'll go hack around with that and stuff squishdot.org with another posting later.
|
[ Reply to this ]
|
-
Re: Mail Notification
by on Tuesday October 24, 08:34PM, 2000
|
See my post below -- I think we're both saying more or less the same thing as far as email notification is concerned -- me under NT (at work, anyway), and you (it seems) under UNIX.
As for receiving, I'm running small Intranet sites behind a firewall, and don't have to worry so much about authentication. If people could initiate a post just by sending me an email with a particular word in the Subject line, I think more people would use the system (my real agenda here). After all, they'd be getting a return notification with a clickable link.
If I want to manufacture postings from incoming emails, than, as you suggest, I just have to parse the data and get it POSTED. I can see already that the Python code (Squishdot.py) has data structures for each of the message parts (title, author, body, etc.), so this can't be that hard to do. I just gotta find the entry point for POST (which can't be that hard either once I find the time).
|
[ Reply to this ]
|
|
The Fine Print: The following comments are owned by whoever posted them.
( Reply )
|
|
Related Links