Kapps
Errors when attempting to use Pushbullet notifications.
I noticed this today, though I haven't used the app in a few days, but whenever a Pushbullet notification would be sent I get: <Failed to send PushBullet notification: The remote server returned an error: (400) Bad Request.>
Additionally, when using SMTP I got this error: <Failed to send SMTP notification: An invalid character was found in the mail header: '@'.> though that may be due to my smtp provider.
My API key appears to be valid .
For Pushbullet, I believe the problem is that you received too many notifications. Unfortunately Pushbullet changed it so free accounts have a limit of 500 messages from third party Apis like the whisper notifier per month. If it worked before and suddenly stopped, this is probably the issue. You could use a different account (maybe?), wait until the month expires, or upgrade to a Pushbullet Pro account (which I remember being rather expensive).
For SMTP, try putting in your username without the @provider.com. It would be pretty specific to each provider what the settings are, and honestly that feature rather fell by the wayside once Pushbullet came in. It's only really been tested with Gmail (and you have to enable it in your account settings in Gmail too).
Thanks for the reply. Regarding the SMTP, my provider does specifically say the entire email address. I will try other alternatives. I was only using SMTP due to my Pushbullet problem. I wasn't aware of a limit as I've not hit IS before
Richard Jeffery
On Feb 21, 2017, at 12:07 PM, Ognjen Ivkovic [email protected] wrote:
For Pushbullet, I believe the problem is that you received too many notifications. Unfortunately Pushbullet changed it so free accounts have a limit of 500 messages from third party Apis like the whisper notifier per month. If it worked before and suddenly stopped, this is probably the issue. You could use a different account (maybe?), wait until the month expires, or upgrade to a Pushbullet Pro account (which I remember being rather expensive).
For SMTP, try putting in your username without the @provider.com. It would be pretty specific to each provider what the settings are, and honestly that feature rather fell by the wayside once Pushbullet came in. It's only really been tested with Gmail (and you have to enable it in your account settings in Gmail too).
― You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Thanks for the reply.
I was trying to use SMTP due to my Pushbullet problem and my provider specifically said to use the entire email address but I will try alternatives. I was not aware of a Pushbullet limit and I've used the notifier for a long time without an error. I will try another account.
I would think that SMTP to text message would be more reliable than Pushbullet but I've never given much thought to it since the tool was already made when I thought about how I could push whispers to my phone.
Richard Jeffery
On Feb 21, 2017, at 12:07 PM, Ognjen Ivkovic [email protected] wrote:
For Pushbullet, I believe the problem is that you received too many notifications. Unfortunately Pushbullet changed it so free accounts have a limit of 500 messages from third party Apis like the whisper notifier per month. If it worked before and suddenly stopped, this is probably the issue. You could use a different account (maybe?), wait until the month expires, or upgrade to a Pushbullet Pro account (which I remember being rather expensive).
For SMTP, try putting in your username without the @provider.com. It would be pretty specific to each provider what the settings are, and honestly that feature rather fell by the wayside once Pushbullet came in. It's only really been tested with Gmail (and you have to enable it in your account settings in Gmail too).
― You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
The new version I just put out has better SMTP support. You'll be able to enter your username in properly. Also there's proper error messages for Pushbullet now. If you're still looking to get this working, it should be better now.
If you do give it a try, let me know if it works. Testing was very limited.
Thanks!
On Fri, Mar 10, 2017 at 9:47 PM, Ognjen Ivkovic [email protected] wrote:
Closed #21 https://github.com/Kapps/PoEWhisperNotifier/issues/21.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kapps/PoEWhisperNotifier/issues/21#event-995850160, or mute the thread https://github.com/notifications/unsubscribe-auth/ACUTFsj8yRbdThb_juf67Qg1c39Wj4J5ks5rkhlRgaJpZM4MHd9f .
Ognjen
I just discovered another small problem with the SMTP, my guild tag is "THE•D" and I tested the smtp feature recently by whispering myself. While the SMTP worked, the message stopped just before the dot as if it's an end of message character.
-Rich
On Fri, Mar 10, 2017 at 10:00 PM, Rich Jeffery [email protected] wrote:
Thanks!
On Fri, Mar 10, 2017 at 9:47 PM, Ognjen Ivkovic [email protected] wrote:
Closed #21 https://github.com/Kapps/PoEWhisperNotifier/issues/21.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kapps/PoEWhisperNotifier/issues/21#event-995850160, or mute the thread https://github.com/notifications/unsubscribe-auth/ACUTFsj8yRbdThb_juf67Qg1c39Wj4J5ks5rkhlRgaJpZM4MHd9f .