email worker doing the opposite

export default {
  async email(message, env, ctx) {
    if (message.headers.get("from").includes("Mark Mateschitz")) {
      await message.forward("<me>");
    } else {
      message.setReject("Rejected. Sending to this inbox has been banned by your email");
    }
  }
}

export default {
  async email(message, env, ctx) {
    if (message.headers.get("from").includes("Mark Mateschitz")) {
      await message.forward("<me>");
    } else {
      message.setReject("Rejected. Sending to this inbox has been banned by your email");
    }
  }
}

export default {
  async email(message, env, ctx) {
    if (message.headers.get("from").includes("Mark Mateschitz")) {
      await message.forward("<me>");
    } else {
      message.setReject("Rejected. Sending to this inbox has been banned by your email");
    }
  }
}

export default {
  async email(message, env, ctx) {
    if (message.headers.get("from").includes("Mark Mateschitz")) {
      await message.forward("<me>");
    } else {
      message.setReject("Rejected. Sending to this inbox has been banned by your email");
    }
  }
}

Sent an email from my test account that doesn't include Mark Mateschitz in the from header but it still rejects.

johtso•6/25/24, 9:08 AM

That's exactly what your code does, rejects the message if it doesn't include that name in the header..

RhinosF1OP•6/25/24, 9:11 AM

yes it does

RhinosF1OP•6/25/24, 9:12 AM

i'm in a very warm room and tired and flipped the logic

RhinosF1OP•6/25/24, 9:15 AM

thank you @johtso, fixed because I'm an idiot

johtso•6/25/24, 9:17 AM

No worries

email worker doing the opposite

Similar Threads

Similar Threads

Similar Threads