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 #1834] [MERGED] chore: update dify-plugin-email-html-pro.difypkg to v0.0.2 #1890

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

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1834
Author: @abesticode
Created: 12/31/2025
Status: ✅ Merged
Merged: 1/5/2026
Merged by: @crazywoola

Base: main ← Head: abesticode/add-email-html-pro

📝 Commits (2)

  • df7e616 chore: update dify-plugin-email-html-pro.difypkg to v0.0.2
  • 6e55850 fix(email_html_pro): support AWS SES IAM credentials for SMTP authentication

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 abesticode/email_html_pro/dify-plugin-email-html-pro.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Version 0.0.2 Update:

New Features:

  • Added animated SVG icons with CSS animations:
    • Floating envelope animation effect
    • Typing HTML brackets (</>) with staggered delay
    • Pulsing shine effect

Bug Fixes:

  • Fixed AWS SES compatibility: Removed email format validation for SMTP username (email_account) to support AWS SES IAM credentials
  • Added proper validation for sender_address field
  • Improved error messages for AWS SES configuration

Documentation:

  • Updated author link in README
  • Added changelog section to documentation

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 uses user-provided SMTP credentials to send emails. The following data is processed but not collected or stored:

  • Email addresses (sender, recipients, CC, BCC, reply-to)
  • Email content (subject, body)

All data is transmitted directly to the user's configured SMTP server and is not stored, logged, or transmitted to any third-party services.

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/1834 **Author:** [@abesticode](https://github.com/abesticode) **Created:** 12/31/2025 **Status:** ✅ Merged **Merged:** 1/5/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `abesticode/add-email-html-pro` --- ### 📝 Commits (2) - [`df7e616`](https://github.com/langgenius/dify-plugins/commit/df7e61693f4e4090b6af2cbdc583860ae2f23895) chore: update dify-plugin-email-html-pro.difypkg to v0.0.2 - [`6e55850`](https://github.com/langgenius/dify-plugins/commit/6e55850602324bf36b7491a2052555426db252c8) fix(email_html_pro): support AWS SES IAM credentials for SMTP authentication ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `abesticode/email_html_pro/dify-plugin-email-html-pro.difypkg` (+0 -0) </details> ### 📄 Description # 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 - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> **Version 0.0.2 Update:** ### New Features: - Added animated SVG icons with CSS animations: - Floating envelope animation effect - Typing HTML brackets (`</>`) with staggered delay - Pulsing shine effect ### Bug Fixes: - **Fixed AWS SES compatibility**: Removed email format validation for SMTP username (email_account) to support AWS SES IAM credentials - Added proper validation for sender_address field - Improved error messages for AWS SES configuration ### Documentation: - Updated author link in README - Added changelog section to documentation ## 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 uses user-provided SMTP credentials to send emails. The following data is processed but **not collected or stored**: - Email addresses (sender, recipients, CC, BCC, reply-to) - Email content (subject, body) All data is transmitted directly to the user's configured SMTP server and is not stored, logged, or transmitted to any third-party services. ### 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:10:51 -05:00
yindo closed this issue 2026-02-22 18:10:51 -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#1890
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?