Support for X-No-Archive planned?
Hi there.
Using mlmmj for a few years now, everything goes smoothly. Thanks to those who worked hard to build the best lightweight mailing list app.
I have a question / feature request.
Suppose I have an active archived mailing list, but I want a particular post not to be archived. What are the possibilities I have?
I know I can delete the file in spool/ml/archive/, but is there anything else that can be done? Is something like “X-No-Archive: yes” supported or planned?
Thanks again!
Signature · 8 lines
--====|====--
--------================|================--------
Patrice Levesque
http://ptaff.ca/
[email protected]
--------================|================--------
--====|====--
--Quoted 2 lines · Patrice Levesque
Using mlmmj for a few years now, everything goes smoothly. Thanks to those who worked hard to build the best lightweight mailing list app.
Thanks for the kind words!
Quoted 9 lines
I have a question / feature request.
Suppose I have an active archived mailing list, but I want a particular post not to be archived. What are the possibilities I have?
I know I can delete the file in spool/ml/archive/, but is there anything else that can be done? Is something like “X-No-Archive: yes” supported or planned?
It's a good idea which I might take a stab at implementing--been a while since I touched mlmmj code, so this might be the one to do. My initial thought is that this wouldn't be too hard to do.
Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.Quoting Patrice Levesque:
Quoted 3 lines
I know I can delete the file in spool/ml/archive/, but is there anything else that can be done? Is something like “X-No-Archive: yes” supported or planned?
Is this necessary inside the mlmmj itself? You could just grep over recent files with find and grep. This would be no real-time solution, of course, but more like Google's "remove after X days" feature (which I'd say is a good thing).
Anyway, a simple approach to do it synchronously could be to use the "noarchive" control flag, i.e. setting it to "2" would honour the X-No-Archive header. But it would be probably better (more generic and flexible) to create a new flag "archivewith", which would define an external program to do the archiving (or not, depending on whatever somebody wants, and also _where_ one wants, like an RDBMS or such, e.g.).
Quoted 5 lines · Jakob Hirsch
Quoting Patrice Levesque:
Quoted 3 lines
I know I can delete the file in spool/ml/archive/, but is there anything else that can be done? Is something like “X-No-Archive: yes” supported or planned?
How do you send this kind of header when sending a mail to the list using thunderbird/icedove for example?
Quoted 2 lines
Is this necessary inside the mlmmj itself? You could just grep over recent files with find and grep.
Humf... Before there's something better around, then! :)
Quoted 3 lines
This would be no real-time solution, of
course, but more like Google's "remove after X days" feature (which I'd say is a good thing).
I don't really like that solution. I run mhonarc using the MLMMJ folder, and unless I force it to reprocess all the full archive each time, the archived message WOULD be processed in my web archive.
Quoted 6 lines
Anyway, a simple approach to do it synchronously could be to use the "noarchive" control flag, i.e. setting it to "2" would honour the X-No-Archive header. But it would be probably better (more generic and flexible) to create a new flag "archivewith", which would define an external program to do the archiving (or not, depending on whatever somebody wants, and also _where_ one wants, like an RDBMS or such, e.g.).
It would be VERY nice to be able to launch a web archive program to update the web archive in real time whenever a message arrives (mhonarc in my case), so it doesn't have to wait for the next cron job to be executed (and even removing the need of any cron job).
Thomas
Quoted 11 lines · Thomas Goirand
Quoted 6 lines
Anyway, a simple approach to do it synchronously could be to use the "noarchive" control flag, i.e. setting it to "2" would honour the X-No-Archive header. But it would be probably better (more generic and flexible) to create a new flag "archivewith", which would define an external program to do the archiving (or not, depending on whatever somebody wants, and also _where_ one wants, like an RDBMS or such, e.g.).
It would be VERY nice to be able to launch a web archive program to update the web archive in real time whenever a message arrives (mhonarc in my case), so it doesn't have to wait for the next cron job to be executed (and even removing the need of any cron job).
I've long planned to have a 'postcommand' control file that then would get executed with the archive path appended so you could have something similar to:
/usr/bin/hypermail -c /my/conffile -1 -m
in the file which then would be executed after done delivery like
/usr/bin/hypermail -c /my/conffile -1 -m /var/spool/mlmmj/list/archive/23
Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.Quoted 6 lines · Thomas Goirand
Quoted 3 lines
This would be no real-time solution, of
course, but more like Google's "remove after X days" feature (which I'd say is a good thing).I don't really like that solution. I run mhonarc using the MLMMJ folder, and unless I force it to reprocess all the full archive each time, the archived message WOULD be processed in my web archive.
Well, that's a problem of your web archive software then. There's probably a way to purge message from that one, too.
Quoted 2 lines
It would be VERY nice to be able to launch a web archive program to update the web archive in real time whenever a message arrives (mhonarc
You could easily do that with Linux' inotifywait. But that's an additional background process running, and this is simple to do inside mlmmj.