diff options
| author | saturneric <[email protected]> | 2025-06-24 13:22:48 +0000 | 
|---|---|---|
| committer | saturneric <[email protected]> | 2025-06-24 13:22:48 +0000 | 
| commit | a026a0464efd8fee8ad47a1f6a2bf4ebe189e5f3 (patch) | |
| tree | e40fef9a78bd8c01cd4bd3de664fa0ef14fe9b56 /src/content/docs/guides/email-operations.md | |
| parent | docs: update image urls in documentation guides (diff) | |
| download | Manual-a026a0464efd8fee8ad47a1f6a2bf4ebe189e5f3.tar.gz Manual-a026a0464efd8fee8ad47a1f6a2bf4ebe189e5f3.zip | |
docs(guides): restructure email operations documentation
- reorganized sections for better flow
- simplified bullet point formatting
- updated image references
- removed redundant headers
- consolidated best practices section
Diffstat (limited to 'src/content/docs/guides/email-operations.md')
| -rw-r--r-- | src/content/docs/guides/email-operations.md | 74 | 
1 files changed, 29 insertions, 45 deletions
| diff --git a/src/content/docs/guides/email-operations.md b/src/content/docs/guides/email-operations.md index 858ba27..01d7f28 100644 --- a/src/content/docs/guides/email-operations.md +++ b/src/content/docs/guides/email-operations.md @@ -46,38 +46,37 @@ other OpenPGP-enabled clients.    - **Decrypt and Verify Together or Separately**: Flexibly handle incoming      messages. -### Creating and Processing Emails - -#### Creating and Signing Emails +### Creating and Signing Emails  1. Open GpgFrontend and click **"New E-Mail"** to create a blank email. - - -  2. Type your email content in the editor.  3. Select your private key from the **Key Toolbox**.  4. Click **"Sign"** to digitally sign the email. -   - Signed emails include a PGP signature block, visible in the content. +5. Fill Sender, Receiver and the Subject of the email. + + - + -#### Encrypting Emails + + + + +### Encrypting Emails  1. Select the recipient's public key in the **Key Toolbox**. -2. Click **"Encrypt"** to secure the email content. -   - The content will be transformed into a PGP-encrypted format. +2. Click **"Encrypt"** to secure the email content. The content will be +   transformed into a PGP-encrypted format. - + -#### Saving Emails for Sending +### Saving Emails for Sending  1. Processed emails can be saved as `.eml` files using **File > Save As**.  2. Upload the `.eml` file to your email client's drafts folder or webmail     interface, then send the email. -### Receiving and Processing Emails - -#### Decrypting and Verifying Emails +### Decrypting and Verifying Emails  1. Export the email source as an `.eml` file from your email client or copy the     raw email source. @@ -87,9 +86,9 @@ other OpenPGP-enabled clients.     - **"Verify"**: Validate the signature without decrypting.     - **"Decrypt"**: Decrypt without verifying. - + -#### Offline Validation +### Offline Validation  - GpgFrontend processes all email verification and decryption offline, ensuring    that no sensitive data is exposed to external servers. @@ -97,21 +96,19 @@ other OpenPGP-enabled clients.  ### Why Use EML Format? -#### Benefits of EML -  - `.eml` is a widely supported format across email clients like Thunderbird,    Outlook, and webmail platforms.  - Unlike proprietary email handling protocols, `.eml` allows for seamless    export, import, and offline processing. -#### Why Not Use IMAP/SMTP? +### Why Not Use IMAP/SMTP?  - Avoids the complexity and potential vulnerabilities introduced by integrating    full-fledged email protocols.  - Keeps the application lightweight and focused on local cryptographic    operations. -#### Addressing PGP Limitations in Clients +### Addressing PGP Limitations in Clients  - Many email clients lack robust PGP support or offer inconsistent    implementations. @@ -157,26 +154,13 @@ other OpenPGP-enabled clients.  ## Best Practices for Secure Email Handling -1. **Use Trusted Keys**: - -   - Regularly validate public keys to prevent misuse. -   - Import keys only from trusted sources. - -2. **Keep Private Keys Offline**: - -   - Avoid uploading private keys to email providers. -   - Store private keys securely, preferably on encrypted storage. - -3. **Leverage GpgFrontend's Local Processing**: - -   - Ensure all encryption, signing, and verification tasks are performed -     offline for maximum security. - -4. **Save Emails in EML Format**: - -   - Use `.eml` files for cross-platform compatibility and simple integration -     with various email clients. - -5. **Check Email Compatibility**: -   - Ensure recipients can handle PGP-encrypted emails or provide instructions -     for using tools like GpgFrontend or Thunderbird. +- Use Trusted Keys: Regularly validate public keys to prevent misuse and import +  keys only from trusted sources. +- Keep Private Keys Offline: Avoid uploading private keys to email providers and +  store private keys securely, preferably on encrypted storage. +- Leverage GpgFrontend's Local Processing: Ensure all encryption, signing, and +  verification tasks are performed offline for maximum security. +- Save Emails in EML Format: Use `.eml` files for cross-platform compatibility +  and simple integration with various email clients. +- Check Email Compatibility: Ensure recipients can handle PGP-encrypted emails +  or provide instructions for using tools like GpgFrontend or Thunderbird. | 
