Cloudflare mail via mailchannels :D

[fforres]

Funcionan! Y son gratis :D

Eventualmente deberiamos ponerle DKIM https://support.mailchannels.com/hc/en-us/articles/7122849237389-Adding-a-DKIM-Signature

Ya les puse domain lockdown y spf1 records

• https://support.mailchannels.com/hc/en-us/articles/16918954360845-Secure-your-domain-name-against-spoofing-with-Domain-Lockdown
• https://support.mailchannels.com/hc/en-us/articles/200262610-Set-up-SPF-Records

Completa un par de items en: #142

---

Nuevo correo

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	85.47%	8076 / 9448
🔵	Statements	85.47%	8076 / 9448
🔵	Functions	84.17%	266 / 316
🔵	Branches	82.77%	668 / 807

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
emails/helpers/index.ts	27.27%	0%	0%	27.27%	4-11
emails/helpers/tickets.tsx	25%	100%	0%	25%	18-72, 76-83
emails/templates/tickets/purchase-order-successful.tsx	25.29%	100%	0%	25.29%	42-168
src/datasources/db/events.ts	100%	100%	100%	100%
src/datasources/db/userTickets.ts	100%	100%	100%	100%
src/datasources/email/sendEmailToWorkers.ts	1.85%	100%	0%	1.85%	2-54

Generated in workflow #600

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@react-email/[email protected]	None	+23	8.76 MB	gabrielmfern
npm/[email protected]	None	0	22.2 MB	kossnocorp

🚮 Removed packages: npm/@react-email/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/@swc/[email protected]	Install script: postinstall Source: node postinstall.js	orphan: npm/@swc/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@swc/[email protected]