How difficult would it be to add this as an option?
ACTION_EXPIRE_DATED is already there, so could it be done in a way that if ACTION_ANCIENT_DATED and the associated variable for the time threshold are not both currently set, then it simply ignores the routine and automatically falls back to the standard settings?
----- Original Message ----
From: Mark Horn <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, October 23, 2006 2:14:33 PM
Subject: Re: Extended Expiration?
From: Mark Horn <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, October 23, 2006 2:14:33 PM
Subject: Re: Extended Expiration?
On 2006-10-23, David Hoffman <[EMAIL PROTECTED]> wrote:
> I suppose it would be useful... provided that the ancient action is
> set to bounce. Otherwise, no matter how old the dated address is,
> it only adds to the bulk in your pending folder. At least this way
> mail that is still expired but not ancient has a chance of being
> confirmed, but mail that is ancient just gets bounced and doesn't
> bloat the pending folder.
I would assume that the default behavior would be that
ACTION_EXPIRED_DATED and ACTION_ANCIENT_DATED would be the same so
that the only people who got the new behavior would be the ones
who wanted it. There are other ways to clean up the pending dir
(PENDING_CLEANUP_ODDS).
What I assume is happening is that my ancient dated address is
getting culled from USENET along with another email address used
for joe-jobbing. The joe-jobbed address sees my confirmation
request and, not remembering who he/she sent email to, confirms it.
This results in me getting spammed and the joe-jobbed guy getting
annoyed. By creating the concept of an ancient dated address,
I can avoid both of these things.
But, of course, the default would be to not automatically engage
this behavior. If you wanted it, you'd have to set it up.
Jason, do you have an opinion?
Thanks.
- Mark
_________________________________________________
tmda-workers mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-workers
> I suppose it would be useful... provided that the ancient action is
> set to bounce. Otherwise, no matter how old the dated address is,
> it only adds to the bulk in your pending folder. At least this way
> mail that is still expired but not ancient has a chance of being
> confirmed, but mail that is ancient just gets bounced and doesn't
> bloat the pending folder.
I would assume that the default behavior would be that
ACTION_EXPIRED_DATED and ACTION_ANCIENT_DATED would be the same so
that the only people who got the new behavior would be the ones
who wanted it. There are other ways to clean up the pending dir
(PENDING_CLEANUP_ODDS).
What I assume is happening is that my ancient dated address is
getting culled from USENET along with another email address used
for joe-jobbing. The joe-jobbed address sees my confirmation
request and, not remembering who he/she sent email to, confirms it.
This results in me getting spammed and the joe-jobbed guy getting
annoyed. By creating the concept of an ancient dated address,
I can avoid both of these things.
But, of course, the default would be to not automatically engage
this behavior. If you wanted it, you'd have to set it up.
Jason, do you have an opinion?
Thanks.
- Mark
_________________________________________________
tmda-workers mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-workers
_________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
