-
Notifications
You must be signed in to change notification settings - Fork 40
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.
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
when attempting to configure proxmox to use mailrise I get a wierd error #123
Comments
Try it with a valid email address in the 'From Address' field. That works for me. |
I assume that proxmox sets
|
I encountered a similar problem when sending from proxmox. There was an error in the logs:
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 configs:
"[email protected]":
urls:
- tgram://.... |
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.
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: configs:
"*@proxmox.domain.com":
urls:
- tgram://....
mailrise:
body_format: text |
Is there any way to configure proxmox not to format these as HTML to begin with? |
thanks for looking at this.
[email protected] works via powershell test: Send-MailMessage -from simon@local -to "[email protected]" -subject "test" -body "test" -smtpserver 10.150.30.240 -port 8025
[2024-06-25 12:11:27] WARNING:apprise:Failed to send Telegram notification to 5526294333: Bad Request: can't parse entities: Unsupported start tag "[email protected]" at byte offset 34, error=400.
[2024-06-25 12:11:27] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE [email protected] ➤ [email protected] ] 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 "[email protected]" at byte offset 34, error=400.
[2024-06-25 12:12:20] WARNING:mailrise.skeleton:Notification failed: address: [ Proxmox VE [email protected] ➤ [email protected] ] 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 ➤ [email protected] ] 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 ➤ [email protected] ] subject: [ Test notification ] body: [ This is a test of th (0.1K) ]
The text was updated successfully, but these errors were encountered: