LIST COMPROMISED? [was: default null-arg feature]

Joerg Arndt on Mon, 06 Aug 2007 13:59:01 +0200

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

LIST COMPROMISED? [was: default null-arg feature]

To: pari-dev@list.cr.yp.to
Subject: LIST COMPROMISED? [was: default null-arg feature]
From: Joerg Arndt <arndt@jjj.de>
Date: Mon, 6 Aug 2007 13:56:22 +0200
Delivery-date: Mon, 06 Aug 2007 13:59:01 +0200
In-reply-to: <20070806103642.GA8196@amd32.purzl.net>
Mailing-list: contact pari-dev-help@list.cr.yp.to; run by ezmlm
References: <20070806103642.GA8196@amd32.purzl.net>

This is the second time I receive mails (including the
full text of my email below) from various sources:

PayPal Customer Service 2 <service2@paypal.com>
PayPal Customer Service 1 <service@paypal.com>
Casa el Chusco <info@casaelchusco.com>
eBay Customer Support <Support@ebay.com>

We may have a harvester bot subscribed to the list.

The operator might want to send individual mails to every subscriber
(with different text for each mail) to determine what is going on.



* Joerg Arndt <arndt@jjj.de> [Aug 06. 2007 13:47]:
> The mechanism to have automatic default zero
> for all arguments has bitten me quite often.
> 
> Is there any reason to have it?
> if so, could we have an option (e.g. something in ~/.gprc)
> to disable it?
> 
> regards,   jj

References:
- default null-arg feature
  - From: Joerg Arndt <arndt@jjj.de>

Prev by Date: default null-arg feature
Next by Date: Re: default null-arg feature
Previous by thread: default null-arg feature
Next by thread: Re: default null-arg feature
Index(es):
- Date
- Thread