Bugs item #1621278, was opened at 2006-12-23 06:16
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1621278&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Kumaraguru (kums)
Assigned to: Nobody/Anonymous (nobody)
Summary: incomplete reply link in archived posts
Initial Comment:
When viewing the archived messages/posts, one can reply to a post by clicking the mailto link next to the author's name. This is of the form
mailto:foo@bar.com?Subject=postsubject&In-Reply-To=unique_message_id
************
THE BUG
************
The unique id for In-Reply-To is present only for posts that are replies to another post. The top level posts don't have a unique id in the mailto link. It is simply blank like it's shown below.
mailto:foo@bar.com?Subject=postsubject&In-Reply-To=
******************
WHY IT MATTERS
******************
Some people may disable mail delivery when the mailing list becomes a high volume one. They can see the archived messages through the web front-end. If they are still subscribed to the mailing list, they can even reply to the list by clicking the above mentioned mailto link.
For messages which are replies to another post, the mailto link is properly formed having a unique messageid for use in the In-Reply-To header. However, for the top level posts, the mailto link is incomplete as the In-Reply-To is simply blank. If someone replied to a top level post by clicking it's reply link, the reply message will appear out-of-sync as a different top-level post instead of being a reply to the original post.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2006-12-23 09:40
Message:
Logged In: YES
user_id=1123998
Originator: NO
It's actually worse than you say. The In-Reply-To= in the mailto URL does
not contain the Message-ID: of the message being viewed. It contains the
In-Reply-To: of the message being viewed, and can be empty for a
subordinate message in a thread if that message doesn't contain an
In-Reply-To: and was threaded by References:. Thus, even when present, it
is wrong and results in improper threading of replies that use it.
I will look at fixing this, but the archiver is complex and fragile, so I
don't know how difficult this will be.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1621278&group_…
Bugs item #1621278, was opened at 2006-12-23 19:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1621278&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Kumaraguru (kums)
Assigned to: Nobody/Anonymous (nobody)
Summary: incomplete reply link in archived posts
Initial Comment:
When viewing the archived messages/posts, one can reply to a post by clicking the mailto link next to the author's name. This is of the form
mailto:foo@bar.com?Subject=postsubject&In-Reply-To=unique_message_id
************
THE BUG
************
The unique id for In-Reply-To is present only for posts that are replies to another post. The top level posts don't have a unique id in the mailto link. It is simply blank like it's shown below.
mailto:foo@bar.com?Subject=postsubject&In-Reply-To=
******************
WHY IT MATTERS
******************
Some people may disable mail delivery when the mailing list becomes a high volume one. They can see the archived messages through the web front-end. If they are still subscribed to the mailing list, they can even reply to the list by clicking the above mentioned mailto link.
For messages which are replies to another post, the mailto link is properly formed having a unique messageid for use in the In-Reply-To header. However, for the top level posts, the mailto link is incomplete as the In-Reply-To is simply blank. If someone replied to a top level post by clicking it's reply link, the reply message will appear out-of-sync as a different top-level post instead of being a reply to the original post.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1621278&group_…
Bugs item #1246004, was opened at 2005-07-27 06:19
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Auke Kok (sofar)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1.6 bin/arch bombs out on unicodeerror
Initial Comment:
Running bin/arch on my i18n- development list I got
this beauty:
Updating HTML for article 2390
Updating HTML for article 2391
Pickling archive state into
/var/mailman/archives/private/xfce-i18n/pipermail.pck
Traceback (most recent call last):
File "bin/arch", line 200, in ?
main()
File "bin/arch", line 188, in main
archiver.processUnixMailbox(fp, start, end)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 573, in processUnixMailbox
self.add_article(a)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 625, in add_article
article.parentID = parentID =
self.get_parent_info(arch, article)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 657, in get_parent_info
article.subject)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
311, in getOldestArticle
self.__openIndices(archive)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
251, in __openIndices
t = DumbBTree(os.path.join(arcdir, archive + '-' + i))
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
65, in __init__
self.load()
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
179, in load
self.__sort(dirty=1)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
73, in __sort
self.sorted.sort()
UnicodeDecodeError: 'ascii' codec can't decode byte
0xc3 in position 0: ordinal not in range(128)
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2006-12-15 10:10
Message:
Logged In: YES
user_id=1123998
Originator: NO
See the threads at
http://mail.python.org/pipermail/mailman-developers/2006-February/018587.ht…
and
http://mail.python.org/pipermail/mailman-users/2006-February/049345.html
----------------------------------------------------------------------
Comment By: Eugene Crosser (crosser)
Date: 2006-12-15 02:37
Message:
Logged In: YES
user_id=124141
Originator: NO
I can see the same thing (line numbers are different) with 2.1.9 version.
Can it be that no one else got bitten by it yet? How to fix it?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…
Bugs item #1246004, was opened at 2005-07-27 17:19
Message generated for change (Comment added) made by crosser
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Auke Kok (sofar)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1.6 bin/arch bombs out on unicodeerror
Initial Comment:
Running bin/arch on my i18n- development list I got
this beauty:
Updating HTML for article 2390
Updating HTML for article 2391
Pickling archive state into
/var/mailman/archives/private/xfce-i18n/pipermail.pck
Traceback (most recent call last):
File "bin/arch", line 200, in ?
main()
File "bin/arch", line 188, in main
archiver.processUnixMailbox(fp, start, end)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 573, in processUnixMailbox
self.add_article(a)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 625, in add_article
article.parentID = parentID =
self.get_parent_info(arch, article)
File "/var/mailman/Mailman/Archiver/pipermail.py",
line 657, in get_parent_info
article.subject)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
311, in getOldestArticle
self.__openIndices(archive)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
251, in __openIndices
t = DumbBTree(os.path.join(arcdir, archive + '-' + i))
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
65, in __init__
self.load()
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
179, in load
self.__sort(dirty=1)
File
"/var/mailman/Mailman/Archiver/HyperDatabase.py", line
73, in __sort
self.sorted.sort()
UnicodeDecodeError: 'ascii' codec can't decode byte
0xc3 in position 0: ordinal not in range(128)
----------------------------------------------------------------------
Comment By: Eugene Crosser (crosser)
Date: 2006-12-15 13:37
Message:
Logged In: YES
user_id=124141
Originator: NO
I can see the same thing (line numbers are different) with 2.1.9 version.
Can it be that no one else got bitten by it yet? How to fix it?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…
Patches item #1615748, was opened at 2006-12-14 15:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1615748&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add a configurable site logo
Initial Comment:
The attached patch adds a site logo - turned off by default. It also fixes the logo outputs to make it more consistent.
Please consider.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1615748&group_…
Bugs item #1256272, was opened at 2005-08-11 01:47
Message generated for change (Comment added) made by poelzi
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: nntp/news
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Kate Turner (kateturner)
Assigned to: Nobody/Anonymous (nobody)
Summary: NNTP gatewaying trashes Message-IDs
Initial Comment:
when a message is relayed to NNTP, the NewsRunner
unconditionally replaces the existing Message-ID with
its own. this breaking threading when reading a list
via news, and when an NNTP user replies to a list message.
a better solution would be either:
1) do not rewrite the message-id unless the NNTP server
reports an error when posting it (duplicate ID); or
2) optionally, always rewrite posters' message-ids into
a mailman-generated ID, and use this ID for both mail
and news.
i have implemented the former at our site and it
appears to work, but it's so ugly i'd not feel
comfortable submitting a patch for it.
----------------------------------------------------------------------
Comment By: Daniel Poelzleithner (poelzi)
Date: 2006-12-12 21:12
Message:
Logged In: YES
user_id=70861
Originator: NO
nobrowser: the problem is, that newsserver drop messages in crossposts
when one is a mailinglist and the other is a newsgroup.
i just had an idea. we you use a small sqlite table:
| Original-ID | Translated-ID | Last-Used |
When a message is pulled von news, we replace in the reference header alle
ocurrences of translated-id's with their original id's.
When a message is posted to news, we replace all original-id's with
translated-id's.
A new message still generates a new message id, the original is inserted
into the table along with it's original id.
On all actions, we update last-used.
The daily cron job, deletes all last-used older than x days (60 for
example) to keep the table small. This way, no thread trashing would occure
on both sides, while keeping crossposting possible and overhead isn't too
much i think.
----------------------------------------------------------------------
Comment By: Kate Turner (kateturner)
Date: 2006-04-29 16:44
Message:
Logged In: YES
user_id=1116721
the conflicts occur when a user cross-posts a message to
two lists. the newsrunner won't turn it into a cross-post,
instead it tries to post it separately to both groups, and
the news server rejects the second one for a duplicate
message-id (tested with innd).
of course, you could say this behaviour is a bug too :) i'm
not sure what the best way to group cross-posted messages
is, since they won't be received by the same mailman
instance. (cancelling the first and re-posting to both
groups might work, but i don't know if inn will still
record the message-id and not allow it to be reused.)
----------------------------------------------------------------------
Comment By: Ian Z. (nobrowser)
Date: 2006-04-20 07:13
Message:
Logged In: YES
user_id=1192798
Finally! I thought I was the only one who noticed this.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346413
Why would the mail message-id ever cause a conflict with
the NNTP server? message-ids are supposed to be globally
unique and there is a convention (in RFC 2822?) that ensures
it (put in the FQDN and something unique to the generating
software). So I think 1) is not ugly but correct :)
2) wouldn't completely solve the problem.
I can post one copy of a message to a mailman list and
another directly to another recipient, including myself.
(I actually Cc myself on all mail I send). If mailman
does 2), the extra recipient will still be confused.
Ian
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_…
Bugs item #1610511, was opened at 2006-12-06 17:00
Message generated for change (Settings changed) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: MikeLempriere (mikelempriere)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot access old lists after delete/recreate of site list
Initial Comment:
I'm running Mailman 2.1.7 on FreeBSD 5.4, using sendmail. I've had the system configured and it's been running multiple lists for years.
Then, in the name of security ("don't use it, turn it off"), I clobbered the "mailman" list which I didn't realize I needed...
Ok, so, I'm an idiot -- I should have gone with the other maxim "don't fix it if it ain't broke"...
I clobbered the list using 'rmlist'.
Upon my next restart of mailman, I got a "site list is missing" error. A quick web search found my answer, namely that the "mailman" list is required.
I used "newlist" to create a new one. Yay, I was now able to restart mailman with no error!
I then created some new lists, and was able to web manage them just fine.
However, here's where it goes bad -- I can no longer get in to the web manager for any of the lists that were created before I blew away the "mailman" list. The web browser simply hangs awaiting server reply upon my hitting the login button.
I can get into the new "mailman" list, and have subscribed myself to it.
I have checked the mm_cfg.py and it is unchanged from mm_cfg.py.dist (only the import of default settings).
Help!
(And Thanks in advance)
----------------------------------------------------------------------
Comment By: MikeLempriere (mikelempriere)
Date: 2006-12-09 04:16
Message:
Logged In: YES
user_id=1662619
Originator: YES
With some help from msapiro (thank you again) I've gotten past the
rpoblem. There were a dozen or so old locks in the locks directory for the
two lists that were affected. Upon stopping mailman daemons, they all
remained -- a bad sign. I deleted them, restarted mailman, all seems well
now, yay!
The two lists that had lockfiles hanging about are the lists that I am
most likely to have had left open in my browser over an extended period of
time (not logged out, just closed the tab thus still logged in).
Additionally, there are other lists that existed before my having clobbered
the site list that did not have bad locks left around, so I believe my
conclusion that clobbering the site list caused this was wrong.
As it's not definate that this problem arose from my having clobbered the
site list, I'd have no objections to simply closing this bug report.
As a matter of fact, mailman is coring every night (I believe when some
spam hits it), so it's more likely this is the problem leaving behind the
lockfiles. I'll try to upgrade to the latest version before reporting this
latter problem.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-12-06 18:37
Message:
Logged In: YES
user_id=1123998
Originator: NO
First, please to subscribe to mailman-users(a)python.org -
http://mail.python.org/mailman/listinfo/mailman-users - and repost this
there if follow up is necessary. The bug tracker is not the best place for
questions of this nature.
Have you checked Mailman's locks/ directory for stale list locks? It seems
like that could be the problem although I don't understand how all the
lists could have gotten locked but maybe something to do with cron or some
other processing while the site list was missing.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Bugs item #1610511, was opened at 2006-12-06 17:00
Message generated for change (Settings changed) made by mikelempriere
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: MikeLempriere (mikelempriere)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot access old lists after delete/recreate of site list
Initial Comment:
I'm running Mailman 2.1.7 on FreeBSD 5.4, using sendmail. I've had the system configured and it's been running multiple lists for years.
Then, in the name of security ("don't use it, turn it off"), I clobbered the "mailman" list which I didn't realize I needed...
Ok, so, I'm an idiot -- I should have gone with the other maxim "don't fix it if it ain't broke"...
I clobbered the list using 'rmlist'.
Upon my next restart of mailman, I got a "site list is missing" error. A quick web search found my answer, namely that the "mailman" list is required.
I used "newlist" to create a new one. Yay, I was now able to restart mailman with no error!
I then created some new lists, and was able to web manage them just fine.
However, here's where it goes bad -- I can no longer get in to the web manager for any of the lists that were created before I blew away the "mailman" list. The web browser simply hangs awaiting server reply upon my hitting the login button.
I can get into the new "mailman" list, and have subscribed myself to it.
I have checked the mm_cfg.py and it is unchanged from mm_cfg.py.dist (only the import of default settings).
Help!
(And Thanks in advance)
----------------------------------------------------------------------
Comment By: MikeLempriere (mikelempriere)
Date: 2006-12-09 04:16
Message:
Logged In: YES
user_id=1662619
Originator: YES
With some help from msapiro (thank you again) I've gotten past the
rpoblem. There were a dozen or so old locks in the locks directory for
the two lists that were affected. Upon stopping mailman daemons, they all
remained -- a bad sign. I deleted them, restarted mailman, all seems well
now, yay!
The two lists that had lockfiles hanging about are the lists that I am
most likely to have had left open in my browser over an extended period of
time (not logged out, just closed the tab thus still logged in).
Additionally, there are other lists that existed before my having
clobbered the site list that did not have bad locks left around, so I
believe my conclusion that clobbering the site list caused this was
wrong.
As it's not definate that this problem arose from my having clobbered the
site list, I'd have no objections to simply closing this bug report.
As a matter of fact, mailman is coring every night (I believe when some
spam hits it), so it's more likely this is the problem leaving behind the
lockfiles. I'll try to upgrade to the latest version before reporting
this latter problem.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-12-06 18:37
Message:
Logged In: YES
user_id=1123998
Originator: NO
First, please to subscribe to mailman-users(a)python.org -
http://mail.python.org/mailman/listinfo/mailman-users - and repost this
there if follow up is necessary. The bug tracker is not the best place for
questions of this nature.
Have you checked Mailman's locks/ directory for stale list locks? It seems
like that could be the problem although I don't understand how all the
lists could have gotten locked but maybe something to do with cron or some
other processing while the site list was missing.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Bugs item #1610511, was opened at 2006-12-06 17:00
Message generated for change (Comment added) made by mikelempriere
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: MikeLempriere (mikelempriere)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot access old lists after delete/recreate of site list
Initial Comment:
I'm running Mailman 2.1.7 on FreeBSD 5.4, using sendmail. I've had the system configured and it's been running multiple lists for years.
Then, in the name of security ("don't use it, turn it off"), I clobbered the "mailman" list which I didn't realize I needed...
Ok, so, I'm an idiot -- I should have gone with the other maxim "don't fix it if it ain't broke"...
I clobbered the list using 'rmlist'.
Upon my next restart of mailman, I got a "site list is missing" error. A quick web search found my answer, namely that the "mailman" list is required.
I used "newlist" to create a new one. Yay, I was now able to restart mailman with no error!
I then created some new lists, and was able to web manage them just fine.
However, here's where it goes bad -- I can no longer get in to the web manager for any of the lists that were created before I blew away the "mailman" list. The web browser simply hangs awaiting server reply upon my hitting the login button.
I can get into the new "mailman" list, and have subscribed myself to it.
I have checked the mm_cfg.py and it is unchanged from mm_cfg.py.dist (only the import of default settings).
Help!
(And Thanks in advance)
----------------------------------------------------------------------
>Comment By: MikeLempriere (mikelempriere)
Date: 2006-12-09 04:16
Message:
Logged In: YES
user_id=1662619
Originator: YES
With some help from msapiro (thank you again) I've gotten past the
rpoblem. There were a dozen or so old locks in the locks directory for the
two lists that were affected. Upon stopping mailman daemons, they all
remained -- a bad sign. I deleted them, restarted mailman, all seems well
now, yay!
The two lists that had lockfiles hanging about are the lists that I am
most likely to have had left open in my browser over an extended period of
time (not logged out, just closed the tab thus still logged in).
Additionally, there are other lists that existed before my having clobbered
the site list that did not have bad locks left around, so I believe my
conclusion that clobbering the site list caused this was wrong.
As it's not definate that this problem arose from my having clobbered the
site list, I'd have no objections to simply closing this bug report.
As a matter of fact, mailman is coring every night (I believe when some
spam hits it), so it's more likely this is the problem leaving behind the
lockfiles. I'll try to upgrade to the latest version before reporting this
latter problem.
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-12-06 18:37
Message:
Logged In: YES
user_id=1123998
Originator: NO
First, please to subscribe to mailman-users(a)python.org -
http://mail.python.org/mailman/listinfo/mailman-users - and repost this
there if follow up is necessary. The bug tracker is not the best place for
questions of this nature.
Have you checked Mailman's locks/ directory for stale list locks? It seems
like that could be the problem although I don't understand how all the
lists could have gotten locked but maybe something to do with cron or some
other processing while the site list was missing.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1610511&group_…
Patches item #1611855, was opened at 2006-12-08 16:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Abram Thielke (athielke)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add invite option to add_members script
Initial Comment:
This will add two options to the add_members script:
--invite-msg-file=file
-m file
This will prepend the message in the file to the invite email that gets generated.
--invite=<y|n>
-i <y|n>
Set to yes if you only want to invite the users to a list, instead of subscribing them.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_…