Re: [Mailman-Users] HTTP_X_FORWARDED_FOR logging support

2015-06-22 Thread Stephen J. Turnbull
Jim Popovitch writes: > For the purpose of something like fail2ban all that is needed is > the IPaddr. Having all the others would be a "nice to have", but > would really drive up the patch size. >From 10 lines to 20? I'd be more worried about the size of message or msgdata objects. > REMO

[Mailman-Users] stopped sending mail

2015-06-22 Thread Al's mail
Hi everyone, I’m having problems with my mailman installation. Its running on a FreeBSD 10.1 and mailman version is 2.1.20. I’ve been tracking an intermittent delivery problem with digests, the reports were of “missing digests”. I couldn’t see anything other than the usual non-delivery reaso

Re: [Mailman-Users] DKIM best practise

2015-06-22 Thread Mark Sapiro
On 06/21/2015 08:58 PM, Stephen J. Turnbull wrote: > Yasir Assam writes: > > > I noticed that this list, mailman-users@python.org, doesn't add a > > DKIM header unless the list itself generates the email, i.e. the > > email you sent to this list only has your DKIM header > > (d=msapiro.net), w

Re: [Mailman-Users] HTTP_X_FORWARDED_FOR logging support

2015-06-22 Thread Jim Popovitch
On Mon, Jun 22, 2015 at 8:06 PM, Stephen J. Turnbull wrote: > Are you proposing this for inclusion in a future Mailman distribution? Yes, at least for the 2.x trunk. > If so, RFC 7239 Forwarded-For should be supported as well. Sure, that makes good sense to add. > Also, since one of the purpos

Re: [Mailman-Users] how to force mailman send a message to all members at a time?

2015-06-22 Thread Mark Sapiro
On 06/22/2015 02:44 AM, surdet wrote: > I have installed mailman version 2.1.12 with postfix. I have 6 members > of a list. I found some time mailman send a message to 4 members and 10 > minutes later it send a message to 2 members remaining. How can I force > mailman send a message to all members

Re: [Mailman-Users] Attachments not getting through at random...

2015-06-22 Thread Mark Sapiro
On 06/21/2015 10:55 AM, Nick Stevens via Mailman-Users wrote: > Hi All, > I'm new to the list - I did search the archives, but cannot find anything > covering my specific case. In the future and when following up, please post from your subscribed (...@gmail.com) address, not ...@googlemail.com. O

[Mailman-Users] Attachments not getting through at random...

2015-06-22 Thread Nick Stevens via Mailman-Users
Hi All, I'm new to the list - I did search the archives, but cannot find anything covering my specific case. My problem is with attachments to my list. For some users, attachments never get through. I'm sure it is not the file, in a couple of cases I asked the senders to CC my personal, email add

[Mailman-Users] how to force mailman send a message to all members at a time?

2015-06-22 Thread surdet
I have installed mailman version 2.1.12 with postfix. I have 6 members of a list. I found some time mailman send a message to 4 members and 10 minutes later it send a message to 2 members remaining. How can I force mailman send a message to all members at a time? Thanks, Mr.Suradet C. -

[Mailman-Users] HTTP_X_FORWARDED_FOR logging support

2015-06-22 Thread Stephen J. Turnbull
Are you proposing this for inclusion in a future Mailman distribution? If so, RFC 7239 Forwarded-For should be supported as well. Also, since one of the purposes of this information appears to be detection of attacks of various kinds, I would think that instead of falling back to REMOTE_HOST or RE

[Mailman-Users] HTTP_X_FORWARDED_FOR logging support

2015-06-22 Thread Jim Popovitch
Hello, I'm looking for feedback on the attached patch which adds support for logging the real client IP address when Mailman is behind a proxy. I'm also looking for feedback on the use of REMOTE_ADDR instead of REMOTE_HOST. Ex: -remote = os.environ.get('REMOTE_HOST', + remote = os.environ