On 28 February 2015 at 10:07, Pranjal Yadav godricg...@gmail.com wrote:
Abhilash,
Thanks! it worked as you said. But renaming clean method is not
conventional. I changed the names and it looks like 'clean_password_repeat'
is good and that is the last input for that test as well, so I don't
On 27 February 2015 at 20:39, Pranjal Yadav godricg...@gmail.com wrote:
Hi Abhilash,
Thanks for your help. I read that we need to define methods as
clean_fieldname however I missed
I was cleaning multiple fields. For the listname method it works the way you
told me but I tried something
On 27 February 2015 at 19:16, Aanand Shekhar Roy 2013...@iiitdmj.ac.in wrote:
Based on the discussion with @Abhilash, Below is the modified approach
for plugin ideas:
*Banned Words*:
1. We create a common set of words that are to be banned in a mail.
How do you create such a list, who
Abhilash,
renaming 'clean_password' to 'clean' did help in running all the tests
successfully but looking at the
coverage stats I realized the 'invalid_email' test is still not functional
since those lines are shown as 'missing'
in stats, So it was just a work around and it didn't actually help.
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
Based on the discussion with @Abhilash, Below is the modified approach
for plugin ideas:
*Banned Words*:
1. We create a common set of words that are to be banned in a mail.
How do you create such a list, who decides which words are banned?
Would it be possible to add/remove words from
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
Hi Abhilash,
Thanks for your help. I read that we need to define methods as
clean_fieldname however I missed
I was cleaning multiple fields. For the listname method it works the way
you told me but I tried something
similar ( http://pastebin.com/p40A19hU ) and it didn't work. If you could
tell me
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,
On Tue, Feb 24, 2015 at 2:08 PM, Daniel Kahn Gillmor d...@fifthhorseman.net
wrote:
Equally important: What would it do to sign a message that's not MIME
to begin with? Could it be compelled to turn it into a MIME message,
perhaps treating the original as a single-part text/plain message
On Feb 27, 2015, at 11:46 AM, Murray S. Kucherawy wrote:
How absurd would it be to propose a flag for Mailman that would take your
first case (non-MIME, or single-part text/plain) and convert it to a
multipart/mixed with a child part of the original text/plain, and then
apply the algorithm you
Hi Murray--
On Fri 2015-02-27 14:46:40 -0500, Murray S. Kucherawy wrote:
Sorry, by sign I meant add a footer. I probably said sign because
this is related to some DKIM work I've been planning, and the morning's
caffeine was already wearing off.
:)
Thanks for that detailed answer (and Barry
On 02/27/2015 12:07 PM, Barry Warsaw wrote:
On Feb 27, 2015, at 11:46 AM, Murray S. Kucherawy wrote:
How absurd would it be to propose a flag for Mailman that would take your
first case (non-MIME, or single-part text/plain) and convert it to a
multipart/mixed with a child part of the
On Fri 2015-02-27 15:07:52 -0500, Barry Warsaw wrote:
The biggest downside, and probably the main reason we append the footer text
in the text/plain-compatible-charset case is because of crappy MUAs. I think
we *still* get complaints about the MIME composition not being rendered very
well.
On 02/27/2015 01:00 PM, Daniel Kahn Gillmor wrote:
Can you point us to those complaints?
http://wiki.list.org/x/4030707 and the posts linked from there in the
archive of the Mailman-users list and many other posts in that archive.
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
Hi Pranjal,
I was able to run the tests in ListNewTest, and kind of debug the
other test too.
In ListNewTest you have two tests doing the same thing, probably you intended
at doing something else, but there is nothing in there right now.
there is a method of django forms called as `errors`. So
21 matches
Mail list logo
