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 =
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.
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.
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
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 at
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
On 22/06/2015 1:58 PM, Stephen J. Turnbull wrote:
As Mark already said, according to the standards it is correct and
good practice to add a DKIM signature to every message you process
outside of the MTA and then reinject into the Internet mail system.
In more friendly terms, if you simply
On Mon, Jun 22, 2015 at 8:06 PM, Stephen J. Turnbull step...@xemacs.org 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
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), whereas
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
10 matches
Mail list logo
