Toen ik Robert Allerstorfer kietelde, kwam er dit uit:
Ruud:
# Filename: base64.rc.inc
[...]
this looks great, thanks for your efforts. However, I haven't found
time to test it yet.
The current interface only decodes 4 characters at a time
(4 base64-characters into 3 decoded bytes).
I am thinking of a line-oriented interface, so that the caller defines
the start-line and the number of lines. The base64-block needs to be
in b64_Input, so a wrapper that puts (the requested part of) some
base64-block in that variable, is handy.
(1/0 = start at line-1/until the end)
(0/-5 = the last 5 lines)
It can also be used well for base64-encoded headers, like
Subject: =?iso-8859-1?b?<base64-encoded-dirt>?
Could you also announce when you release v1.0 so
I could consider replacing the current way I am using in my Softlabs
AntiVirus Filter
Please view it as an option, not as a replacement.
FYI, I have just released version 0.4 of that tool, where I also
worked hard to replace executing external programs by pure-procmail
code as much as it was possible.
Idea: give the local variables names like savf_Name (where savf =
Softlabs AntiVirus Filter) to make the rc-files more re-usable.
| # YYYYMMDD:
| DATE = `date +"%Y%m%d"`
Get the date from the From_header. If that fails, maybe try to get it from
the most recent Received-header. If even that fails, call date.
| # make sure the header contains a unique Message-ID:
| :0 fW
| | formail -a "Message-ID:"
Check first if it already has one (saves formail-calls).
--
Affijn, Ruud
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail