Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

when attempting to configure proxmox to use mailrise I get a wierd error #123

Open
simonmcnair opened this issue Jun 25, 2024 · 10 comments
Open

when attempting to configure proxmox to use mailrise I get a wierd error #123

simonmcnair opened this issue Jun 25, 2024 · 10 comments

Comments

@simonmcnair
Copy link

thanks for looking at this.

telegram@mailrise.xyz works via powershell test: Send-MailMessage -from simon@local -to "telegram@mailrise.xyz" -subject "test" -body "test" -smtpserver 10.150.30.240 -port 8025

image

[2024-06-25 12:11:27] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "simon@local.com" at byte offset 34, error=400.
[2024-06-25 12:11:27] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE simon@local.com ➤ telegram@mailrise.xyz ] subject: [ Test notification ] body: [ This is a test of th (0.1K) ]
[2024-06-25 12:12:20] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "telegram@mailrise.xyz" at byte offset 34, error=400.
[2024-06-25 12:12:20] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE telegram@mailrise.xyz ➤ telegram@mailrise.xyz ] subject: [ Test notification ] body: [ This is a test of th (0.1K) ]
[2024-06-25 12:15:36] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "simon" at byte offset 34, error=400.
[2024-06-25 12:15:36] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE ➤ telegram@mailrise.xyz ] subject: [ Test notification ] body: [ This is a test of th (0.1K) ]
[2024-06-25 12:17:54] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "simon" at byte offset 34, error=400.
[2024-06-25 12:17:54] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE ➤ telegram@mailrise.xyz ] subject: [ Test notification ] body: [ This is a test of th (0.1K) ]
@sachapan
Copy link

Try it with a valid email address in the 'From Address' field. That works for me.

@AlBundy33
Copy link

AlBundy33 commented Jul 29, 2024 •
edited
Loading

I assume that proxmox sets <simon@local.com> as sender.
do you get the same error with

Send-MailMessage -from "<simon@local.com>" -to "telegram@mailrise.xyz" -subject "test" -body "test" -smtpserver 10.150.30.240 -port 8025

@Deniom3
Copy link

Deniom3 commented Aug 25, 2024 •
edited
Loading

I encountered a similar problem when sending from proxmox. There was an error in the logs:

WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE <proxmox@domain.com> ➤ proxmox@domain.com ] subject: [ Test notification  ] body: [ This is a test of th (0.0K) ]

By chance I managed to find out what the problem was. Mailrise does not work correctly with the author field. The problem goes away if you put a space there. It seems to me that the problem is on the mailrise side, since alternative solutions handle this situation correctly.

P.S. Until the next edit of the submission

Example of working settings:
image

configs:
  "proxmox@domain.com":
    urls:
      - tgram://....

@Deniom3
Copy link

Deniom3 commented Aug 25, 2024 •
edited
Loading

Unfortunately, although the above setting worked for testing, it did not work in real notifications. The problem is still the same: the sender's nickname is transmitted, which breaks the entire logic of parsing recipients.

[2024-08-25 10:38:18] WARNING:apprise:Failed to send Telegram notification to <chatid>: Bad Request: can't parse entities: Unsupported start tag "proxmox@domain.com" at byte offset 73, error=400.
[2024-08-25 10:38:18] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox <proxmox@domain.com> ➤ proxmox@domain.com ] subject: [ vzdump backup status (proxmox.domain.com): backup successful  ] body: [ <html>
 (3.4K) ]

I managed to solve the problem only partially (html is not displayed correctly in telegram messages), but the notifications themselves finally arrive with these settings:

image

configs:
  "*@proxmox.domain.com":
    urls:
      - tgram://....
    mailrise:
      body_format: text

@luispabon
Copy link

Is there any way to configure proxmox not to format these as HTML to begin with?

@simonmcnair
Copy link
Author

this is still an issue. Any help pls ?

@simonmcnair
Copy link
Author 

[2025-03-03 11:40:03] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "telegram@mailrise.xyz" at byte offset 34, error=400.
[2025-03-03 11:40:03] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE <telegram@mailrise.xyz> ➤ telegram@mailrise.xyz ] subject: [ Test notification  ] body: [ This is a test of th (0.1K) ]

@luispabon
Copy link

this is still an issue. Any help pls ?

I have personally given up on this now that proxmox allows you to define a webhook in enough detail that you can make it work with telegram:

Image

@simonmcnair
Copy link
Author

It isn't ideal but this seems to fix it (replace telegram with your config name):

telegram:
mailrise:
body_format: text

IT is the html it doesn't seem to like perhaps ?

@simonmcnair
Copy link
Author

FYI this only seems to occur with the telegram plugin. The email one I configured worked first time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@AlBundy33 @luispabon @sachapan @Deniom3 @simonmcnair