Contact us page

[Pato-desu]

• The form is huge. too much space in between things.
• Change some wording
• And it is a bit overlapping with "Partnerships"
• And "Press"
• And even with "Send us feedback"
• Not sure where the second form should send emails to, I need to create that address prob
• Add mailersend integration
• Have to test both forms in local
• adding API key
• Fixing whatever is happening with the API

[netlify]

✅ Deploy Preview for pauseai ready!

Name	Link
🔨 Latest commit	957dc0a
🔍 Latest deploy log	https://app.netlify.com/projects/pauseai/deploys/695d897e26b12a0008808b4a
😎 Deploy Preview	https://deploy-preview-616--pauseai.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 64 (🔴 down 16 from production) Accessibility: 90 (no change from production) Best Practices: 100 (no change from production) SEO: 98 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[joepio]

I created a new MAILERSEND_API_KEY API key ENV with post permissions and added it to netlify. Note that I renamed the other, existing Mailersend token to "DEVELOPMENT", the new one is "PRODUCTION"

[Pato-desu]

@joepio You're sure everything is set up correctly? I'm having trouble on the deploy preview but it's working on local.

Gemini:
I've investigated the issue thoroughly and found the likely cause of the 500 Internal Server Error. The problem appears to be with your MailerSend configuration, which is handled in src/routes/contact-us/+page.server.ts.
Please verify the following:
MAILERSEND_API_KEY: Ensure that the MAILERSEND_API_KEY environment variable is correctly set in your Netlify project settings. This key is essential for authenticating with the MailerSend service.

[anthonybailey]

If you do struggle with any "mail from Pause AI" issues, note that sending mail under apps using Google's own SMTP at rates up to 2,000 emails/day has proved easy, robust, and better insulated from spam detection concerns. Just making sure people know their options.

…

On Tue, 6 Jan 2026, 22:38 Pato-desu, ***@***.***> wrote: *Pato-desu* left a comment (PauseAI/pauseai-website#616) <#616 (comment)> @joepio <https://github.com/joepio> You're sure everything is set up correctly? I'm having trouble on the deploy preview but it's working on local. Gemini: I've investigated the issue thoroughly and found the likely cause of the 500 Internal Server Error. The problem appears to be with your MailerSend configuration, which is handled in src/routes/contact-us/+page.server.ts. Please verify the following: MAILERSEND_API_KEY: Ensure that the MAILERSEND_API_KEY environment variable is correctly set in your Netlify project settings. This key is essential for authenticating with the MailerSend service. — Reply to this email directly, view it on GitHub <#616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAXXDPL6GICIOONEQTSNC34FQ2PTAVCNFSM6AAAAACQTVTNFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJWGYYTONRQGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Pato-desu]

Yeah, but it would be useful in the future if we had mailersend integrated to be able to use templates for example

[anthonybailey]

Capturing some detail.

Joep's comment advising he changed the key is dated Jan 6 09:59 UTC and presumed after making the the change.

Pato's commit 957dc0a is marked same day PM in a not specified timezone, and appears after Joep's comment, so should have picked up the new environment value.

In Netlify said env is annotated "Same value in all deploy contexts. Joep Meindertsma updated 11 days ago" (FFS what is it with dev tools not specifying timestamps) and has prefix mlsn.416ee

The deploy preview web UX reports just "An unexpected error occurred" on submit.

[anthonybailey]

Yeah here we go in edge function log:

Jan 17, 06:42:48 AM: 01KF5B2B error [render]
[500] POST /contact-us
Error: Dynamic require of "node:https" is not supported
at file:///root/.netlify/edge-functions/render.js:15:9

The mailersend SDK isn't edge-compatible. It depends on gaxios which uses Node's node:https, and edge functions run on Deno (not the Node runtime.)

When you were running locally (perhaps under dev) you won't have manifested the same issue. You can if you use "netlify serve" but even then the version of Deno Netlify use is not directly matchable in dev.

Options:

You could move to serverless function. This would rename/move the handler so Netlify routes it through Node.js functions instead of edge. This is "correct" and conventional, but doesn't match our usual website choices so could be another can of worms for you.

Probably simplest: replace the Mailersend SDK call with a raw fetch — Mailersend's API is simple enough that you can call it directly with fetch(), which works everywhere. Eliminates the dependency.

(Really simplest as noted previously: consistently use Google apps to send Gmail.)

@Pato-desu that should unblock you and with more help from Gemini I suspect you can determine the URL, code and test the raw fetch.