Always with the same `mailfrom` domain, as the one in that screenshot?

Always with the same

mailfrom

mailfrom

mailfrom

mailfrom domain, as the one in that screenshot?

DDarkDeviL Always with the same `mailfrom` domain, as the one in that screenshot?

addison•2/23/24, 5:02 AM

yeah always that domain, does it have to be the same domain as from? I assume not

DarkDeviLOP•2/23/24, 5:03 AM

Technically, no, they can be two completely different domain names (as well as the local parts, i.e. the stuff before

DarkDeviLOP•2/23/24, 5:06 AM

However, one thing I notice digging on that domain name:

You do not have a _mailchannels_mailchannels TXT record, for their Domain Lockdown.

addison•2/23/24, 5:08 AM

ohhh does mailfrom need the record too? ill give that a shot

addison•2/23/24, 5:18 AM

there was an invalid mailchannels record but i swapped it with the valid one and still no luck

Aaddison ohhh does mailfrom need the record too? ill give that a shot

DarkDeviLOP•2/23/24, 5:21 AM

The "Domain Lockdown" thing was supposed to "fix" a problem where every Workers user, could pretend to be someone else's domain, and pass SPF checks, due to the wide include:relay.mailchannels.netinclude:relay.mailchannels.net, so it was just a thought I got.

It wouldn't make any sense to apply that to the "fromfrom" (e.g. header From:From:), but only the "

mailfrom

mailfrom

" (SMTP MAIL FROM) part, assuming that it exists, as that would be the one the SPF checks would be checked against.

addison•2/23/24, 5:24 AM

seems like mail from still doesn't exist unfortunately

DarkDeviLOP•2/23/24, 5:30 AM

Can you try to shoot one or more messages my way, where you play around with

mailfrom

mailfrom

DarkDeviLOP•2/23/24, 5:30 AM

cloudflare-discord-476641014841475084-addison@darkdevil.dkcloudflare-discord-476641014841475084-addison@darkdevil.dk

DarkDeviLOP•2/23/24, 5:31 AM

Alternatively, if you want a numbered tagging or so, if you take personal notes, you can do like:

DarkDeviLOP•2/23/24, 5:31 AM

cloudflare-discord-476641014841475084-addison-1@darkdevil.dkcloudflare-discord-476641014841475084-addison-1@darkdevil.dk
cloudflare-discord-476641014841475084-addison-2@darkdevil.dkcloudflare-discord-476641014841475084-addison-2@darkdevil.dk
[...]

addison•2/23/24, 5:32 AM

sent one over

DarkDeviLOP•2/23/24, 5:34 AM

Exact same testing@testing@ SMTP FROM (envelope from, Return-Path, ...) as header From:.

addison•2/23/24, 5:35 AM

this is what im sending over

DarkDeviLOP•2/23/24, 5:37 AM

It would be all guessing though, ... I wonder if they might have a documentation issue.

DarkDeviLOP•2/23/24, 5:38 AM

I mean, it goes with multiple distinct names such as SMTP FROM (envelope from, Return-Path, ...) ?

DarkDeviLOP•2/23/24, 5:38 AM

Can you try replacing mailfrom:mailfrom: with mfrom:mfrom:, and see if that makes any difference?

addison•2/23/24, 5:39 AM

sent

addison•2/23/24, 5:39 AM

their docs specify mailfrom:mailfrom: but i cant find any examples that use it

DarkDeviLOP•2/23/24, 5:40 AM

Exact same testing@testing@ on both of them again.

DarkDeviLOP•2/23/24, 5:40 AM

And yeah, it's very limited (to none) that you find with the mailfrom:mailfrom:, I just happened to find it at some point, which is why I suggested it to you earlier this month, as according to the documentation, that's the one we're after.

addison•2/23/24, 5:41 AM

yeah you are where i got the idea from in the first place

addison•2/23/24, 5:41 AM

definitely feels like a documentation issue though

DarkDeviLOP•2/23/24, 5:42 AM

envfrom:envfrom: could be tried as well though.

addison•2/23/24, 5:43 AM

i sent another with envfrom

DarkDeviLOP•2/23/24, 5:43 AM

But yeah, either technical (as in incorrectly not doing at all), or documentation issue (such as documenting the wrong thing) would be what I suspect too.

DarkDeviLOP•2/23/24, 5:44 AM

Third time wasn't the lucky time here, as it's still just testing@testing@.

addison•2/23/24, 5:44 AM

is there some sort of contact for this? i've tried contacting mailchannels support before with no luck

DarkDeviLOP•2/23/24, 5:54 AM

If you have already tried MailChannels Support (cc @skoogeer @fiirhok), with no luck, I don't think so.

However, you could try assuming that the email (or whatever) was lost in transmission, and try again.

skoogeer•2/23/24, 5:56 AM

Please feel free to submit a support ticket to us via our web site and someone can search our logs to track down your delivery/

DDarkDeviL If you have already tried MailChannels Support (cc @skoogeer @fiirhok), with no ...

addison•2/23/24, 6:11 AM

I'll give it a try again, last time I did I had some weird account issues with the support thing they use

Aaddison I'll give it a try again, last time I did I had some weird account issues with t...

DarkDeviLOP•2/23/24, 6:16 AM

You're more than welcome to ping me, and let me know what you're (eventually) finding out with them.

Sskoogeer Please feel free to submit a support ticket to us via our web site and someone c...

addison•2/23/24, 7:00 AM

I've done so now, have a good night chat

charl.dev•2/23/24, 10:30 AM

Hi guys at 8:46 we had an issue where a lot of api calls proxied via a worker was giving 526 errors. When we updated the worker triggers to be more explicit, it started working

charl.dev•2/23/24, 10:31 AM

Has anything changed and would workers ever return a 526

charl.dev•2/23/24, 10:36 AM

We confirmed it was a wild card at the beginning

charl.dev•2/23/24, 10:37 AM

Has anything with the way the triggers work changed?

charl.dev•2/23/24, 10:49 AM

Ticket 3158394

charl.dev•2/23/24, 10:59 AM

Just want to know if something with triggers and prefixed with wildcard would be effected

Liam•2/23/24, 2:59 PM

Hey guys! Quick question:

I'm using a cloudflare reverse proxy for load balancing on API calls. Is there anything I need to explicitly do to make the load balancing work if I'm using the default template?

BBulbasaur https://blog.cloudflare.com/updated-tos Actually, now I'm confused again with th...

Santosh•2/23/24, 4:14 PM

Can Cloudflare comment on this thread? TOS and all are good, clarifications would do wonders as well.

BBulbasaur https://blog.cloudflare.com/updated-tos Actually, now I'm confused again with th...

Hello, I’m Allie!•2/23/24, 4:17 PM

Assets must be stored on the Developer Platform(R2, Images, R2). Proxying a video through a Worker does not count, and thus would still be against the ToS

Santosh•2/23/24, 4:17 PM

Proxying a video srtored on R2, what would that fall under?

Hello, I’m Allie!•2/23/24, 4:17 PM

Though note, I am not a lawyer, nor am I Cloudflare Support, so for 100% certainty, I would recommend filing a ticket

SSantosh Proxying a video srtored on R2, what would that fall under?

Hello, I’m Allie!•2/23/24, 4:17 PM

Fine by ToS

HHello, I’m Allie!Assets must be stored on the Developer Platform(R2, Images, R2). Proxying a vide...

Bulbasaur•2/23/24, 5:08 PM

The conflict is that they explicitly say in the previous blog post that a user serving video through workers was not against tos. So either something changed between those two blog posts, or there’s a mistake

BBulbasaur The conflict is that they explicitly say in the previous blog post that a user s...

Hello, I’m Allie!•2/23/24, 6:10 PM

I would recommend contacting support with your use case, for the most up to date advice