On Sat, Apr 16, 2011 at 3:56 AM, Dr. David Kirkby
wrote:
> On 04/15/11 09:43 PM, Justin C. Walker wrote:
>>
>> On 15 Apr, 2011, at 13:21 PM, David Kirkby wrote:
>>
>>> On 15 April 2011 17:51, Volker Braun wrote:
I would think that it is sufficient to only allow non-anonymous email
On 04/15/11 09:43 PM, Justin C. Walker wrote:
On 15 Apr, 2011, at 13:21 PM, David Kirkby wrote:
On 15 April 2011 17:51, Volker Braun wrote:
I would think that it is sufficient to only allow non-anonymous email
accounts. For example:
* an institutional address: .edu, .ac.uk, ...
* a sourc
On Friday 15 April 2011, Justin C. Walker wrote:
> +1. I think posting to sage-devel/support would have to be a pre-requisite
> (why get a trac account otherwise?), RobertB's example notwithstanding.
> In the latter case, there may be an alternate approach, but for requests
> out of the blue, I c
Hi David,
On Fri, Apr 15, 2011 at 10:04 PM, Dr. David Kirkby
wrote:
> What checks do you suggest the trac account managers do? That is quite a
> critical point, as otherwise it would be very easy to spam if no checks were
> made.
It would be even easier to spam using some automated registration
On 15 Apr, 2011, at 13:48 PM, Volker Braun wrote:
> On Friday, April 15, 2011 9:43:21 PM UTC+1, Justin C. Walker wrote:
> You can't rely on mail with this in the header:
>From: j...@wolfram.com
> You have to check the detailed headers to be (somewhat) sure that the 'From'
> address is valid.
On Friday, April 15, 2011 9:43:21 PM UTC+1, Justin C. Walker wrote:
>
> You can't rely on mail with this in the header:
>From: j...@wolfram.com
> You have to check the detailed headers to be (somewhat) sure that the
> 'From' address is valid. Most spammers either cobble together 'From' (as
>
On 15 Apr, 2011, at 13:21 PM, David Kirkby wrote:
> On 15 April 2011 17:51, Volker Braun wrote:
>> I would think that it is sufficient to only allow non-anonymous email
>> accounts. For example:
>> * an institutional address: .edu, .ac.uk, ...
>> * a sourceforge-address associated to an active
On 15 April 2011 17:51, Volker Braun wrote:
> I would think that it is sufficient to only allow non-anonymous email
> accounts. For example:
> * an institutional address: .edu, .ac.uk, ...
> * a sourceforge-address associated to an active project
> * an address that has been used to post to goo
I would think that it is sufficient to only allow non-anonymous email
accounts. For example:
* an institutional address: .edu, .ac.uk, ...
* a sourceforge-address associated to an active project
* an address that has been used to post to google groups before (use
search)
People that want to
>
>
> It would seem wise to me that the email is initially at least the same one
> as they have used to post to sage-devel or sage-support. If they have never
> posted there, I don't feel they need a trac account.
>
I disagree. I've had examples of colleagues who use sage (but never posted)
and h
On 04/15/11 11:39 AM, Minh Nguyen wrote:
Hi folks,
Following a recent discussion on sage-devel [1], I've created a new
Google Group called "sage-trac-account" at
Hi Henrietta,
Welcome to the Sage community. Before your trac account could be
setup, the account managers need the following inf
11 matches
Mail list logo
