sh4yy / cloudflare-email Goto Github PK

It seems like this should use Worker Secrets to store the configuration, no?

I can not run this command:
npx wrangler secret put --env production TOKEN

X [ERROR] A request to the Cloudflare API (/accounts/xxxxxxxx/workers/scripts/worker-email-production/secrets) failed.

Authentication error [code: 10000]

Getting User settings...
👋 You are logged in with an OAuth Token, associated with the email [email protected]!
┌───────────────────────────────────┬──────────────────────────────────┐
│ Account Name │ Account ID │
├───────────────────────────────────┼──────────────────────────────────┤
│ [email protected]'s Account │ 07f655250xxxxxx │
└───────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)

• account (read)
• user (read)
• workers (write)
• workers_kv (write)
• workers_routes (write)
• workers_scripts (write)
• workers_tail (read)
• d1 (write)
• pages (write)
• zone (read)
• ssl_certs (write)
• constellation (write)
• ai (write)
• queues (write)
• offline_access

Hi,

How can we use this to send notification mails from websites like wordpress and other?
or like a smtp service.

I am trying to understand how this is 'free' and what the limits are? Especially since it uses MailChannels as a relay, whose services start at $500 USD/month.

I have deploy my this worker into production.

And added a SPF record and a _mailchannels record to my domainA.

And added a custom domainB to my worker.

Then try to POST https://domainB/api/email the body below:

{
	"to": "[email protected]",
	"from": "support@domainA",
	"subject": "Hello World",
	"text": "Hello World"
}

But it always showed Internal Server Error.

Is there anything I missing to use this email sender?

Hi,

I am trying to install this with the cloudflare deploy option,but after now 1 hour the status still showing " [Initializing] "
Is this still working or not, or should i do some pre settings before deploy ?

Since launching our free email sending API for Cloudflare Workers customers, we have been proud to provide a simple yet effective solution to deliver messages from Workers code with a minimum of setup complexity. Unfortunately, we regret to announce that this free service will be coming to an end on June 30th, 2024.

What's next?
Cloudflare customers utilizing the free MailChannels email API have until 5:00 PM Pacific Daylight Savings Time (UTC-7) on June 30th, 2024 to transition to an alternative email delivery solution. After that date, the API endpoint will begin rejecting connections from unauthorized senders. As soon as June 1st, 2024, we will begin failing a small fraction of API requests and including a link to this article in the error message.

Source: https://support.mailchannels.com/hc/en-us/articles/26814255454093-End-of-Life-Notice-Cloudflare-Workers

Found this repo for the first time today, was excited to use it, didn't think this journey would end before it even started :(

RIP

Hey there, it is not possible to auto deploy this repository as it is missing a github workflow that does so. The manual instructions do work so I assume it was just an oversight?

Following the docs on how to setup DKIM it looks like we need to be able to pass a couple of things to the personalization object such as dkim_private_key.

As far as I can tell the worker currently doesn’t support that. Am I missing something?

Was thinking about this. I don't have time to work on it tonight, but it might be nice to optionally return any errors to the caller in the HTTP body.

This could be disabled via an env variable.

Replace === with crypto.subtle.timingSafeEqual in https://github.com/Sh4yy/cloudflare-email/blob/main/src/middlewares/auth.ts#L16 to prevent timing attacks.

Example: https://developers.cloudflare.com/workers/examples/protect-against-timing-attacks/

can you add functionality for attaching files