• pgp anyone?

    From August Abolins@2:221/1.58 to Gunter on Thu Jan 1 09:55:00 2026
    Hello gunter.sandner # googlemail.com!

    Another matter I have been revisiting: how to encrypt a
    message, but my attempts have been failing.

    I have defined several functions in the Tools menu:


    Tools Menu
    Ŀ
    Menu Program $FILE S W L A Mem
    1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer
    2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer
    3 gnupg decrypt gpg -d $FILE w/o header
    4 GPG Verify msg gpg --verify $FILE Puffer
    5

    1 and 2 do not seem to work.
    But 3 and 4 do.


    What am I doing wrong?

    Do 1 and 2 need the gpg -o parameter? And if so, what should
    those lines look like?
    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Gunter@2:221/10 to All on Thu Jan 1 17:59:00 2026
    From: Gunter <gunter.sandner@googlemail.com>

    Hallo August!

    I have defined several functions in the Tools menu:

    │ 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer √ │
    │ 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer √ │
    │ 3 gnupg decrypt gpg -d $FILE w/o header √ │
    │ 4 GPG Verify msg gpg --verify $FILE Puffer √ │

    1 and 2 do not seem to work.
    But 3 and 4 do.

    What am I doing wrong?

    Do 1 and 2 need the gpg -o parameter? And if so, what should
    those lines look like?

    I simply don't know. I haven't used PGP for years and it's currently way
    out of my focus, sorry...


    Ciao
    Gunter

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Martin Wodrich@2:221/10 to Gunter on Mon Jan 5 18:06:00 2026
    From: Martin Wodrich <martin@martinwodrich.de>

    Gunter schrieb:
    Hallo August!

    I have defined several functions in the Tools menu:

    │ 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer √ │
    │ 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer √ │
    │ 3 gnupg decrypt gpg -d $FILE w/o header √ │
    │ 4 GPG Verify msg gpg --verify $FILE Puffer √ │

    1 and 2 do not seem to work.
    But 3 and 4 do.

    What am I doing wrong?

    Do 1 and 2 need the gpg -o parameter? And if so, what should
    those lines look like?

    I simply don't know. I haven't used PGP for years and it's currently way
    out of my focus, sorry...

    PGP in XP is not working since pgp 2.6.x is out of use.

    GPG should work, but no one tested this.
    --
    Mit freundlichen Gruessen,
    Martin Wodrich

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Martin Wodrich on Mon Jan 5 13:38:00 2026
    Hello martin # martinwodrich.de!

    PGP in XP is not working since pgp 2.6.x is out of use.

    So.. the code makes calls using "pgp" hardcoded?

    Why not simply replace "pgp" with "gpg" in the source?


    GPG should work, but no one tested this.

    These work:

    Message
    Ĵ
    PGP..
    Ŀ
    1. Decode message
    1. Test signature
    1.

    And I'm using:

    gpg --version
    gpg (GnuPG) 2.2.19
    libgcrypt 1.8.5

    I'm just not sure how to use the $ASK and $FILE variables in
    the Tools menu to make my own "gpg -sea -r " command tool.


    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Mon Jan 5 21:32:38 2026
    Hi August,

    On 2026-01-05 13:38:00, you wrote to Martin Wodrich:

    PGP in XP is not working since pgp 2.6.x is out of use.

    So.. the code makes calls using "pgp" hardcoded?

    Why not simply replace "pgp" with "gpg" in the source?

    If it's hardcoded you could make a copy of gpg.exe to pgp.exe...?

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.6-B20251227
    * Origin: FMail development HQ (2:280/464)
  • From August Abolins@2:221/1.58 to Wilfred van Velzen on Mon Jan 5 19:20:00 2026
    Hello Wilfred!

    So.. the code makes calls using "pgp" hardcoded?
    Why not simply replace "pgp" with "gpg" in the source?

    If it's hardcoded you could make a copy of gpg.exe to pgp.exe...?

    Turns out that OXP actually has modest config options for
    seleting a specific "PGP":


    Config Tools
    Ŀ
    Options..
    External..
    Ŀ
    Lister
    Editor
    Shell
    Unpacker
    pmCrypt
    ij PGP <===


    PGP settings Ŀ

    PGP version GnuPG  <===

    [x] PGP support <===

    [x] Batch mode
    [ ] Wait for key after PGP call
    [ ] Log file for automatic actions

    [x] Automatic key import from Mails
    [ ] Automatic key import from News

    User ID _____________________________ <===

    GPG options _________________________  <===


    ..including fields to fill in User ID and GPG options.

    I suppose I need to study those a bit more. The latter two
    fields are blank here.

    The F1 Help for the latter field reads:

    ͻ

    Please enter GnuPG command line options that shall be
    used for encrypting mails here.

    This way you can create GnuPG encrypted mails that ma
    be decrypted by PGP. Use the first option seen after
    pressing F2 to keep GnuPG compatible with PGP 2.x (yo
    need to install GnuPG IDEA support then). Use the
    second option to keep GnuPG compatible with PGP 5.x
    and higher. IDEA support needs not to be installed
    then.

    The drop-down options for the type of PGp this..

    PGP version GnuPG  <===

    [x] PGP support <===

    [x] Batch mode
    [ ] Wait for key after PGP call
    [ ] Log file for automatic actions

    [x] Automatic key import from Mails
    [ ] Automatic key import from News

    User ID _____________________________ <===

    GPG options _________________________  <===


    ..including fields to fill in User ID and GPG options.

    I suppose I need to study those a bit more. The latter two
    fields are blank here.

    The F1 Help for the latter field reads:

    ͻ

    Please enter GnuPG command line options that shall be
    used for encrypting mails here.

    This way you can create GnuPG encrypted mails that ma
    be decrypted by PGP. Use the first option seen after
    pressing F2 to keep GnuPG compatible with PGP 2.x (yo
    need to install GnuPG IDEA support then). Use the
    second option to keep GnuPG compatible with PGP 5.x
    and higher. IDEA support needs not to be installed
    then.

    The drop-down options for the type of PGp this above..

    PGP version GnuPG  <===

    ..are:

    Ŀ
    2.6.x
    5.x
    6.5.x
    GnuPG


    I've selected GnuPG.

    I have no idea what IDEA support is, or whether it applies in
    my case.



    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Gunter on Mon Jan 5 19:49:00 2026
    Tools MenuĿ
    Menu Program $FILE S W L A Mem 1 ^GnuPGP Wilfre gpg -sea -r wilfred $FILE Puffer 2 GnupPGP ASK gpg -sea -r $ASK $FILE Puffer 3 gnupg decrypt gpg -d $FILE w/o header 4 GPG Verify msg gpg --verify $FILE Puffer 5

    I think I am closer to getting [2] to work.

    I noticed that after executing [2] above, a MSG.TMP.asc file is
    created in the ~\temp diretory below the OpenXP home directory.

    That .asc is precisely what "gpg -sea -r $ASK $FILE" generates.

    However, the contents of that file do not get replaced into the
    Editor.

    So.. I figured I would try this:

    gpg -sea -o temp\MSG.TMP -r $ASK -$FILE

    ..but that did not work. Instead I got an error:

    File 'temp\MSG.TMP' exists. Overwrite? (y/N) y
    gpg: can't create 'temp\MSG.TMP': No such file or directory
    gpg: H:\DOWNLOADS\OPENXP\TEMP\MSG.TMP: sign+encrypt failed: No such file or directory
    Press any key ...

    What am I missing?


    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Tue Jan 6 09:27:48 2026
    Hi August,

    On 2026-01-05 19:20:00, you wrote to me:

    I have no idea what IDEA support is, or whether it applies in
    my case.

    It's an old encryption method (maybe the default in PGP), that is deprecated in GPG, and not available without using a special backwards compatible option for GPG...

    You should only use it when you need to communicate with someone that has only an old PGP version available.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.6-B20251227
    * Origin: FMail development HQ (2:280/464)
  • From Martin Wodrich@2:221/10 to August Abolins on Tue Jan 6 15:25:00 2026
    From: Martin Wodrich <martin@martinwodrich.de>

    August Abolins schrieb:

    Hello martin # martinwodrich.de!

    PGP in XP is not working since pgp 2.6.x is out of use.

    So.. the code makes calls using "pgp" hardcoded?

    No, there is a config option:
    ┌─ PGP-Einstellungen ──────────────────────────────┐
    │ │
    │ PGP-Version GnuPG ↓ │
    │ ┌───────┐ │
    │ [ ] PGP-U│ 2.6.x │ung │
    │ │ 5.x │ │
    │ [ ] PGP-R│ 6.5.x │ übergehen │
    │ [ ] Warte│ GnuPG │tendruck nach PGP-Aufruf │
    │ [ ] Logfi└───────┘tomatische Aktionen │
    │ │
    │ [x] Keys aus PMs automatisch einlesen │
    │ [ ] Keys aus AMs automatisch einlesen │
    │ │
    │ User-ID martin@martinwodrich.de
    │ │
    │ GPG-Optionen --compress-algo 1 --cipher-algo►↓ │
    │ │
    │ │
    │ │ └─────────────────────────────────────────── [F2] ─┘

    Why not simply replace "pgp" with "gpg" in the source?

    No, just set up GnuPG and use it.
    PGP-Version 2.6.x is the old PGP.
    PGP-Version GnuPG means gpg.
    PGP-Version 5.x and 6.5.x no one knows.
    --
    Mit freundlichen Gruessen,
    Martin Wodrich

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Martin Wodrich@2:221/10 to Wilfred van Velzen on Tue Jan 6 15:36:00 2026
    From: Martin Wodrich <martin@martinwodrich.de>

    Wilfred van Velzen schrieb:
    Hi August,

    On 2026-01-05 19:20:00, you wrote to me:

    I have no idea what IDEA support is, or whether it applies in
    my case.

    It's an old encryption method (maybe the default in PGP), that is
    deprecated in GPG, and not available without using a special backwards compatible option for GPG...

    You should only use it when you need to communicate with someone that has only an old PGP version available.


    Old means: PGP 2.6.x

    --
    Mit freundlichen Gruessen,
    Martin Wodrich

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Thomas Barghahn@2:221/10 to All on Tue Jan 6 21:10:24 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    [...]

    What am I doing wrong?

    Can you tell us what your goal is?

    Do you want to reply to encrypted emails and also create encrypted
    emails yourself using GPG?

    OXP can encrypt and decrypt emails automatically with the correct
    settings. So you don't need any additional tools like the ones you
    presented here.

    Thomas
    --
    == S E N D E Z E I T ================
    + DATUM : Dienstag, 06. Januar 2026
    + UHRZEIT: 21:10:24 UHR (MEZ)
    == +++ Heilige Drei Knige +++ ======

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Tue Jan 6 19:36:00 2026
    Hello Th.Barghahn # gmx.de!

    ** On Tuesday 06.01.26 - 21:10, Th.Barghahn # gmx.de wrote to All:

    Can you tell us what your goal is?

    I want to send netmail/email encrypted.


    Do you want to reply to encrypted emails and also create
    encrypted emails yourself using GPG?

    YES!

    Basically, I notice that OpenXP decrypts a message fine. And,
    once it is decrypted, it stays decrypted. So.. there is no need
    to specifically "reply to encrypted" messages since they will
    be decrypted by then.


    OXP can encrypt and decrypt emails automatically with the
    correct settings. So you don't need any additional tools
    like the ones you presented here.


    That sounds wonderful. What needs to be done?

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Thu Jan 8 11:31:14 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    OXP can encrypt and decrypt emails automatically with the
    correct settings. So you don't need any additional tools
    like the ones you presented here.

    That sounds wonderful. What needs to be done?

    To avoid any misunderstandings: OXP only supports "gpg/inline"!

    OXP does not support "gpg/mime", which is used and generated by modern
    email clients!

    Your settings are almost identical to mine.

    Also check your settings for the relevant email addresses:
    [TAB] => Spezial => PW
    <https://barghahn-online.de/Pictures/oxp_tab_pw.png>

    Thomas
    --
    == S E N D E Z E I T ===================================
    + DATUM : Donnerstag, 08. Januar 2026
    + UHRZEIT: 11:31:14 UHR (MEZ)
    == Heute: Internationaler Tag des Maschinenschreibens ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Thu Jan 8 08:21:00 2026
    Hello Th.Barghahn # gmx.de!

    ** On Thursday 08.01.26 - 11:31, Th.Barghahn # gmx.de wrote to All:

    To avoid any misunderstandings: OXP only supports "gpg/inline"!

    OXP does not support "gpg/mime", which is used and generated by modern email clients!

    That is no problem. Inline is quite fine. That is how I was
    doing it manually - creating the pgp block and reediting the
    outgoing message by dropping in the new block.


    Your settings are almost identical to mine.

    Also check your settings for the relevant email addresses:
    [TAB] => Spezial => PW <https://barghahn-online.de/Pictures/oxp_tab_pw.png>

    Now.. THAT setting I was not aware of!

    a#### @ #######.ca Ŀ

    Password _______________________________

    Crypt method PGP 

    [x] Default: Crypt



    ͻ

    Enter the password here with which messages to and
    from the selected user can be coded. You can decide
    each time when you send a message, whether to code it
    or not.

    The general rule is: the longer the password,
    the more secure the encryption.


    So, it sounds like the PW is optional, and I willbe prompted
    for it if that field is blank?

    I am not sure what that password that needs to be. Is it
    supposed to be my private key password?

    [time elapses..]

    OK.. I tried it without a PW and the message went out in the
    clear.

    When I entered a PW in the Above settings, and tried again, I
    got this:

    Error Ŀ

    Encoding/signing was not successful.



    Surely there are other settings required to get OXP to enrypt
    an outgoing message?



    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Thu Jan 8 15:49:48 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    Sorry, August. Before we discuss further details:

    Which operating system are you using?
    Which version of gpg/Gpg4Win are you using?
    Which version of OXP are you using?

    Thomas
    --
    == S E N D E Z E I T ===================================
    + DATUM : Donnerstag, 08. Januar 2026
    + UHRZEIT: 15:49:48 UHR (MEZ)
    == Heute: Internationaler Tag des Maschinenschreibens ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Thu Jan 8 18:24:00 2026
    Hello Th.Barghahn # gmx.de!

    ** On Thursday 08.01.26 - 15:49, Th.Barghahn # gmx.de wrote to All:

    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    Sorry, August. Before we discuss further details:

    Which operating system are you using?
    Which version of gpg/Gpg4Win are you using?
    Which version of OXP are you using?

    [1] XP

    [2] H:\temp>gpg --version
    gpg (GnuPG) 2.2.19
    libgcrypt 1.8.5

    [3]
    Ŀ
    Open \\// 5.0.64 (Win32) (c) 1992-1999 Peter Mandrella
    //\\ XP (c) 2000-2025 OpenXP-Team
    OpenSSL 1.0.2u 20 Dec 2019



    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Fri Jan 9 12:17:44 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:
    Hello Th.Barghahn # gmx.de!

    ** On Thursday 08.01.26 - 15:49, Th.Barghahn # gmx.de wrote to All:

    Which operating system are you using?
    Which version of gpg/Gpg4Win are you using?
    Which version of OXP are you using?

    [1] XP
    Ok.

    [2] H:\temp>gpg --version
    gpg (GnuPG) 2.2.19
    libgcrypt 1.8.5

    Oh, that version is quite a bit outdated already. ;-)
    Please install the 'Gpg4Win 4.4.1' package on your Windows XP system. It includes the current version of 'gpg'. The package also contains the
    latest version of "Kleopatra", which you can use to manage all your
    keys. You can download Gpg4Win from the following page: <https://www.gpg4win.de/>

    My versions:

    | C:\gpg --version
    | gpg (GnuPG) 2.4.8
    | libgcrypt 1.11.1
    | Kleopatra 3.3.0

    Import all your relevant keys into Kleopatra that includes your own
    key pair as well as all public keys you need for encryption and
    verification.

    OpenXP 5.0.64 (Win32)
    Ok.

    | --- your M-ID:<news:675090789@f1.n221.z2.fidonet.fi> ---

    [...]

    So, it sounds like the PW is optional, and I willbe prompted
    for it if that field is blank?

    This input field has no meaning for current gpg versions and should be
    left empty.

    I am not sure what that password that needs to be. Is it
    supposed to be my private key password?

    First, please install GPG4Win with Kleopatra and import all your
    keys. Then try sending an email with OpenXP.


    Thomas
    --
    == S E N D E Z E I T ===============
    + DATUM : Freitag, 09. Januar 2026
    + UHRZEIT: 12:17:44 UHR (MEZ)
    == Heute: Tag der Aprikose =========

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Fri Jan 9 08:02:00 2026
    Hello Th.Barghahn # gmx.de!

    First, please install GPG4Win with Kleopatra and import all your
    keys. Then try sending an email with OpenXP.

    Email works.

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Fri Jan 9 14:47:17 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:
    Hello Th.Barghahn # gmx.de!

    First, please install GPG4Win with Kleopatra and import all your
    keys. Then try sending an email with OpenXP.

    Email works.

    Really? You installed Gpg4Win with "Kleopatra", imported all relevant addresses, and now encryption works?

    Thomas
    --
    == S E N D E Z E I T ===============
    + DATUM : Freitag, 09. Januar 2026
    + UHRZEIT: 14:47:17 UHR (MEZ)
    == Heute: Tag der Aprikose =========

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Fri Jan 9 09:00:00 2026
    Hello Th.Barghahn # gmx.de!

    ** On Friday 09.01.26 - 14:47, Th.Barghahn # gmx.de wrote to All:

    Email works.

    Really? You installed Gpg4Win with "Kleopatra", imported all relevant addresses, and now encryption works?

    Email to and from oxp works, yes.

    I opted out of kleopatra. The current version is not supported
    in XP. I prefer to manage my keys and manually.


    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Fri Jan 9 16:11:33 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:
    ** On Friday 09.01.26 - 14:47, Th.Barghahn # gmx.de wrote to All:

    Email works.

    Really? You installed Gpg4Win with "Kleopatra", imported all
    relevant addresses, and now encryption works?

    Email to and from oxp works, yes.

    Perfect! :-) As I said, this only works with "gpg/inline". Macros or
    scripts are still required for "gpg/mime".

    I opted out of kleopatra. The current version is not supported
    in XP.

    Really? ;-)
    <https://barghahn-online.de/Pictures/win10_kleopatra.png>

    I prefer to manage my keys and manually.

    Ok.

    Thomas
    --
    == S E N D E Z E I T ===============
    + DATUM : Freitag, 09. Januar 2026
    + UHRZEIT: 16:11:33 UHR (MEZ)
    == Heute: Tag der Aprikose =========

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Thomas Barghahn@2:221/10 to All on Fri Jan 9 16:15:18 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *Thomas 'Ingrid' Barghahn* meinte:

    I opted out of kleopatra. The current version is not supported
    in XP.

    Really? ;-)
    <https://barghahn-online.de/Pictures/win10_kleopatra.png>

    Sorry! Is not "XP"! :-(

    Thomas
    --
    == S E N D E Z E I T ===============
    + DATUM : Freitag, 09. Januar 2026
    + UHRZEIT: 16:15:18 UHR (MEZ)
    == Heute: Tag der Aprikose =========

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Fri Jan 9 13:09:00 2026
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    Hello Th.Barghahn # gmx.de!

    ** On Friday 09.01.26 - 16:11, Th.Barghahn # gmx.de wrote to All:

    Email to and from oxp works, yes.

    Perfect! :-) As I said, this only works with "gpg/inline". Macros or scripts are still required for "gpg/mime".

    An outging inline blosck is fine.

    OXP handles PGP/Decrypt and Signing on messages fine.


    I prefer to manage my keys and manually.

    Ok.

    So.. what else is required now?

    The GPG system works perfectly fine for my other needs.
    Something else needs to be activated or onfigured for OXP.
    What is it?

    - --
    ../|ug
    -----BEGIN PGP SIGNATURE-----

    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAmlhREgACgkQ7w6JZVeJ WJukngf+KE+D/yECOq+UCteZY9Omt83rBPfu/8jTVHhtSVKHpqepYkg2hnnAZbwx 5gGxZd18u7eh98G0YhQojEN3cwH+vIjg08inwdZcJp+3eD+1pvc0HcK+dkkAScuM 8unT+DoOnqhv1tpIYwJzSSzBoCQGxUDPJmDF1L9sZMSMYFcBWsSaTBLw3NO4zzmh evCMdBZAhMLmbPFksfAT0SmXl+51+LV6/lJqAxb33j8Sa2vQIRKH/JYqrgIqhrmq vDbt8r3anUEnv7oSqtvBgEo1JR46UzohS0JTU/UD8v1ZLhGqSeL5mbVALnTTeY8p KSZlPAI4LxWyErOSIdGgN/K6qu54ow==
    =M9XW
    -----END PGP SIGNATURE-----

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Fri Jan 9 20:27:23 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    An outging inline blosck is fine.
    OXP handles PGP/Decrypt and Signing on messages fine.

    So.. what else is required now?

    If encryption and signing using 'gpg/inline' now work for you in OpenXP without any additional tools, then theres nothing more you need to do
    on the OXP side.

    Just to make this absolutely clear: if you want to use gpg/mime, you
    will need additional scripts or macros. OpenXP does not support gpg/mime natively only gpg/inline works out of the box.

    One more important note: since you are still using Windows XP, the
    current version of Kleopatra will no longer run on that system. If a
    modern Kleopatra version were available, you wouldnt need any
    additional scripts or macros, because Kleopatra can fully decode
    PGP/MIME messages on its own.

    Thomas
    --
    == S E N D E Z E I T ===============
    + DATUM : Freitag, 09. Januar 2026
    + UHRZEIT: 20:27:23 UHR (MEZ)
    == Heute: Tag der Aprikose =========

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Fri Jan 9 15:23:00 2026
    Hello Th.Barghahn # gmx.de!

    An outging inline blosck is fine.
    OXP handles PGP/Decrypt and Signing on messages fine.

    So.. what else is required now?

    If encryption and signing using 'gpg/inline' now work for you in OpenXP without any additional tools, then theres nothing more you need to do
    on the OXP side.

    No.. I said, signing [as I showed you in my last reply] and
    decrypt works from OXP's menu options.

    But it does not encrypt a message that I want.

    What are the steps after writing a message to get it to
    encrypt?


    Just to make this absolutely clear: if you want to use gpg/mime, you
    will need additional scripts or macros. OpenXP does not support gpg/mime natively only gpg/inline works out of the box.

    Then, maybe my OXP needs a macro/script to handle creating the
    in-line block!


    One more important note: since you are still using Windows XP, the
    current version of Kleopatra will no longer run on that system. If a modern Kleopatra version were available, you wouldnt need any
    additional scripts or macros, because Kleopatra can fully decode
    PGP/MIME messages on its own.

    Actually, decrypting a mime-message is not a problem in OXP as-
    is. After "Message/PGP../Decode message", the separate sections
    are all listed:

    Message-Part Lines Filename Ŀ
    Vorspann 2
    Text 27
    File (pgp-signature) 13 signature.asc
    Whole Message 56
    EXIT

    ..and I can view any of those decrypted parts.


    And.. as I wrote earlier, enabling Password via TAB/Special/Pw
    does not seem to do anything except fail. What is the PW that
    needs to be entered in the Password field?




    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From AugustA@2:221/10 to Th.Barghahn on Fri Jan 9 18:56:00 2026
    From: AugustA <nospam@nospam.net>

    Hello Th.Barghahn!

    ** On Thursday 08.01.26 - 11:31, Th.Barghahn wrote to :

    Your settings are almost identical to mine.

    Also check your settings for the relevant email addresses:
    [TAB] => Spezial => PW
    <https://barghahn-online.de/Pictures/oxp_tab_pw.png>


    So.. WHAT needs to be placed in the "Password _______" line?

    Is that optional?

    When I leave it blank, and set the other parameter to "PGP" and
    "[x] Crypt" is set, like this..


    ┌─ arnold @ kolico.ca ─────────────────────

    │ Password

    │ Crypt method PGP ↓

    │ [x] Default: Crypt
    │ └──────────────────────────────────────────

    ..a "P" shows up next to the person's email address:

    √ P ~ 1 sveiks a#####@#####.ca


    Then, just before I save it, I see this:

    ┌─ Private message ────────────────────────────────────────

    │ To: a#####@#####.ca

    │ Subject TEST, FRI 6:50p

    │ Server sveiks Code: PGP

    │ Size 71 Bytes Copies: none

    │ Send... Change...
    │ ►Yes◄ No Internal Special Subj. Server Code └──────────────────────────────────────────────────────────


    Then, after I save it, the Sending queue looks like this:

    ■ +!c 71 09.01.26 arnold@kolico.ca sveiks TEST, FRI 6:50p


    So.. I would assume that the "c" at the far left means that the
    message is supposed to be encrypted? But.. I get no gpg
    prompts to do that, and the message sits in-the-clear - not
    encrypted.

    So.. maybe the Linux version does things right, but clearly
    it's not working in the Windows version.


    --
    ../|ug

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Thomas Barghahn@2:221/10 to All on Sat Jan 10 01:07:45 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    If encryption and signing using 'gpg/inline' now work for you in
    OpenXP
    without any additional tools, then there▒s nothing more you need
    to do on the OXP side.

    No.. I said, signing [as I showed you in my last reply] and
    decrypt works from OXP's menu options.

    But it does not encrypt a message that I want.

    What are the steps after writing a message to get it to
    encrypt?

    This is how I create an encrypted and signed email.

    Step 1:
    [TAB]

    Step 2:
    recipient selection

    Step 3:
    [w]rite

    Step 4:
    creating the subject
    <https://barghahn-online.de/Pictures/oxp/Step_4.png>

    Step 5:
    create the message in the editor, save the message,
    close the editor
    <https://barghahn-online.de/Pictures/oxp/Step_5.png>

    Step 6:
    OXP displays this dialog:
    <https://barghahn-online.de/Pictures/oxp/Step_6.png>

    Step 7:
    [Spezial] => ]PGP] (signing the message) <https://barghahn-online.de/Pictures/oxp/Step_7.png>

    Step 8:
    Send ... [Yes]
    <https://barghahn-online.de/Pictures/oxp/Step_8.png>

    Step 9:
    Enter passphrase
    <https://barghahn-online.de/Pictures/oxp/Step_9.png>

    Step 10:
    NetCall
    <https://barghahn-online.de/Pictures/oxp/Step_10.png>

    Ready!

    Thomas
    --
    == S E N D E Z E I T =======================
    + DATUM : Samstag, 10. Januar 2026
    + UHRZEIT: 01:07:45 UHR (MEZ)
    == Heute: Bundesweiter Tag der Blockflöte ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From Thomas Barghahn@2:221/10 to All on Sat Jan 10 01:17:22 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *AugustA* meinte:

    Then, just before I save it, I see this:

    ┌─ Private message ────────────────────────────────────────


    Then, after I save it, the Sending queue looks like this:

    ■ +!c 71 09.01.26 arnold@kolico.ca sveiks TEST, FRI 6:50p

    That's how it should be!

    So.. I would assume that the "c" at the far left means that the
    message is supposed to be encrypted?

    YES! Exactly! :-)


    Thomas
    --
    == S E N D E Z E I T =======================
    + DATUM : Samstag, 10. Januar 2026
    + UHRZEIT: 01:17:22 UHR (MEZ)
    == Heute: Bundesweiter Tag der Blockflöte ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Fri Jan 9 21:18:00 2026
    Hello Th.Barghahn # gmx.de!

    So.. I would assume that the "c" at the far left means that
    the message is supposed to be encrypted?

    YES! Exactly! :-)

    SO.. after some monitoring of the new files that openxp
    creates, I noticed some *new* #####.$$$ files in the TEMP
    directory. Indeed, I noticed that one of the recent ones had
    the PGP BLOCK type.

    That seemed promising. Decrypting it manually proved to be the
    right message.

    I did not realize that any ####.$$$ file was being created, and
    therefore I assumed that the original unencrypted message that
    I saw in my UNSENT list was not encrypted!

    It turns out that the encrypted message *DID* get sent.

    So.. the important thing is to select "[x] Crypt" for the
    specific email recipient, and that "PGP" is selected too.

    And, as you nicely illustrated in your Step_N images, signing
    of that message works as expected too. However, I wonder
    where the signed block is stored? Which TEMP is it?


    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Sat Jan 10 11:29:37 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    So.. the important thing is to select "[x] Crypt" for the
    specific email recipient, and that "PGP" is selected too.

    And, as you nicely illustrated in your Step_N images, signing
    of that message works as expected too. However, I wonder
    where the signed block is stored? Which TEMP is it?

    In the case of PGP/inline, the signature is not stored in a separate
    TEMP file. The entire signed content is the block between:

    -----BEGIN PGP MESSAGE-----
    [...]
    -----END PGP MESSAGE-----

    That block already contains the signed data and the OpenPGP signature
    packet. So there is no additional file everything is embedded
    directly in the message body.

    See:
    RFC 4880 OpenPGP Message Format and
    RFC 9580 OpenPGP (2024)

    Thank you for the nice discussion and have fun with encryption and
    signing in OpenXP! :-)

    Thomas
    --
    == S E N D E Z E I T =======================
    + DATUM : Samstag, 10. Januar 2026
    + UHRZEIT: 11:29:37 UHR (MEZ)
    == Heute: Bundesweiter Tag der Blockflte ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Sat Jan 10 08:37:00 2026
    Hello Th.Barghahn # gmx.de!

    ** On Saturday 10.01.26 - 11:29, Th.Barghahn # gmx.de wrote to All:

    In the case of PGP/inline, the signature is not stored in
    a separate TEMP file. The entire signed content is the
    block between:

    -----BEGIN PGP MESSAGE-----
    [...]
    -----END PGP MESSAGE-----

    That block already contains the signed data and the
    OpenPGP signature packet. So there is no additional file
    everything is embedded directly in the message body.


    Ah.. I should have noticed the "valid signature" when I tested
    the ####.$$$ temp file.

    Thx.


    Thank you for the nice discussion and have fun with
    encryption and signing in OpenXP! :-)

    Yes.. that went wel.. Thx for your interest to work through the
    matter. :)

    I have recently received mime-type email from someone. OpenXP
    can't seem to handle that on its own. Basically, the messages
    seem to arrive in base64.

    Eg.

    Content-Disposition: inline

    This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)

    --2wErROdFz89KWACh58u=_36ptLjUNwMbIq
    Content-Type: application/pgp-encrypted
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment
    Content-Description: PGP/MIME version identification

    VmVyc2lvbjogMQ0KDQo=

    --2wErROdFz89KWACh58u=_36ptLjUNwMbIq
    Content-Type: application/octet-stream;
    name="encrypted.asc"
    Content-Transfer-Encoding: base64
    Content-Disposition: inline;
    filename="encrypted.asc"
    Content-Description: OpenPGP encrypted message

    LS0tLS1CRUdJTiBQR1AgTUVTU0FHRS0tLS0tDQoNCmhRRU1BMWc3S2ExcDBKbW VFZyb2dlbUJlaXNBMlNqdjA1dDlKRlI3QldtUSthUmNKK0M2QmcNClNzVzczVT
    [...]

    OPX can show me the PGP BLOCK of the encrypted.asc file, which
    it saves to a temporary external file in the FILES dir, then I
    can drop to the cmdline and execute "gpg -d [FILE]" ..and I
    can view the message onscreen.

    Do you have ready-made macros or a Tools script-line that you
    can tell me about that will handle mime-type?


    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From Thomas Barghahn@2:221/10 to All on Sat Jan 10 23:04:44 2026
    From: Thomas Barghahn <Th.Barghahn@t-online.de>

    *August Abolins* meinte:

    OPX can show me the PGP BLOCK of the encrypted.asc file, which
    it saves to a temporary external file in the FILES dir, then I
    can drop to the cmdline and execute "gpg -d [FILE]" ..and I
    can view the message onscreen.

    Do you have ready-made macros or a Tools script-line that you
    can tell me about that will handle mime-type?

    In this case, you need "Kleopatra" *and* a "base64 decoder"
    OR:
    own gpg tools *and* a "base64 decoder".

    See my procedure:
    -----------------

    Step 1:
    select the email to be decrypted <https://barghahn-online.de/Pictures/oxp/Step_1_decrypt.png>

    Step 2:
    select "File ... encrypted.asc" <https://barghahn-online.de/Pictures/oxp/Step_2_decrypt.png>

    Step 3:
    copy/save the entire part:
    -----BEGIN PGP MESSAGE-----
    [...]
    -----END PGP MESSAGE-----
    to the clipboard (Linux) => Result File: ~/.openxp/temp/.openxp.clipboard.1000 in File: "out.asc"
    <https://barghahn-online.de/Pictures/oxp/Step_3_decrypt.png>

    STEP 4.1:

    +++ with "Kleopatra" - START +++
    |
    | Step 4.1.1:
    | Tools => Clipboard => encrypt/decrypt
    | <https://barghahn-online.de/Pictures/oxp/Step_4_1_1_decrypt.png>
    |
    | Step 4.1.2:
    | Enter passphrase
    | <https://barghahn-online.de/Pictures/oxp/Step_4_1_2_decrypt.png>
    |
    | Step 4.1.3:
    | check Sig and close "Kleopatra"
    | <https://barghahn-online.de/Pictures/oxp/Step_4_1_3_decrypt.png>
    |
    +++ with "Kleopatra" - END +++

    STEP 4.2:

    +++ w/o "Kleopatra" - START +++
    |
    | || !! Create Tools-Menu !!
    | || Menu display: decr. gpg/mime
    | || <https://barghahn-online.de/Pictures/oxp/Step_4_2_decrypt.png>
    | ||
    | || Linux:
    | || ------
    | || Program name: gpg -d -o ~/.openxp/temp/input.txt ~/.openxp/temp/.openxp.clipboard.1000
    | ||
    | || Windows11:
    | || ----------
    | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt d:\my_programs\open_xp\files\out.txt
    |
    | Step 4.2.1:
    | Tools => decr. gpg/mime
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png>
    |
    | Step 4.2.2:
    | Enter passphrase
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png>
    |
    +++ w/o "Kleopatra" - END +++

    Step 5:
    open the file "input.txt" in your preferred editor and copy the
    "base64 part" to the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png>

    Step 6:
    open your "base64 decoder"[1] and paste from the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png>

    Step 7:
    decode the base64 part <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png>

    Ready! :-)

    [1] Copyright by Thomas Barghahn ;-)

    Thomas
    --
    == S E N D E Z E I T =======================
    + DATUM : Samstag, 10. Januar 2026
    + UHRZEIT: 23:04:44 UHR (MEZ)
    == Heute: Bundesweiter Tag der Blockflte ==

    ---
    * Origin: rbb sglnx - the fidonet nntp junction (2:221/10)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Sun Jan 11 19:34:00 2026
    Hello Th.Barghahn # gmx.de!

    STEP 4.2:

    +++ w/o "Kleopatra" - START +++
    |
    | || !! Create Tools-Menu !!
    | || Menu display: decr. gpg/mime
    | || <https://barghahn-online.de/Pictures/oxp/Step_4_2_decrypt.png>
    | ||
    | || Windows11:
    | || ----------
    | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt d:\my_programs\open_xp\files\out.txt |

    My dilema.. How do I know what file OXP uses as the temp file
    after saving a message or seletion to Clipboard?

    For example, I saved this message to Clipboard and noticed a
    new temp file that contains the content:

    3382 2026-01-11 19:24:04.406250000 TEMP/1892.$$$

    But.. if that file name is always different, how can I build
    the proper Program line to use it as imput?

    Is the selection to clipboard represented by the $FILE
    variable?



    | Step 4.2.1:
    | Tools => decr. gpg/mime
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png>
    |
    | Step 4.2.2:
    | Enter passphrase
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png>
    |
    +++ w/o "Kleopatra" - END +++

    All that helped. Thx!


    Step 5:
    open the file "input.txt" in your preferred editor and copy the
    "base64 part" to the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png>

    Step 6:
    open your "base64 decoder"[1] and paste from the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png>

    Step 7:
    decode the base64 part <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png>

    I could prabably build the decrypt base64 tool with:

    "busybox base64 -d [FILE]

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Sun Jan 11 19:55:00 2026
    Hello Th.Barghahn # gmx.de!

    STEP 4.2:

    +++ w/o "Kleopatra" - START +++
    |
    | || !! Create Tools-Menu !!
    | || Menu display: decr. gpg/mime
    | || Windows11:
    | || ----------
    | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt d:\my_programs\open_xp\files\out.txt |


    Ok.. So mine should be this?

    Tools Menu 5 Ŀ

    Menu display decrypt gpg/mime

    Program name gpg -d -o de-mime.txt $FILE

    $FILE-Msg. w/o header  [ ] Subject-name

    [ ] Wait
    [x] Fullscreen Memory: 600 KBytes
    [ ] Output to lister
    [ ] Look for files in AUTOEXEC directory


    So... I open the message particulars:

    Message-Part Lines Filename Ŀ
    Vorspann 2
    Text 2
    File (pgp-encrypted) 2
    File 52 encrypted.asc
    Whole Message 79
    EXIT

    ..Then, I select the enrypted.asc, and open that up to view,
    and then copy that clipboard?








    | Step 4.2.1:
    | Tools => decr. gpg/mime
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_1_decrypt.png>
    |
    | Step 4.2.2:
    | Enter passphrase
    | <https://barghahn-online.de/Pictures/oxp/Step_4_2_2_decrypt.png>
    |
    +++ w/o "Kleopatra" - END +++

    Step 5:
    open the file "input.txt" in your preferred editor and copy the
    "base64 part" to the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png>

    Step 6:
    open your "base64 decoder"[1] and paste from the clipboard. <https://barghahn-online.de/Pictures/oxp/Step_6_decrypt.png>

    Step 7:
    decode the base64 part <https://barghahn-online.de/Pictures/oxp/Step_7_decrypt.png>

    Ready! :-)

    [1] Copyright by Thomas Barghahn ;-)

    Thomas
    --
    == S E N D E Z E I T =======================
    + DATUM : Samstag, 10. Januar 2026
    + UHRZEIT: 23:04:44 UHR (MEZ)
    == Heute: Bundesweiter Tag der Blockflte ==

    -+-
    + Origin: rbb sglnx - the fidonet nntp junction (2:221/10)

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Sun Jan 11 21:36:00 2026
    Hello Th.Barghahn # gmx.de!

    Oops.. I accidentally sent off an unfinished reply!

    I'll try to finish it properly below..



    STEP 4.2:

    +++ w/o "Kleopatra" - START +++
    |
    | || !! Create Tools-Menu !!
    | || Menu display: decr. gpg/mime
    | || Windows11:
    | || ----------
    | || Program name: gpg -d -o d:\my_programs\open_xp\files\input.txt
    d:\my_programs\open_xp\files\out.txt |


    Ok.. So mine should be this?

    Tools Menu 5 Ŀ

    Menu display decrypt gpg/mime

    Program name gpg -d -o de-mime.txt $FILE

    $FILE-Msg. w/o header  [ ] Subject-name

    [ ] Wait
    [x] Fullscreen Memory: 600 KBytes
    [ ] Output to lister
    [ ] Look for files in AUTOEXEC directory



    The file de-mime.txt would be the decrypted output of the whole
    message. But in this case, $FILE did not work as expected.

    Instead, I modified the "Program.." line above to:

    gpg -d -o de-mime.txt mime


    So... I open the message particulars:

    Message-Part Lines Filename Ŀ
    Vorspann 2
    Text 2
    File (pgp-encrypted) 2
    File 52 encrypted.asc
    Whole Message 79
    EXIT

    ..Then, I select the enrypted.asc, and open that up to view,
    and then copy that clipboard?

    The problem with copying to clipboard is that OXP saves the
    content to randomly numbered files in the TEMP diretory like
    this:

    3392.$$$
    8745.$$$

    ..etc.

    So.. I can't really program the line like this..

    gpg -d -o de-mime.txt 3392.$$$

    ..because I'll never know what the .$$$ file will be named.


    HOWEVER, I can save the encrypted.asc block to a specific file,
    say.. "mime.txt"

    ..and then I can use this:

    gpg -d -o de-mime.txt FILES\mime.txt

    ..and that produces a decrypted file called "de-mime.txt" in
    the home directory.


    Step 5:
    open the file "input.txt" in your preferred editor and copy the
    "base64 part" to the clipboard.
    <https://barghahn-online.de/Pictures/oxp/Step_5_decrypt.png>

    I haven't received anything with a base64 part yet. But it
    appears that is basically the same kind of steps as decrypting
    encrypted.asc, but instead save the base64 block to a file and
    run a tool to decode it.

    I suppose "busybox base64 -d FILE > readme.txt" ..would work?



    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)
  • From August Abolins@2:221/1.58 to Thomas Barghahn on Thu Jan 15 20:27:00 2026
    Hello Th.Barghahn # gmx.de!


    Some UPDATES on my foray into this venture..


    gpg -d -o de-mime.txt mime

    So... I open the message particulars:

    Message-Part Lines Filename Ŀ
    Vorspann 2
    Text 2
    File (pgp-encrypted) 2
    File 52 encrypted.asc
    Whole Message 79
    EXIT


    ..Then, I select the enrypted.asc, and open that up to view,
    and then copy that clipboard?

    The problem with copying to clipboard is that OXP saves the
    content to randomly numbered files in the TEMP diretory like
    this:

    3392.$$$
    8745.$$$

    ..etc.

    So.. I can't really program the line like this..

    gpg -d -o de-mime.txt 3392.$$$

    ..because I'll never know what the .$$$ file will be named.


    HOWEVER, I can save the encrypted.asc block to a specific file,
    say.. "mime.txt"

    ..and then I can use this:

    gpg -d -o de-mime.txt FILES\mime.txt

    ..and that produces a decrypted file called "de-mime.txt" in
    the home directory.


    I still haven't received anything with a true base64 part, but
    I tried to streamline the decrypt process for the
    "enrypted.asc" part.

    I tried this as one of the Tools:

    gpg -d -o mime files\mime && type mime | more

    (were "mime" is the name of the file where I copy the
    encrypted.asc content with the W key.)


    ..but openxp didn't know how to handle the part after &&

    So, I created two Tool lines:

    5 gpg -d -o mime files\mime
    6 type mime | more

    That worked. But "type.." tended to be quite limited and
    awkward especially with a longer message. So.. this was *much*
    better:

    6 busybox less mime

    The less command allows scrolling the displayed text up and down!

    :D


    NEXT, it would be much nicer if the decrypted encrypted.asc
    could become part of the message database for a particular
    message so that I wouldn't have to go through the whole Tools
    process each time.

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: (2:221/1.58)