Self Hosted

SMTP flooding

Jul 21, 2026, 11:00Last activity 1 month ago

View on Discord

Votes

Replies

Participants

Messages

iStornZOriginal post

Rank 3: Container

Jul 21, 2026, 10:15

I upgraded a self-hosted server from 1.8.1 to 1.9.0 then 1.9.5 and now every day at 02:00 AM seems the instance flood Mailjet with a ton of trash email "demo@example.com" subject "Test SMTP Connection" why?
There is env 200 mail sent by day!
Seems to impact my quota of email too...

Tried to see mail logs: docker logs appwrite-worker-mails but the mails was not sent too...

worker.v1-mails · 311.2ms · 18711ebc

  level                 info
  project.id            x-prod
  mail.template         recovery
  mail.smtp_type        cloud
  mail.recipient_domain gmail.com
  mail.status           success

────────────────────────────────────────────────────────────
worker.v1-mails · 123.3ms · 29509daf

  level                 info
  project.id            x-prod
  mail.template         recovery
  mail.smtp_type        cloud
  mail.recipient_domain gmail.com
  mail.status           success

Summary

User is inquiring about SMTP flooding and also discussing generic OIDC login options. The conversation includes suggestions for accessing the admin dashboard and creating a feature request.

iStornZ

Rank 3: Container

Jul 21, 2026, 10:37

Seems related to doctor command but why it's running everyday???

https://github.com/appwrite/appwrite/blob/f44e3c2cfc6149db2ddfb7a53c6127a461d9368e/src/Appwrite/Platform/Tasks/Doctor.php#L221

Chirag Aggarwal

Jul 21, 2026, 10:52

in your docker compose change healthcheck for appwrite to this

healthcheck:
  test:
    - CMD-SHELL
    - 'curl -fsS -o /dev/null -H "Host: $${_APP_DOMAIN:-localhost}" http://localhost/v1/health/version'
  interval: 5s
  timeout: 5s
  retries: 12
  start_period: 120s

this has been fixed in latest compose file

iStornZ

Rank 3: Container

Jul 21, 2026, 11:06

Thanks, you mean this one:

appwrite:
    container_name: appwrite
    logging:
      driver: json-file
      options:
        max-file: "5"
        max-size: 10m
    image: ${_APP_IMAGE:-appwrite/appwrite}:${_APP_VERSION:-latest}
    healthcheck:
      test:
      - CMD
      - doctor
      interval: 5s
      timeout: 5s
      retries: 12
    networks:
    - appwrite

Need to be:

appwrite:
    container_name: appwrite
    logging:
      driver: json-file
      options:
        max-file: "5"
        max-size: 10m
    image: ${_APP_IMAGE:-appwrite/appwrite}:${_APP_VERSION:-latest}
    healthcheck:
      test:
        - CMD-SHELL
        - 'curl -fsS -o /dev/null -H "Host: $${_APP_DOMAIN:-localhost}" http://localhost/v1/health/version'
      interval: 5s
      timeout: 5s
      retries: 12
      start_period: 120s
networks:
    - appwrite

That's OK?

iStornZ

Rank 3: Container

Jul 21, 2026, 11:07

Seems also related to Appwrite doctor show incorrect status because it retry but the instance seems healthy...

Ibaraki Douji

Jul 21, 2026, 11:26

i think the issue is that the appwrite-api use the doctor as the healthcheck, you should change it to request the /v1/health/version endpoint instead

Ibaraki Douji

Jul 21, 2026, 11:27

https://discord.com/channels/564160730845151244/1466421286598344787

Ibaraki Douji