am 08 12 2007 20:27 schrieb Dada Mail (Justin Simoni):

On Dec 8, 2007, at 3:31 AM, Peter Velan wrote:

am 08 12 2007 10:03 schrieb Peter Velan:

a subscription (using standard confirmed opt-in) leaves the following traces in dada_usage_text:

(cited to prevent line breaks) [Fri Dec 7 21:14:56 2007] listname ip-quad Subscribed to
listname sub_confirm_list x@example com [Fri Dec 7 21:24:30 2007] listname ip-quad Unsubscribed from
listname - sub_confirm_list x@example com [Fri Dec 7 21:24:30 2007] listname ip-quad Subscribed to
listname list x@example com

I think, the second line is wrong: An unsubscription process isn't active here

Looks like you're using the new 2 11 Alpha 8?

No, I'm using 2 10 16

If so, that's the
correct behavior -

When someone requests a subscription confirmation, they're put on the
"Subscription Confirmation List" - this is where the subscription
information is saved until the subscription can be confirmed Once
they're subscribed, they're unsubscribed from the, "sub_confirm_list"
and added to the, "list" mailing list

Aaah, now its makes sense But nevertheless, this information seems to me like an logging overkill: Removing an adress from "sub_confirm_list" is a "natural" consequence if the address was added to "list"

If you're using the SQL backend, this move is done just by changing
the value in the, "list_type" column You're using the PlainText
backend, so the move is sort of emulated

I'm using SQL and wondered why column list_type does not simply changes from "sub_confirm_list" to "list" after confirmation After your above clarification, I understand the underlying process

Thanks for clarification, Peter