Thanks. Barry for the detailed explanation. I will surely have a look on
that part as you mentioned.
Thanks,
Ankush Sharma
github.com/black-perl
On Fri, Feb 27, 2015 at 9:47 PM, Barry Warsaw ba...@list.org wrote:
On Feb 27, 2015, at 01:02 PM, Ankush Sharma B.Tech. Electronics Engg,
IIT(BHU),
Yes, Stephen also mentioned about its separate working and not being able
to get integrated with mailman. But, I guess it would be cool if this
metrics project can be integrated with postorius or hyperkitty as you
mentioned.
Thanks,
Ankush Sharma
github.com/black-perl
On Sat, Feb 28, 2015 at
There’s a bug at:
https://bugs.launchpad.net/mailman/+bug/1423756
Requesting domainowner and serverowner
thanks
On 26 Feb 2015, at 10:10 am, Barry Warsaw ba...@list.org wrote:
On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote:
I’m looking forward to being able to set and get domainowner and
On 02/27/2015 12:24 AM, Terri Oda wrote:
It's not that it's a bad feature in isolation. But there are so *many*
potential features for Mailman, and I'd like to see ideas that are less
socially problematic get implemented first.
And there are many customer relations managements systems
On Feb 27, 2015, at 01:02 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU),
Varanasi (U.P.), INDIA wrote:
A personalized mailing list will allow mailman users to send personalized
emails to all the list members from a common email template.
Almost all the pieces are already there to support
On 2015-02-27 1:06 AM, Stephen J. Turnbull wrote:
Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA
writes:
I was wondering if there is a sort of tool that generates summaries
for mailing list activity and charts like number of users, number
of active users,
Honestly, I don't love this idea. I would be technically feasible with
VERP, but it edges into features that are very popular for people
sending spam.
On 2015-02-26 11:32 PM, Ankush Sharma B.Tech. Electronics Engg,
IIT(BHU), Varanasi (U.P.), INDIA wrote:
How about having personalized
Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA
writes:
I was wondering if there is a sort of tool that generates summaries
for mailing list activity and charts like number of users, number
of active users, etc. Would something like this be a good idea or
is it
I realize the feature I proposed earlier is more of a commercial feature
and might not be be so useful for Mailman as you mentioned it's pitfalls.
Are there other directions that I should think in? I am good with Python,
Javascript, HTML5.
I was wondering if there is a sort of tool that
I am quite aware of the definition of spam (in fact, I have a master's
thesis on the subject).
What I'm concerned about is that in the past, mail merges (which is what
you're describing) is a feature that has often been requested by people
doing marketing lists. It's not a subset of users
Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA
writes:
Spamming would be the case when you are sending the emails to people who
don't want to receive such emails. While if we control the email variable
to take value from the set of emails of the list members only
How about having personalized announcement mailing lists ?
A personalized mailing list will allow mailman users to send personalized
emails to all the list members from a common email template. Suppose I am
the manager of a company and I need to ask all the workers for a meeting. I
want each of
On Fri, Feb 27, 2015 at 1:13 PM, Terri Oda te...@toybox.ca wrote:
Honestly, I don't love this idea. I would be technically feasible with
VERP,
I don't know about VERP. I will surely have a look.
but it edges into features that are very popular for people sending spam.
Spamming would be
On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote:
I’m looking forward to being able to set and get domainowner and serverowner
(or siteowner or whatever its called). It will allow me to delete lots of
code and there’s no greater joy than deleting code.
Are you anticipating this will be in V3.0?
On Feb 24, 2015, at 07:53 AM, Chris Nulk wrote:
Also, I believe I remember a goal for Mailman v3 was to have one instance of
Mailman be able to host lists for multiple domains.
Yes, but not on physically distinct hosts. Or in other words, yes MM3
supports virtual domains
Given that information
On 2/23/2015 8:08 PM, Stephen J. Turnbull wrote:
Andrew Stuart writes:
I am currently associating users, not addresses with these
permissions, so your suggestion is compatible with my stuff.
+1 on associating users with permissions (plus the validation Barry
recommends).
site owner
I’m looking forward to being able to set and get domainowner and serverowner
(or siteowner or whatever its called). It will allow me to delete lots of code
and there’s no greater joy than deleting code.
Are you anticipating this will be in V3.0?
thanks
as
On 24 Feb 2015, at 11:42 am, Barry
Andrew Stuart writes:
I am currently associating users, not addresses with these
permissions, so your suggestion is compatible with my stuff.
+1 on associating users with permissions (plus the validation Barry
recommends).
site owner does sound more appropriate than server owner.
Users
Do you think this has to be integrated into the core for 3.0? I'd still
prefer to keep it separate for better experimentation and testing.
if:
there was an “application data” table:
resource_type | resource_id |
Barry Warsaw writes:
On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote:
It’s workable as a part of the auth proxy but feels like it would fit better
in the Mailman core database since the data is so tightly bound to Mailman
resources. It’ll need an effective replication mechanism to
On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote:
It’s workable as a part of the auth proxy but feels like it would fit better
in the Mailman core database since the data is so tightly bound to Mailman
resources. It’ll need an effective replication mechanism to ensure
consistency with Mailman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.02.2015 um 06:46 schrieb Terri Oda:
Thanks all! I've put up stuff for the ideas I could describe well
enough off the top of my head.
Thank you Terri!
Also, mentors, I've listed a few likely key people beside each
project idea, but some
[1] The additional user info bit possibly re-raises the big question of a
central user data store for all Mailman components, which will clearly not
be solved as part of a GSoC project, especially a beginner-friendly one.
But we do already have a little bit of info, the user's email
Thanks all! I've put up stuff for the ideas I could describe well
enough off the top of my head.
Also, mentors, I've listed a few likely key people beside each project
idea, but some of them are just a generic anyone can help with this --
if any of these particularly interests you, please
How about domain-wide settings for default list styles or maybe set a
default list style for an entire mailman installation through Postorius?
That could make the work of list-admins easy if they manage too many
lists and don't want to do repetitive change in each and every list.
Additionally
On Feb 18, 2015, at 12:24 AM, Abhilash Raj wrote:
How about domain-wide settings for default list styles or maybe set a
default list style for an entire mailman installation through Postorius?
That could make the work of list-admins easy if they manage too many
lists and don't want to do
On 02/17/2015 04:03 AM, Terri Oda wrote:
Hi all,
In my role as org admin for Python, I'm trying to make sure we have more
beginner-friendly ideas on the GSoC pages, and Mailman's among the
groups that doesn't have any. How embarrassing for me as a Mailman
developer. ;) It's also a problem
27 matches
Mail list logo
