Image 1 — Custom patch not working.. I don't know how to use it...
Image 2 — Custom patch not working.. I don't know how to use it...

Custom patch not working.. I don't know how to use it...

I haven't used lucky patcher in years and years and years... I don't know if I'm doing something wrong please help.

u/lucidparadigm — 7 days ago
▲ 2 r/kimi

Where is 2.6??

I subscribed a couple days ago and I'm using the cli there's only 2.7 code? I paid $40 and I can't find other models in the sub for coding. I was expecting to find 2.6 as well.

reddit.com
u/lucidparadigm — 2 months ago
▲ 5 r/aws

AWS SES production access rejected for low-volume transactional emails despite verified domain, DKIM, SPF, and DMARC

Hi everyone,

I’m looking for advice after an AWS SES production access rejection.

My use case is low-volume transactional email only, mainly password reset and account recovery emails for a small web app. I am not sending marketing emails, newsletters, bulk campaigns, cold outreach, or third-party email.

Before applying, I fully configured the sending domain and email authentication, including:

  • Verified domain identity in SES
  • DKIM
  • SPF
  • DMARC
  • Dedicated sender address
  • Proper domain-based sending setup

AWS asked for more details, so I explained that:

  • Emails are transactional and user-initiated only
  • Current use case is password reset / account recovery
  • Future use case may include account verification emails
  • Recipients are only users who register directly or request account recovery
  • No purchased, scraped, rented, imported, or third-party recipient lists
  • Password reset links expire after a short period
  • The forgot-password endpoint uses a generic response to avoid account enumeration
  • Failed email sends are logged and are not retried in bulk
  • Bounces and complaints would be monitored
  • Hard bounces or complaints would be suppressed from future sends

AWS still rejected the request and said they identified concerns, but could not provide specifics for security reasons.

For people who have successfully gotten SES production access approved:

  1. Is there anything else AWS expects beyond verified domain identity, DKIM, SPF, DMARC, and a clear transactional-only use case?
  2. Would it help to provide exact sample email content?
  3. Should I describe rate limiting, CAPTCHA, abuse prevention, and suppression handling in more detail?
  4. Are new AWS accounts, new domains, or low-traffic apps more likely to be rejected?
  5. Is there a better way to phrase a reapplication for a password-reset-only use case?

I would appreciate any advice from people who have gone through this successfully.

reddit.com
u/lucidparadigm — 3 months ago