Re: [Mailman-Developers] Regarding the idea " A Dashboard for Admins/Owners/Moderators "

Abhilash Raj writes: > What you need to start with is clearly stating what do you mean by > "Dashboard", +1 Also (I've referenced this before), two years ago Systers had a project "Mailman Interface" or "MI" which was exactly a dashboard (if by dashboard you mean a "collection of widgets nicel

Re: [Mailman-Developers] Some doubts, feature request and bug in postorius

Hi Ashish, On 8 March 2015 at 15:28, Ashish Kumar wrote: > Hi, > I am new to postorius interface. I was going through it and In some places > I was confused and Hence, made below points for discussion. > > 1. How to register a user through postorius web interface? For now, people can register on

Re: [Mailman-Developers] Regarding the idea " A Dashboard for Admins/Owners/Moderators "

Hi Raja, On 11 March 2015 at 01:39, rajashekar reddy wrote: > hello , > > I am Raja shekar Reddy, i have read the idea of "A Dashboard for > Admins/Owners/Moderators " in ideas page started of thinking it , i had > good knowledge in javascript ,html,python and had confidence that i could > do t

Re: [Mailman-Developers] Doubt regarding threads

> After enough exchanges, the reference line will get too long, and then > the proper (per the RFC) procedure is to drop the oldest reference. (For > threading to work in the MUA, it only needs the last couple to find the > latest message that has been received and thread under it) > > There is als

[Mailman-Developers] RES: Mailman error after restoring backup

As long as you're here, you may as well continue this thread (which I'm going to suppress from now on on my MUA). But this list is for development of Mailman; debugging configuration is appropriate for mailman-us...@python.org. ___ Mailman-Developers ma

Re: [Mailman-Developers] MIME footers

Murray S. Kucherawy writes: > I had forgotten about message headers (i.e., prepended text). Are > those common? I had thought pretty much everyone uses footers > only. They're sometimes useful on lists that only get occasional distribution. I've used them in situations where I have an emerg

Re: [Mailman-Developers] RES: RES: Mailman error after restoring backup

On 03/10/2015 06:12 PM, jovino Borret wrote: > Thank you again, > > There is one Postfix that runs in the same server where Mailman runs > (We have another Postfix installed in the mail server (two differents > machines). > > The first 9 lines of the file main.cf from Mailman server fol

[Mailman-Developers] RES: RES: Mailman error after restoring backup

Thank you again, There is one Postfix that runs in the same server where Mailman runs (We have another Postfix installed in the mail server (two differents machines). The first 9 lines of the file main.cf from Mailman server follow: myhostname = e-listas.uerj.br mydomain = e-listas.uer

Re: [Mailman-Developers] RES: Mailman error after restoring backup

On 03/10/2015 05:41 PM, jovino Borret wrote: > >In my last mail, replying some questions, I have forgotten to include > these messages of /var/log/mailman/smtp-failure : > > Mar 10 21:30:51 2015 (2185) delivery to luci...@uol.com.br failed with code > -1: Server not connected > Mar 10 21:

[Mailman-Developers] RES: Mailman error after restoring backup

Hi Mark, In my last mail, replying some questions, I have forgotten to include these messages of /var/log/mailman/smtp-failure : Mar 10 21:30:51 2015 (2185) delivery to luci...@uol.com.br failed with code -1: Server not connected Mar 10 21:30:51 2015 (2185) delivery to tadeu.r...@gmail.co

Re: [Mailman-Developers] RES: Mailman error after restoring backup

On 03/10/2015 04:20 PM, jovino Borret wrote: > Thanks a lot Mark, > > >I have found in the /var/log/maillog a lot of messages like this: > > Mar 10 19:53:43 e-listas postfix/smtpd[2190]: NOQUEUE: reject: RCPT from > localhost[::1]: 554 5.7.1 : Relay access denied; > from= to= > proto=ESM

[Mailman-Developers] RES: Mailman error after restoring backup

Thanks a lot Mark, I have found in the /var/log/maillog a lot of messages like this: Mar 10 19:53:43 e-listas postfix/smtpd[2190]: NOQUEUE: reject: RCPT from localhost[::1]: 554 5.7.1 : Relay access denied; from= to= proto=ESMTP helo= Mar 10 19:53:45 e-listas postfix/smtpd[2190]: too man

[Mailman-Developers] Fast development environment setup for newbies using mmdev_bootstrap

Hello everyone, The newbies starting to contribute to mailman sometimes face difficulty in setting up the dev environment for Mailman. I created a repo to automate setting up mailman for usage and dev environment interactively. It automatically creat

Re: [Mailman-Developers] MIME footers

OK, this time I was properly caffeinated, but that also meant I had a short attention span. :-) Sorry for the long delay replying. On Fri, Feb 27, 2015 at 12:55 PM, Daniel Kahn Gillmor wrote: > One issue this process brings up is that it's now necessary to treat > pretty much every part of the

Re: [Mailman-Developers] Mailman error after restoring backup

On 03/10/2015 01:13 PM, jovino Borret wrote: > > The problem is that after restarting Postfix and Mailman, many error > messages > > Is been logged in the /var/log/mailman. He is some examples: > > 1) /var/log/mailman/post > > > > Mar 10 15:20:20 2015 (1454) post to uer

[Mailman-Developers] Mailman error after restoring backup

Hi all, We have a problem in the Mailman Server and I had to restore a image from some months ago. After restoring this image, I have restored /var/lib/mailman, /usr/lib/mailman and /var/spool of the system. The problem is that after restarting Postfix and Mailman, many error m

[Mailman-Developers] Regarding the idea " A Dashboard for Admins/Owners/Moderators "

hello , I am Raja shekar Reddy, i have read the idea of "A Dashboard for Admins/Owners/Moderators " in ideas page started of thinking it , i had good knowledge in javascript ,html,python and had confidence that i could do this. What I understood is " now for every list there is one seperate pag

Re: [Mailman-Developers] full anonymisation approach

Stephen J. Turnbull writes: > It's really not possible. You have proposed an implementation but not > addressed the requirements issue. In software engineering "correct > design" means "the implementation will satisfy the requirements", but > I still don't really understand what problem you are t