Failed to send to Discord notification: Bad Request about mailrise HOT 3 CLOSED

It looks like something to do with Apprise, because the Bad Request log message is coming from that library. All Mailrise really does is forward the title, message text, and YAML configuration to Apprise.

A sample email and the configuration section for Discord might be helpful here.

from mailrise.

I have the same issue, emails coming from proxmox backups to discord are failing. I already sent a test email of just text so it does work.

[2023-07-02 15:54:33] WARNING:apprise:Failed to send to Discord notification: Bad Request - Unsupported Parameters., error=400.
[2023-07-02 15:54:33] WARNING:mailrise.skeleton:Notification failed: vzdump backup status (pve-general-rig.localdomain) : backup successful ➤ [email protected]

I tried text and html and markdown

configs:
 pve_general_rig_discord:
  mailrise:
   body_format: html
  urls:
   - https://discord.com/api/webhooks/........./............

version: "2.1"
services:
  mailrise:
    image: yoryan/mailrise:latest
    container_name: mailrise
    restart: unless-stopped
    ports:
      - 8025:8025
    volumes:
    - ./mailrise.conf:/etc/mailrise.conf:ro

I don't have a handy way to get the email, but it should look like the following:
https://www.servethehome.com/wp-content/uploads/2022/12/Proxmox-VE-Backup-Successful-e-mail.jpg

or the other kinds like shown in the blog (the dark mode photos): https://www.servethehome.com/proxmox-ve-e-mail-notifications-are-important/

from mailrise.

These emails contain entire logs. So I think what's happening here is that Discord is rejecting them for exceeding the maximum length. It's like copy-pasting a log file into the Discord app; you're going to get rejected.

You can cut split your messages into multiple notifications using Apprise's overflow options, but beware that they can be defeated by a long subject line, which isn't currently included in the split calculation (caronc/apprise#845).

For future reference, you should be able to retrieve the message by turning on debug logging (-vvv):

version: "2.1"
services:
  mailrise:
    image: yoryan/mailrise:latest
    container_name: mailrise
    restart: unless-stopped
    ports:
      - 8025:8025
    volumes:
      - ./mailrise.conf:/etc/mailrise.conf:ro
    command: -vvv /etc/mailrise.conf

from mailrise.