Skip to content

Update dify-plugin-email-html-pro.difypkg v0.0.3#2445

Merged
crazywoola merged 2 commits into
langgenius:mainfrom
abesticode:abesticode/email-html-pro-v0.0.3
May 21, 2026
Merged

Update dify-plugin-email-html-pro.difypkg v0.0.3#2445
crazywoola merged 2 commits into
langgenius:mainfrom
abesticode:abesticode/email-html-pro-v0.0.3

Conversation

@abesticode
Copy link
Copy Markdown
Contributor

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Version 0.0.3 - Added SMTP relay support without authentication.

Changes:

  • SMTP Relay Support: Plugin now works with unauthenticated SMTP relay servers (e.g., internal company relay servers) in addition to authenticated SMTP servers (Gmail, AWS SES, Outlook, etc.)
  • Optional Authentication: Email Account and Email Password credentials are now optional. Leave them empty for relay servers that do not require authentication.
  • Sender Address Requirement: Sender Address is now required when Email Account is not provided, ensuring a valid "From" address is always set.
  • Provider Validation: When no authentication credentials are provided, the provider validates connectivity using an SMTP connection test (EHLO) instead of sending a test email.
  • Updated Documentation: README updated with SMTP relay configuration example and updated credential requirements.

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 user-provided data for email delivery purposes only:

  • Email addresses: Sender, recipient, CC, and BCC email addresses
  • SMTP credentials: Email account and password for SMTP authentication (optional, not stored)
  • Email content: Subject and body content provided by the user

No data is collected, stored, or shared with third parties. All data is used solely for the purpose of sending emails via 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

@abesticode
Copy link
Copy Markdown
Contributor Author

hi @crazywoola , can you accept for this PR ?
thank you.

Copy link
Copy Markdown
Member

@crazywoola crazywoola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM

Decision: Approve

Local Check Results

Check Status Detail Required action
PR content language ✅ Pass PR title/body CJK ratio=0.0% (zh=0, en=2729, ignored_zh=0, allowed_zh<=0) None.
Project structure ✅ Pass All expected files present: manifest.yaml, README.md, PRIVACY.md. _assets/: yes. None.
Manifest author ✅ Pass author is valid. None.
Icon validation ✅ Pass icon exists: _assets/icon.svg None.
Version check ✅ Pass version 0.0.3 is available. None.
README language ✅ Pass README.md CJK ratio=0.0% (zh=0, en=3384, allowed_zh<=0) None.
PRIVACY.md ✅ Pass PRIVACY.md exists and is non-empty. None.
Dependency install ✅ Pass requirements installed successfully. None.
dify_plugin version ✅ Pass dify_plugin version 0.6.2 satisfies >= 0.5.0. None.
Install test ✅ Pass plugin install test passed. None.
Packaging test ✅ Pass packaging check passed. None.

@crazywoola crazywoola merged commit 2872194 into langgenius:main May 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants