langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1790] [CLOSED] feat: add email-html-pro plugin #1851

New Issue
Closed
opened 2026-02-22 18:09:53 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:09:53 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1790
Author: @abesticode
Created: 12/24/2025
Status: ❌ Closed

Base: main ← Head: main

📄 Description

  • Add email_html_pro plugin with HTML email support and raw HTML feature

  • Reorganize knowledge_pro plugin into dedicated folder

  • Remove deprecated difypkg from root abesticode folder

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Email HTML Pro is a professional email sending plugin for Dify that enables sending HTML emails via SMTP with comprehensive template support.

Key Features:

  • Raw HTML Templates: Send pre-built HTML templates without any modification - perfect for marketing emails and custom designs
  • Markdown to HTML: Automatically convert markdown content to beautifully formatted HTML emails
  • SMTP Compatibility: Works with Gmail, AWS SES, and any standard SMTP server
  • File Attachments: Attach multiple files to emails
  • Batch Sending: Send to multiple recipients at once
  • CC/BCC Support: Include carbon copy and blind carbon copy recipients
  • Reply-To: Set custom reply-to addresses
  • Encryption: Support for SSL, TLS, or no encryption

Tools Included:

  1. Send Email: Send a single email to one recipient
  2. Send Batch Email: Send emails to multiple recipients at once

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin processes the following data during email operations:

  • Email addresses: Sender, recipients, CC, and BCC addresses (used only for email delivery, not stored)
  • SMTP credentials: Server, port, email account, and password (stored encrypted by Dify's credential system)
  • Email content: Subject, body, and attachments (processed in-memory only, not retained)

Note: No data is collected or stored by this plugin. All data is processed in real-time and transmitted directly to the configured SMTP server.

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1790 **Author:** [@abesticode](https://github.com/abesticode) **Created:** 12/24/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📄 Description - Add email_html_pro plugin with HTML email support and raw HTML feature - Reorganize knowledge_pro plugin into dedicated folder - Remove deprecated difypkg from root abesticode folder # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: abesticode - **Plugin Name**: email_html_pro - **Repository URL**: https://github.com/abesticode/dify-plugin-email-html-pro ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> **Email HTML Pro** is a professional email sending plugin for Dify that enables sending HTML emails via SMTP with comprehensive template support. ### Key Features: - **Raw HTML Templates**: Send pre-built HTML templates without any modification - perfect for marketing emails and custom designs - **Markdown to HTML**: Automatically convert markdown content to beautifully formatted HTML emails - **SMTP Compatibility**: Works with Gmail, AWS SES, and any standard SMTP server - **File Attachments**: Attach multiple files to emails - **Batch Sending**: Send to multiple recipients at once - **CC/BCC Support**: Include carbon copy and blind carbon copy recipients - **Reply-To**: Set custom reply-to addresses - **Encryption**: Support for SSL, TLS, or no encryption ### Tools Included: 1. **Send Email**: Send a single email to one recipient 2. **Send Batch Email**: Send emails to multiple recipients at once ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> This plugin processes the following data during email operations: - **Email addresses**: Sender, recipients, CC, and BCC addresses (used only for email delivery, not stored) - **SMTP credentials**: Server, port, email account, and password (stored encrypted by Dify's credential system) - **Email content**: Subject, body, and attachments (processed in-memory only, not retained) **Note**: No data is collected or stored by this plugin. All data is processed in real-time and transmitted directly to the configured SMTP server. ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:09:53 -05:00
yindo closed this issue 2026-02-22 18:09:53 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1851
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?