FAQ
Hello all

I made a new list and it seems to work OK, except that all the
confirmation strings are invalid.

Even if I answer at once, it says it's bad confirmation string and only
suggests it has been expired. I have also checked that the time is all
right on both ends. Any hints?

I also added another virtual host to mailman, and this list uses it,
could this cause this somehow?

Best regards

Hannu

Search Discussions

  • Mark Sapiro at Jan 25, 2006 at 3:37 pm

    Niemi Hannu wrote:
    I made a new list and it seems to work OK, except that all the
    confirmation strings are invalid.

    Even if I answer at once, it says it's bad confirmation string and only
    suggests it has been expired. I have also checked that the time is all
    right on both ends. Any hints?

    Have you overridden PENDING_REQUEST_LIFE in mm_cfg.py?

    How are you confirming? Web or email? Does it fail both ways? What do
    the actual confirm strings look like?
    I also added another virtual host to mailman, and this list uses it,
    could this cause this somehow?
    Is it only this list that fails? It is not likely a virtual host
    problem as host really isn't involved in processing confirmations.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Niemi Hannu at Jan 26, 2006 at 6:22 am

    -----Alkuper?inen viesti-----
    L?hett?j?: Mark Sapiro [mailto:msapiro at value.net]
    L?hetetty: 25. tammikuuta 2006 17:37
    Vastaanottaja: Niemi Hannu; mailman-users at python.org
    Aihe: Re: [Mailman-Users] Confirmation problems
    Have you overridden PENDING_REQUEST_LIFE in mm_cfg.py?
    Not that I know... and I checked, no such a line. The default in Defaults.py seems to be days(3) as it should....
    How are you confirming? Web or email? Does it fail both ways?
    What do the actual confirm strings look like?
    Yes, it fails all ways, I have tried replying, sending the confirm string and by the web form. Always the same.

    Confirm string looks like this:
    confirm 0e36dd2b0c2825e99b3a9fe234790f8fba059f6f
    I also added another virtual host to mailman, and this list uses it,
    could this cause this somehow?
    Is it only this list that fails? It is not likely a virtual
    host problem as host really isn't involved in processing
    confirmations.
    I had to test the others. To be honest I haven't earlier used this kind of "user-driven subscription" in any of the lists on that server, but have been adding the users on the web form instead.

    And the result is that (what was exactly what I was afraid of ;)) that at least the one I tested worked...

    What gives???

    Best regards

    hannu
  • Mark Sapiro at Jan 27, 2006 at 9:30 pm

    Niemi Hannu wrote:
    Is it only this list that fails? It is not likely a virtual
    host problem as host really isn't involved in processing
    confirmations.
    I had to test the others. To be honest I haven't earlier used this kind of
    "user-driven subscription" in any of the lists on that server, but have been adding the users on the web form instead.

    And the result is that (what was exactly what I was afraid of ;)) that at least the one I tested worked...

    What gives???

    Check mailman's 'error' log and also permissions on the list's
    pending.pck file.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedJan 25, '06 at 8:13a
activeJan 27, '06 at 9:30p
posts4
users2
websitelist.org

2 users in discussion

Niemi Hannu: 2 posts Mark Sapiro: 2 posts

People

Translate

site design / logo © 2022 Grokbase