Variables in welcome message are not replaced
Hi all I set up a mailman mailinglist (everything preinstalled on a plesk-based hosting) and have a strange effect.
When I subscribe a user from my address by using the email-command with the optional "address=<user-address>", the user receives the confirmation-message without problems. BUT if the user replies to the message (to confirm), he gets a welcome-message with the variable-codes instead of the real values.
When the user himself does the same procedure (obviously without the address= option, that is not needed in this case), the welcome-message looks just fine.
I tried the same with the mailman-users-list itself and it worked, so I think this is not a bug - at least not in the actual version. I am using version 2.1.5.
Can anybody help me with this one? Regards Stefan
Hi again
I posted the following about two weeks ago. Can anybody help me with this one?
Thanks Stefan
Hi all
I set up a mailman mailinglist (everything preinstalled on a plesk-based hosting) and have a strange effect.
When I subscribe a user from my address by using the email-command with the optional "address=<user-address>", the user receives the confirmation-message without problems. BUT if the user replies to the message (to confirm), he gets a welcome-message with the variable-codes instead of the real values.
When the user himself does the same procedure (obviously without the address= option, that is not needed in this case), the welcome-message looks just fine.
I tried the same with the mailman-users-list itself and it worked, so I think this is not a bug - at least not in the actual version. I am using version 2.1.5.
Can anybody help me with this one? Regards Stefan
On 1/7/08, Stefan Burkard wrote:
I posted the following about two weeks ago. Can anybody help me with this one?
Two things:
- You're using Plesk. You need to talk to your provider about anything that might potentially be caused by Plesk or the customized version of Mailman that they have installed. The kinds of problems you're describing seem very likely to me to be a result of something that Plesk or your site administrator has done, and only your provider would be able to fix those problems.
See also FAQ 6.15 at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.015.htp.
- You're using Mailman 2.1.5, and the current version of Mailman is 2.1.9 (which is what we're running on python.org), with 2.1.10 in early beta and set to be released soon. So, part of your problem could potentially be resolved by upgrading the version of Mailman you're running, but then this gets back to point #1 above.
-- Brad Knowles brad@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu
Hi All--
Brad Knowles wrote:
On 1/7/08, Stefan Burkard wrote:
I posted the following about two weeks ago. Can anybody help me with this one?
Two things:
- You're using Plesk. You need to talk to your provider about anything that might potentially be caused by Plesk or the customized version of Mailman that they have installed. The kinds of problems you're describing seem very likely to me to be a result of something that Plesk or your site administrator has done, and only your provider would be able to fix those problems.
Plesk doesn't enter into this one. I'm using Plesk to create my lists, and this doesn't happen to me or my subscribers.
The only thing bizarre that's happened since my forced upgrade from 2.1.8 to 2.1.9 has been that I sometimes get disable notifications for one list from the bounce address at another list.
See also FAQ 6.15 at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.015.htp.
- You're using Mailman 2.1.5, and the current version of Mailman is 2.1.9 (which is what we're running on python.org), with 2.1.10 in early beta and set to be released soon. So, part of your problem could potentially be resolved by upgrading the version of Mailman you're running, but then this gets back to point #1 above.
Metta, Ivan
Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh... Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours
On 1/6/08, Ivan Van Laningham wrote:
Plesk doesn't enter into this one. I'm using Plesk to create my lists, and this doesn't happen to me or my subscribers.
Plesk doesn't enter into this issue directly, but the fact that he's using Plesk means that he probably can't make any of the necessary changes himself, or at the very least he's going to have to do a lot more work to properly integrate that with Plesk -- I've worked on sites where they upgraded Mailman while keeping Plesk, and I can tell you that it was one of the worst nightmares I've ever seen.
-- Brad Knowles brad@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu
Stefan Burkard wrote:
When I subscribe a user from my address by using the email-command with the optional "address=<user-address>", the user receives the confirmation-message without problems. BUT if the user replies to the message (to confirm), he gets a welcome-message with the variable-codes instead of the real values.
When the user himself does the same procedure (obviously without the address= option, that is not needed in this case), the welcome-message looks just fine.
I have looked at the way the welcome message is generated, at least in our 2.1.5 distribution, and I don't see any way in which the generation of the welcome message from the template is different depending on whether the subscribed address comes from address= or From:. In fact, the difference between these two modes is only very early in the subscribe process before the confirmation is even sent to the user. Once the confirmation is received, there is no difference in how it is processed and the welcome message sent.
If you are sure that the address= is the only thing that is different, this can't be explained by anything in our code as far as I can see.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Brad Knowles -
Ivan Van Laningham -
Mark Sapiro -
Stefan Burkard