Re: Emails not going out?
I'm still seeing this issue with direct messages and new follows (appears to have been happening since sometime in yesterday). DMs and followers come into twitter, but I don't get any emails (and therefore can't process the DMs and follows, of course). Twitter username is addnetflix Thanks, Greg On Feb 11, 2:49 pm, pnoeric e...@ericmueller.org wrote: Thanks Matt ( Alex, ops folks!), I'll keep an eye on it. E On Feb 11, 10:55 am, Matt Sanford m...@twitter.com wrote: Hi Eric (and others with the problem), Alex and I talked to our operations folks and they found some outbound mail problems. The issue should now be fixed. Let me know if you don't get future emails. Thanks; — Matt Sanford On Feb 11, 2009, at 09:36 AM, pnoeric wrote: Thanks Doug Matt. Doug - yeah, we haven't touched settings, and we definitely would get emails aplenty when new followers came in. Matt - thank you... it's my work account, @FLWbooks. Looking forward to hearing what you see. best E On Feb 11, 9:33 am, Matt Sanford m...@twitter.com wrote: Hi Eric, I don't know of any issue but if you include the account name I could certainly check. In the future things like this that are not API related are better handled at help.twitter.com. Thanks; — Matt Sanford / @mzsanford On Feb 11, 2009, at 09:31 AM, dougw wrote: Eric, Just getting the obvious out of the way... have you checked your settings, are they still specifying that you want emails for DMs and new followers? @dougw On Feb 11, 11:57 am, pnoeric e...@ericmueller.org wrote: Hi-- we're noticing that though our follower count is going up, the emails to us saying X is now following you are not coming in. We're also not receiving emails when we get a direct message, and we suspect that when we follow someone, they're not getting an email telling them as much. Though this doesn't have to do directly with the API, it's definitely part of the whole circuit, and our code relies on those emails to know who our new followers are So just wondering, any info about what's going on with email notifications? Is it just us or a Twitter issue? I don't see anything on the status blog. thanks Eric
Re: Emails not going out?
Yep - just got one from the other day. Thanks!! On Feb 11, 5:25 pm, Alex Payne a...@twitter.com wrote: We had an issue with our mail server. Should be catching up, though. On Wed, Feb 11, 2009 at 14:20, El Greg greglaval...@gmail.com wrote: I'm still seeing this issue with direct messages and new follows (appears to have been happening since sometime in yesterday). DMs and followers come into twitter, but I don't get any emails (and therefore can't process the DMs and follows, of course). Twitter username is addnetflix Thanks, Greg On Feb 11, 2:49 pm, pnoeric e...@ericmueller.org wrote: Thanks Matt ( Alex, ops folks!), I'll keep an eye on it. E On Feb 11, 10:55 am, Matt Sanford m...@twitter.com wrote: Hi Eric (and others with the problem), Alex and I talked to our operations folks and they found some outbound mail problems. The issue should now be fixed. Let me know if you don't get future emails. Thanks; — Matt Sanford On Feb 11, 2009, at 09:36 AM, pnoeric wrote: Thanks Doug Matt. Doug - yeah, we haven't touched settings, and we definitely would get emails aplenty when new followers came in. Matt - thank you... it's my work account, @FLWbooks. Looking forward to hearing what you see. best E On Feb 11, 9:33 am, Matt Sanford m...@twitter.com wrote: Hi Eric, I don't know of any issue but if you include the account name I could certainly check. In the future things like this that are not API related are better handled at help.twitter.com. Thanks; — Matt Sanford / @mzsanford On Feb 11, 2009, at 09:31 AM, dougw wrote: Eric, Just getting the obvious out of the way... have you checked your settings, are they still specifying that you want emails for DMs and new followers? @dougw On Feb 11, 11:57 am, pnoeric e...@ericmueller.org wrote: Hi-- we're noticing that though our follower count is going up, the emails to us saying X is now following you are not coming in. We're also not receiving emails when we get a direct message, and we suspect that when we follow someone, they're not getting an email telling them as much. Though this doesn't have to do directly with the API, it's definitely part of the whole circuit, and our code relies on those emails to know who our new followers are So just wondering, any info about what's going on with email notifications? Is it just us or a Twitter issue? I don't see anything on the status blog. thanks Eric -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] 413 Request Entity Too Large for Direct Message
Hi there - I'm trying to get set up with the new OAuth API for a little app that I'm hosting on site5. When make a signed POST request from the app on my home machine, it works just fine. When I have the application do it on my host, the response to my curl request is a 413 Requet Entity Too large and looks like this (hope it comes out): !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title413 Request Entity Too Large/title /headbody h1Request Entity Too Large/h1 The requested resourcebr //direct_messages/new.jsonbr / does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. pAdditionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request./p /body/html I'm not sure if I want to post the entire signed request and its parameters for security reasons. I can't understand why it would work locally and not up on the server... Is it possible that my web host is attaching some junk to the request that twitter is rejecting?
[twitter-dev] Re: 413 Request Entity Too Large for Direct Message
Bump - any idea on this? I'm trying to switch my app to OAuth before the big switch at the end of June. Thanks, Greg On Jun 13, 10:32 pm, El Greg greglaval...@gmail.com wrote: Hi there - I'm trying to get set up with the new OAuth API for a little app that I'm hosting on site5. When make a signed POST request from the app on my home machine, it works just fine. When I have the application do it on my host, the response to my curl request is a 413 Requet Entity Too large and looks like this (hope it comes out): !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title413 Request Entity Too Large/title /headbody h1Request Entity Too Large/h1 The requested resourcebr //direct_messages/new.jsonbr / does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. pAdditionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request./p /body/html I'm not sure if I want to post the entire signed request and its parameters for security reasons. I can't understand why it would work locally and not up on the server... Is it possible that my web host is attaching some junk to the request that twitter is rejecting?
[twitter-dev] Re: 413 Request Entity Too Large for Direct Message
Thanks, Taylor. Turns out I was being a bit of an idiot and not including the POST parameters correctly in my curl request. Apparently the error when you POST to a signed URL without any POST data is this 413 business. Thanks again for the reply, Greg On Jun 16, 4:49 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Greg, Do you have any kind of HTTP proxy active in your other location? It's definitely possible that they are messing with HTTP headers or proxying the request in some way. Though unrelated, you'll want to make sure that the time on your server is within a reasonable amount of drift from our server time (which is included in a HTTP header of every request). Is just this particular POST request failing in your site5 server, or all POST requests? Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Wed, Jun 16, 2010 at 1:08 PM, El Greg greglaval...@gmail.com wrote: Bump - any idea on this? I'm trying to switch my app to OAuth before the big switch at the end of June. Thanks, Greg On Jun 13, 10:32 pm, El Greg greglaval...@gmail.com wrote: Hi there - I'm trying to get set up with the new OAuth API for a little app that I'm hosting on site5. When make a signed POST request from the app on my home machine, it works just fine. When I have the application do it on my host, the response to my curl request is a 413 Requet Entity Too large and looks like this (hope it comes out): !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title413 Request Entity Too Large/title /headbody h1Request Entity Too Large/h1 The requested resourcebr //direct_messages/new.jsonbr / does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. pAdditionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request./p /body/html I'm not sure if I want to post the entire signed request and its parameters for security reasons. I can't understand why it would work locally and not up on the server... Is it possible that my web host is attaching some junk to the request that twitter is rejecting?
