All,
I am trying to use rc.local.s10.mhonarc from
http://www.ha-schneider.de/software/smartlist/
to set up an archive for a mailing list.
I have renamed rc.local.s10.mhonarc to rc.local.s30 and added following line to rc.custom
RC_LOCAL_SUBMIT_30 = rc.local.s30
rc.local.s10 and rc.local.s20 are already in use and since I do not know how to merge the recipe in rc.local.s10.mhonarc with either of the two, I renamed it to rc.local.s30 and added a new line in rc.custom.
Could someone please help me understand as to how it all works.
Thanks
Nishi
The following is a sample of the results of a search that I receive by email.
This there a way to hide the line number?
ARCHIVE egrep august latest/*
BEGIN---------------cut here------------------
latest/10:16:Monday, August 27, 2001
latest/11:16:Tuesday, August 21, 2001
latest/12:16:Wednesday, August 29, 2001
END-----------------cut here------------------
Thanks for your help!
Alan,
hi!
how can i modyfiy the text for the automatic subscribe/unsubscribe-mail?
The possibilities of a *subscribe.txt*-file in my folder are not enough for
me. I want suppress the information about the transmited data and translate
the rest of the mail to german.
TIA, martin
--
"Who needs horror movies when we have Microsoft?"
- Christine Comaford, PC Week
Hello:
Does SmartList have an archiving and (hopefully user friendly) search capability?
[I'm not interested in the archives of this Disc List, but of the list I run for my
'users'].
Thanks,
Mitch Darer
--
Mitchell Darer, WebMaster, mitch(a)focusing.org
The Focusing Institute, 34 East Lane, Spring Valley, NY 10977
http://www.focusing.org (845) 362-5222 (phone/fax)
At 11:41 AM -0400 7/28/00, Werner Reisberger is rumored to have typed:
> I never saw any
> admin reply to the numerous complains about spam messages.
Actually, that's not _strictly_ true, since I remember when Stephen was
actually maintaining the list (and probably anally have archives of the list
from that time somewhere on some floppy or MO cart from a long time ago and
far far away). But you're right, it's been _years_ since he's been around.
However, the list belongs to the maintainer (or at least the machine's
admin), not the members. You'll get no argument from me that the list should
be moved (I believe I said exactly that a couple of times), but to suggest
the admins need to take a poll to ask what they may or may not do with the
existing list is silly, to say the least. They are certainly able to move
this list to mailman without the list subscriber's permission - indeed, they
_have_ done so, which makes my point for me.
Whether we should move this list to a SmartList server is a completely
seperate issue...one which Philip should probably weigh in on, since he is
now maintaining the procmail/SmartList source and as such the de facto head
of our band of merry wanderers...
Charlie
Now I am setting up Smartlist with qmail (on a RH mamchine).
qmail is installed and tested.
Previously I only copied Smartlist over from a similar platform (RH
Linux). Now I decided to install from the source:
I unpackaged SmartList-3.15 over procmail-3.22 (I cannot find
procmail-3.15, thus by tweaking the folder name I managed to have them in
the same dirrectory "procmail-3.15").
Now when I run
> cd procmail-3.15/SmartList
> sh install.sh /home/slist
it spit out endlessly the following line:
install.sh3: line 3: cd: .: Not a directory
install.sh3: line 3: cd: .: Not a directory
install.sh3: line 3: cd: .: Not a directory
...
that evenually I had to kill the process.
Is it a version problem or else?
Zhiliang
Charlie - Thanks for the clarification.
I have been using it for plain text only. Now this is straight.
Zhiliang
On Mon, 17 Mar 2014, charlie(a)lofcom.com wrote:
> Date: Mon, 17 Mar 2014 13:04:07 -0400 (EDT)
> From: charlie(a)lofcom.com
> To: smartlist(a)lists.rwth-aachen.de
> Subject: Re: mail body
>
> Zhiliang wrote ..
>
>> I wonder which part of the
>> smartlist converts mordern mails to old fashioned plain text(?),
>
> It doesn't. It treats "modern mails" the same way it treats "antique
> mails;" as a stream. If you want only plain-text mails in your list,
> you need to reject or convert multipart outside of SmartList. (Well,
> ok, you can call your rejection or conversion routine, like the demime
> perl script, from any of the rc.submit.* you want, but I mean that
> SmartList cannot natively change multipart to plain text. Truth is,
> IMHO, one of the things that makes it such an excellent tool even now
> is that it _doesn't_ munge the body.)
>
>> and if I
>> can take that part out (e.g. is it in "rc.submit"? etc).
>
> There's nothing to remove. SmartList is working exactly as-designed;
> passing the message on to the list mostly the way it found it (header
> changes notwithstanding).
>
> Charlie
Zhiliang wrote ..
> I wonder which part of the
> smartlist converts mordern mails to old fashioned plain text(?),
It doesn't. It treats "modern mails" the same way it treats "antique mails;" as a stream. If you want only plain-text mails in your list, you need to reject or convert multipart outside of SmartList. (Well, ok, you can call your rejection or conversion routine, like the demime perl script, from any of the rc.submit.* you want, but I mean that SmartList cannot natively change multipart to plain text. Truth is, IMHO, one of the things that makes it such an excellent tool even now is that it _doesn't_ munge the body.)
> and if I
> can take that part out (e.g. is it in "rc.submit"? etc).
There's nothing to remove. SmartList is working exactly as-designed; passing the message on to the list mostly the way it found it (header changes notwithstanding).
Charlie
I have a new list, that turns all attachable parts/hyper text to plain
text into the mail body (see lower part for an example). I did an
experiment, using procmailrc code to only forward to a list of emails with
! `cat listfile`
which passes the mails with multi-parts well. I wonder which part of the
smartlist converts mordern mails to old fashioned plain text(?), and if I
can take that part out (e.g. is it in "rc.submit"? etc).
Thanks,
Zhiliang
-------------
-- example --
-------------
--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: multipart/alternative;
boundary="_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_"
--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
......................
mail body text
...........................
--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http://www.w3.org/TR/REC-html40">
...................................
mail body hyper text
......................................
</body>
</html>
--_000_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_--
--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_
Content-Type:
application/vnd.openxmlformats-officedocument.wordprocessingml.document;
name="2014 NRSP 8 Leadership.docx"
Content-Description: 2014 NRSP 8 Leadership.docx
Content-Disposition: attachment; filename="2014 NRSP 8 Leadership.docx";
size=19737; creation-date="Mon, 17 Mar 2014 13:42:32 GMT";
modification-date="Mon, 17 Mar 2014 13:42:32 GMT"
Content-ID: <814DB34A2C17E0419B28190B2C5E44B5(a)mail.iastate.edu>
Content-Transfer-Encoding: base64
UEsDBBQABgAIAAAAIQAk5ahdmwEAAJYGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
.................
coded lines
......................
--_004_4BBDE0AB525DA74BB64ABBFEA3F2C4B53A7CB7F1ITSDAG2Ditsiast_--