Hi Rob, It might be caused by GC itself, they have problems with notifications. codesite-noreply at googlecode.com email (or something like that) can't be used, now notifications must come from jallib at googlecode.com. But this is not something we can change by ourselves, right now (they plan to make it possible). I asked them to do so, that is to set email coming from jallib at ... as they say, since then it doesn't seem to work. I did not create a member, expecting to have a group management email, but nothing came. I'll create this user, and we'll see...
Cheers, Seb > > Hi Seb, > > Sebastien Lelong wrote: > > > Due to bugs in SVN & issue tracker notifications, sent to groups and > > reported as spam (see > > http://code.google.com/p/support/issues/detail?id=3135), notifications > > are now sent from [email protected] <mailto:[email protected]> > > and [email protected] <mailto:[email protected]> > > > > For jallib, it should give less false positive spam (less to manage, > > only done by admin). For jaluino, it should actually notify commits & > > new issues (real lack as of now). > > I didn't receive any notifications (yet) after my commits of yesterday > night. Could that be caused by your change? > > > Regards, Rob. > > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
