Re: [Mailman-Users] Plus in email address

2010-09-03 Thread David Lubkin

Mark Sapiro wrote:


The subscription request won't appear in the admindb until it is
confirmed by the user, so everything is consistent within Mailman. The
problem is the user never received the confirmation request email or
didn't confirm. Check your MTA logs to see that the confirmation was
sent.


Bingo. Thanks. The problem has nothing to do with +. His server is
rejecting the email because it doesn't like how my DNS entries are
set up. It was coincidence that the first user with a + in his address
was also the first user from that finicky destination server.

Mail directly from me to him doesn't use the same source domain,
so it didn't hit the server's validation check.


-- David.

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Plus in email address

2010-09-03 Thread Mark Sapiro
David Lubkin wrote:

>Mark Sapiro wrote:
>
>>What Mailman version is this?
>
>2.1.13, running on CentOS. I'm fine with upgrading; I just haven't gotten
>around to it because this is the first hint of a problem.
>
>>By "request appears in the log" do you mean Mailman's vette log? If
>>not, what log and what's the message and what's in Mailman's vette
>>log? What's in Mailman's error log?
>
>In the subscribe log --
>
>timestamp (number) mylist: pending Joe Foo  123.45.67.89
>
>Nothing related to the request appears in the vette or error logs.


The fact that there is a pending entry in the subscribe log and nothing
in the vette log indicates that the lists subscribe_policy is "Confirm
and approve" ans the confirmation to the user was never answered.

Can the user actually receive mail sent to foo+...@goo.com?

The subscription request won't appear in the admindb until it is
confirmed by the user, so everything is consistent within Mailman. The
problem is the user never received the confirmation request email or
didn't confirm. Check your MTA logs to see that the confirmation was
sent.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Plus in email address

2010-09-03 Thread David Lubkin

Mark Sapiro wrote:


What Mailman version is this?


2.1.13, running on CentOS. I'm fine with upgrading; I just haven't gotten
around to it because this is the first hint of a problem.


By "request appears in the log" do you mean Mailman's vette log? If
not, what log and what's the message and what's in Mailman's vette
log? What's in Mailman's error log?


In the subscribe log --

timestamp (number) mylist: pending Joe Foo  123.45.67.89

Nothing related to the request appears in the vette or error logs.


Was the subscribe from the listinfo page or via email?


listinfo page.

He tried subscribing a few weeks later, with exactly the same results,
and then contacted me to see why I hadn't approved his request.


-- David.

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Plus in email address

2010-09-03 Thread Mark Sapiro
David Lubkin wrote:

>One of my users has tried to subscribe with an email address with
>a + in it, for filtering as a subaddress, e.g.,
>
>Joe Foo 
>
>I have the list set for moderator approval of subscription requests.
>The request appears in the log but no email is sent to me and the
>request does not appear in the moderator action queue.


What Mailman version is this?

By "request appears in the log" do you mean Mailman's vette log? If
not, what log and what's the message and what's in Mailman's vette
log? What's in Mailman's error log?

Was the subscribe from the listinfo page or via email?


>Apart from the problem itself, will it work if I manually add him to the
>list, or will other scripts in Mailman have a problem?


That depends on what the problem is. It works for me on my development
platform with subscribe via the listinfo page.
 
-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] Plus in email address

2010-09-03 Thread David Lubkin

One of my users has tried to subscribe with an email address with
a + in it, for filtering as a subaddress, e.g.,

Joe Foo 

I have the list set for moderator approval of subscription requests.
The request appears in the log but no email is sent to me and the
request does not appear in the moderator action queue.

I've looked through the wiki and my archives of this list, but I don't
see anything pertinent. It should be legit. There are no imposed
semantics on local-part in the RFCs, and in my experience mailman
developers are sticklers for standards compliance. So I'm confused.

The fact that it's + that's the problem is suspicious and makes me
think the issue relates to URL (en | de)coding.

Apart from the problem itself, will it work if I manually add him to the
list, or will other scripts in Mailman have a problem?


-- David.

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] mailto: vaild

2010-09-03 Thread Dave Foran
DISREGARD
Wrong group

THis caommand imbedded in a message does not work when clicking on to reply

Any thoughts

Dave


--
Dave Foran  Internet ONLY:  d...@hamnet.org
 Cruise Missile Coordinates 41.36.978N 81.25.867W




--
Dave Foran  Internet ONLY:  d...@hamnet.org
 Cruise Missile Coordinates 41.36.978N 81.25.867W

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Mark Sapiro
W. Curtis Preston wrote:
>
>All I can say is http://www.backupcentral.com/ha.mp3 
>
>It works!  Thank you so much for your help with this!
>
>The following URL will set an existing user's digest flag on and nothing
>else:
>http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&user%2540gmail.com_digest=1&setmemberopts_btn=1&adminpw=password
>
>The opposite (digest=0) doesn't turn it off.  I don't need it for me, but I
>am curious about your thoughts on that, as I plan to help update the FAQ
>with what we've learned here.


Actually, the way the code works (and it works that way because of the
way most browsers work) setting a key to any value, e.g.
user%2540gmail.com_digest=1 or even user%2540gmail.com_digest=0 will
set the corresponding option on. To set an option off for a user you
just include "user=user%2540gmail.com" and omit the
user%2540gmail.com_ setting entirely.

Note that this means that

http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&setmemberopts_btn=1&adminpw=password

will effectively uncheck all the checkboxes for the user. Those that
you want checked such as perhaps nodupes and plain need to be
explicitly mentioned as in


http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&user%2540gmail.com_nodupes=1&user%2540gmail.com_digest=1&user%2540gmail.com_plain=1&setmemberopts_btn=1&adminpw=password

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread W. Curtis Preston
All I can say is http://www.backupcentral.com/ha.mp3 

It works!  Thank you so much for your help with this!

The following URL will set an existing user's digest flag on and nothing
else:
http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&user%2540gmail.com_digest=1&setmemberopts_btn=1&adminpw=password

The opposite (digest=0) doesn't turn it off.  I don't need it for me, but I
am curious about your thoughts on that, as I plan to help update the FAQ
with what we've learned here.

The other tip you gave also works:
http:///mailman/admin/
>
>
> /members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=
> u...@example.com&user=user%2540example.com
> &user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw=


That does indeed subscribe them and set them to digest mode.  That will
simplify my code.

Did I mention this is what I'm hearing: http://www.backupcentral.com/ha.mp3??

Thanks, Mark.  Your internal knowledge of Mailman was really needed to
figure this out.  You could have just said "Dude, that's not really how
Mailman was meant to be used..."  but you didn't.  Thank you, thank you,
thank you.

>
>
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Mark Sapiro
Mark Sapiro wrote:
>
>Note also that you can subscribe the user and set options with a single
>GET URL. For example:
>
>http:///mailman/admin//members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=u...@example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw=
>


Note that the /add in the above is not required. It could just as well
be

http:///mailman/admin//members?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=u...@example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw=

The only difference is what the results page is.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] making the "Your name" Field required

2010-09-03 Thread Mark Sapiro
On 9/2/2010 12:00 PM, Doug Warren wrote:
>  
> I am new to mailman and just learning the basics. I am looking for away to 
> make 
> the "your name" field on the subscription page required for our private list. 
> I 
> have changed the (optional) to (required) on the screen but I have been 
> unable 
> to find out how to get the list to make it a mandatory field. I am hoping 
> someone will be able to give me some pointers on this.


This is tricky. Presumably you know how to edit the listinfo template to
change (optional) to (required). You will note that the actual text box
for entry of the real name is generated by the tag  in
the listinfo template. This tag expands to  in the generated HTML. It would be
nice if you could just replace the tag with its expansion and just add a
'REQUIRED' attribute, but I don't think HTML has such an attribute for
INPUT elements.

What this means is you would have to look also at the
 tag which expands to  and add some ONCLICK= javascript
to enforce an entry for fullname.

But, there are multiple problems with this. The first issue is that due
to XSS protection, you can't put things like ONCLICK in HTML templates
edited via the web admin interface. You would have to have access to the
Mailman server and create an edited template as discussed in the FAQ at
. Another way to do it would be to just
remove the subscribe form and replace it with a link to your own
subscribe page (see ).

Beyond that, even if you made a bomb proof page that would refuse to
allow subscription without a real name, it wouldn't prevent a user from
subscribing by email without a real name.

You could (if you have access) modify the Mailman code to require a real
name for subscription, but even this could be effectively bypassed by a
user providing a bogus name. Perhaps a better approach is to set your
list's Privacy options... -> Subscription rules -> subscribe_policy to
"Require approval" and just not approve any requests that don't provide
an acceptable real name.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Mark Sapiro
W. Curtis Preston wrote:
>
>So it seems I misunderstood your previous post.  Sorry about that. I
>followed your suggestion.  Both of them, actually.  I tried all of the
>following URLs, to no avail.  The first two do at least display just the
>username in question.  I did change the chunksize variable and did the
>latter two URLs, and that didn't work either. (In case it's not obvious, I
>tried using the values off/on and 0/1 in case that was the problem.)


I finally had some time to devote to debugging this, and I know what
the problem is. The 2.1.10 change was made because the local part of
an email address can be quoted with a double quote as in
"john&jane"@example.com. The presence of those double quotes would
break the HTML for the membership list page by creating things like

/mailman/admin//members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=u...@example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw=

Note the following:

I have specified subscribees instead of subscribees_upload as in the
OP. This doesn't matter; either will work, but subscribees is shorter.
Note the address here is raw, not encoded.

I have corrected send_notifications_to_list_owner which was
notification_to_list_owner in the OP.

I have omitted allmodbit_val=0 since this is ignored unless
allmodbit_btn is present.

I have setmemberopts_btn=1 since the actual value is ignored - only the
presence or absence of the key is significant.

I have omitted the '=0' option settings. In most cases (language is an
exception), ommitting a setting is the same as setting it to unchecked
or empty. This does mean that settings which are on by default must be
explicitly set whether you do it with one step or two or they will be
turned off. The exception is language which will be unchanged if
omitted.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] set the "your name" field to Required

2010-09-03 Thread Doug Warren
Hello
 
I am new to Mailman so please bear with me. I am trying to set the "Your name" 
field on the subscription page of our entire list to required, but I have been 
unable to find the commands to set this up. I have changed the "(optional)" to 
“(required)” on the subscription HTML page on a test list and that looks good, 
but they users can submit a subscription with out submitting  that information.
 Any help will be greatly appreciated.
 
Thank you
Doug 


  
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Mark Sapiro
Geoff Shang wrote:

>On Fri, 3 Sep 2010, Brad Knowles wrote:
>
>> I'm sure Mark will correct me if I'm wrong, but I assume you stopped and 
>> restarted Mailman after making the chunksize change?  I don't think that 
>> this is something that is baked into the list when it's created, but is 
>> instead something that can be changed after-the-fact, and all that 
>> should be required is a restart.
>
>I doubt this needs a restart, as member chunk size is something a list 
>owner can change on the admin pages.


Geoff is correct. admin_member_chunksize is a list attribute and simply
changing a list attribute never requires a restart. Further, in this
case, we are dealing with CGIs, and the CGI scripts are always loaded
as a new process by the web server, so changes that affect only the
CGI scripts don't require a restart either.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Geoff Shang

On Fri, 3 Sep 2010, Brad Knowles wrote:

I'm sure Mark will correct me if I'm wrong, but I assume you stopped and 
restarted Mailman after making the chunksize change?  I don't think that 
this is something that is baked into the list when it's created, but is 
instead something that can be changed after-the-fact, and all that 
should be required is a restart.


I doubt this needs a restart, as member chunk size is something a list 
owner can change on the admin pages.


Geoff.

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread Brad Knowles
On Sep 3, 2010, at 2:01 AM, W. Curtis Preston wrote:

> So it seems I misunderstood your previous post.  Sorry about that. I followed 
> your suggestion.  Both of them, actually.  I tried all of the following URLs, 
> to no avail.  The first two do at least display just the username in 
> question.  I did change the chunksize variable and did the latter two URLs, 
> and that didn't work either. (In case it's not obvious, I tried using the 
> values off/on and 0/1 in case that was the problem.)

I'm sure Mark will correct me if I'm wrong, but I assume you stopped and 
restarted Mailman after making the chunksize change?  I don't think that this 
is something that is baked into the list when it's created, but is instead 
something that can be changed after-the-fact, and all that should be required 
is a restart.

But there's something tickling in the back of my brain regarding this, and I 
can't figure out what it is

--
Brad Knowles 
LinkedIn Profile: 

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Cannot set digest mode via URL

2010-09-03 Thread W. Curtis Preston
So it seems I misunderstood your previous post.  Sorry about that. I
followed your suggestion.  Both of them, actually.  I tried all of the
following URLs, to no avail.  The first two do at least display just the
username in question.  I did change the chunksize variable and did the
latter two URLs, and that didn't work either. (In case it's not obvious, I
tried using the values off/on and 0/1 in case that was the problem.)

http://domain.com/mailman/admin/listname/members?findmember=username%40gmail.com&user=username%40gmail.com&username%40gmail.com_unsub=0&username%40gmail.com_mod=0&username%40gmail.com_hide=0&username%40gmail.com_nomail=0&username%40gmail.com_ack=0&username%40gmail.com_notmetoo=0&username%40gmail.com_nodupes=0&username%40gmail.com_digest=1&username%40gmail.com_plain=0&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password

http://domain.com/mailman/admin/listname/members?findmember=username%40gmail.com&user=username%40gmail.com&username%40gmail.com_unsub=off&username%40gmail.com_mod=off&username%40gmail.com_hide=off&username%40gmail.com_nomail=off&username%40gmail.com_ack=off&username%40gmail.com_notmetoo=off&username%40gmail.com_nodupes=off&username%40gmail.com_digest=on&username%40gmail.com_plain=off&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=off&adminpw=password

http://domain.com/mailman/admin/listname/members?user=username%40gmail.com&username%40gmail.com_unsub=off&username%40gmail.com_mod=off&username%40gmail.com_hide=off&username%40gmail.com_nomail=off&username%40gmail.com_ack=off&username%40gmail.com_notmetoo=off&username%40gmail.com_nodupes=off&username%40gmail.com_digest=on&username%40gmail.com_plain=off&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password

http://domain.com/mailman/admin/listname/members?user=username%40gmail.com&username%40gmail.com_unsub=0&username%40gmail.com_mod=0&username%40gmail.com_hide=0&username%40gmail.com_nomail=0&username%40gmail.com_ack=0&username%40gmail.com_notmetoo=0&username%40gmail.com_nodupes=0&username%40gmail.com_digest=1&username%40gmail.com_plain=0&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org