Or perhaps just use Exim's existing base62 and base62d expansion operators?
:-)
http://www.exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html#SECTexpop
These:
- use the character set [A-Za-z0-9] on case-sensitive systems;
- use base36 encoding using [A-Z0-9] instead on systems with
case-insensitive file names;
- are used by Exim to generate its message identifiers, and hence
(presumably safe!) file names to store message data in the file system.
Cheers,
Mike B-)
On 18 October 2016 at 22:21, Phil Pennock <exim-users@???> wrote:
> On 2016-10-18 at 08:28 +0200, Arkadiusz Miśkiewicz wrote:
> > On Monday 17 of October 2016, Phil Pennock wrote:
> > > Or base64-encode it.
> >
> > "/" is part of base64 alphabet, so would have to replace that with other
> > character, too.
>
> You're quite right. I was thinking of the `base64url` encoding from
> RFC4648; it's used so often that I forgot.
--
Systems Administrator & Change Manager
IT Services, University of York, Heslington, York YO10 5DD, UK
Tel: +44-(0)1904-323811
Web:
www.york.ac.uk/it-services
Disclaimer:
www.york.ac.uk/docs/disclaimer/email.htm
