[Nagiosplug-devel] Re: Changes to tracker status

[Subhendu Ghosh]

I added noreplyATsourceforge as an acceptable alias for nagiosplug-devel 
list.  So we should start to see the tracker changes flowing directly to 
the list.

Will let you know if this isn't so...

-sg


On Thu, 20 Feb 2003, Karl DeBisschop wrote:

> Jeremy T. Bouse writes: 
> 
> > On Thu, Feb 20, 2003 at 01:05:43AM -0500, Karl DeBisschop wrote:
> >> On Thu, 2003-02-20 at 00:19, Jeremy T. Bouse wrote:
> >> > 	You'll get no complaints on this one from me... I actually
> >> > enabled this by default on my own project I've started on SF... As for
> >> > the posts to the mailing lists it could be because the list is setup for
> >> > submissions only from list members... It might allow spam to make it in
> >> > but opening it up would allow the tracker emails to come through... I
> >> > think you would have to do it through the Mailman interface itself
> >> > rather than through the SF list admin pages... 
> >> 
> >> If that's the case, maybe we could add the tracker originator as a
> >> member? 
> >> 
> > 	Provided the tracker messages all originate from the same
> > address that is a possible solution as well... I hadn't been paying
> > close enough attention to see if they all came from the same address or
> > not...
> 
> It poses as noreply at sourceforge.net -- it looks like it's actually 'nobody' 
> on the web server host. 
> 
> As far as I can tell so far, it's consistent. 
> 
>  --
> Karl
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
> The most comprehensive and flexible code editor you can use.
> Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
> www.slickedit.com/sourceforge
> _______________________________________________
> Nagiosplug-devel mailing list
> Nagiosplug-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 

--