From mark at msapiro.net Wed Jul 6 17:12:02 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 Jul 2016 21:12:02 -0000 Subject: [Bug 266588] Re: Add SpamAssassin filter to mail pipeline References: <20080905193752.32763.39358.launchpad@forster.canonical.com> Message-ID: <20160706211202.23996.11787.malone@gac.canonical.com> For completeness, this is the spamd.py from comment #17 with the patch from comment #23 applied. It should be applicible for any Mailman 2.1 version. ** Attachment added: "Updated spamd.py" https://bugs.launchpad.net/mailman/+bug/266588/+attachment/4696590/+files/spamd.py -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266588 Title: Add SpamAssassin filter to mail pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266588/+subscriptions From mark at msapiro.net Wed Jul 6 17:06:25 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 Jul 2016 21:06:25 -0000 Subject: [Bug 266588] Re: Add SpamAssassin filter to mail pipeline References: <20080905193752.32763.39358.launchpad@forster.canonical.com> Message-ID: <20160706210625.18487.17550.malone@wampee.canonical.com> As of Mailman 2.1.21 the method for checking accept_these_nonmembers has changed again. For Mailman prior to 2.1.10, use the SpamAssassin.py attached to comment #18. For Mailman >= 2.1.10 and < 2.1.21 use that SpamAssassin.py patched with the patch attached to comment #22. For Mailman >= 2.1.21 use the SpamAssassin.py attached here. ** Attachment added: "Updated SpamAssassin.py Handler" https://bugs.launchpad.net/mailman/+bug/266588/+attachment/4696589/+files/SpamAssassin.py -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266588 Title: Add SpamAssassin filter to mail pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266588/+subscriptions From mark at msapiro.net Mon Jul 11 17:42:04 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2016 21:42:04 -0000 Subject: [Bug 558155] Re: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. References: <20100408090656.1687.59831.launchpad@loganberry.canonical.com> Message-ID: <20160711214205.17855.70984.launchpad@wampee.canonical.com> ** Summary changed: - i18n: Header Filter Rules (& fix) + i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558155 Title: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558155/+subscriptions From mark at msapiro.net Mon Jul 11 17:50:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2016 21:50:53 -0000 Subject: [Bug 558155] Re: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. References: <20100408090656.1687.59831.launchpad@loganberry.canonical.com> Message-ID: <20160711215053.23279.64156.malone@gac.canonical.com> Portions of this patch, but not the Unicode normalization have been applied or otherwise addressed in MM versions 2.1.6 through 2.1.15. I intend to deal with the spirit of the rest by converting the headers to the cset of the list's preferred language using encode(errors='backslashreplace') instead of encode(errors='replace'). In this way, these characters will be converted to '\uxxxx' escapes rather than '?', and header_filter_rules patterns can be constructed to match them. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.23 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558155 Title: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558155/+subscriptions From 558155 at bugs.launchpad.net Mon Jul 11 19:43:47 2016 From: 558155 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 11 Jul 2016 23:43:47 -0000 Subject: [Bug 558155] Re: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. References: <20100408090656.1687.59831.launchpad@loganberry.canonical.com> Message-ID: <20160711234351.796.32800.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558155 Title: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558155/+subscriptions From mark at msapiro.net Mon Jul 11 21:47:09 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2016 01:47:09 -0000 Subject: [Bug 558155] Re: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. References: <20100408090656.1687.59831.launchpad@loganberry.canonical.com> Message-ID: <20160712014710.25828.82875.malone@gac.canonical.com> The committed fix together with prior changes implements a few of the things in this patch. It does not do the Unicode normalization portion of this patch. I was mostly trying to address the issue of trying to recognize Chinese spam by detecting Chinese characters in message headers. I understand that the normalization can be important to actually match specific things in subjects in say Japanese on a Japanese language list. If that is still desired, please submit a new patch against the current code base. ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558155 Title: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558155/+subscriptions From 1602608 at bugs.launchpad.net Wed Jul 13 06:11:25 2016 From: 1602608 at bugs.launchpad.net (Sebastian Wagner) Date: Wed, 13 Jul 2016 10:11:25 -0000 Subject: [Bug 1602608] [NEW] mailman crash for subscription in webinterface Message-ID: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Public bug reported: A Traceback from mailman's logs for a subscription. The bug can be triggered with the following post-data: language='' Jul 11 20:29:34 2016 admin(29209): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(29209): [----- Mailman Version: 2.1.16 -----] admin(29209): [----- Traceback ------] admin(29209): Traceback (most recent call last): admin(29209): File "/var/lib/mailman/scripts/driver", line 117, in run_main admin(29209): main() admin(29209): File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 73, in main admin(29209): language = cgidata.getvalue('language') admin(29209): File "/usr/lib/python2.7/cgi.py", line 548, in getvalue admin(29209): if key in self: admin(29209): File "/usr/lib/python2.7/cgi.py", line 594, in __contains__ admin(29209): raise TypeError, "not indexable" admin(29209): TypeError: not indexable admin(29209): [----- Python Information -----] admin(29209): sys.version = 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] admin(29209): sys.executable = /usr/bin/python admin(29209): sys.prefix = /usr admin(29209): sys.exec_prefix = /usr admin(29209): sys.path = ['/var/lib/mailman/pythonlib', '/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(29209): sys.platform = linux2 admin(29209): [----- Environment Variables -----] admin(29209): SSL_VERSION_INTERFACE: mod_ssl/2.4.7 admin(29209): HTTP_REFERER: https://mail.example.com/cgi-bin/mailman/subscribe/news admin(29209): SSL_CIPHER_EXPORT: false admin(29209): CONTEXT_DOCUMENT_ROOT: /usr/lib/cgi-bin/ admin(29209): SERVER_SOFTWARE: Apache admin(29209): CONTEXT_PREFIX: /cgi-bin/ admin(29209): SSL_SERVER_A_KEY: rsaEncryption admin(29209): QUERY_STRING: admin(29209): SERVER_SIGNATURE: admin(29209): REQUEST_METHOD: POST admin(29209): PATH_INFO: /news admin(29209): SERVER_PROTOCOL: HTTP/1.1 admin(29209): SSL_SERVER_S_DN: CN=mail.example.com admin(29209): SSL_CIPHER: ECDHE-RSA-AES128-GCM-SHA256 admin(29209): SSL_SERVER_V_START: Apr 17 16:42:00 2016 GMT admin(29209): SSL_TLS_SNI: mail.example.com admin(29209): CONTENT_LENGTH: 106 admin(29209): SSL_CLIENT_VERIFY: NONE admin(29209): HTTP_USER_AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 admin(29209): HTTP_CONNECTION: keep-alive admin(29209): HTTP_COOKIE: PHPSESSID=... admin(29209): SERVER_NAME: mail.example.com admin(29209): REMOTE_ADDR: 192.0.2.1 admin(29209): SSL_CIPHER_ALGKEYSIZE: 128 admin(29209): SSL_SECURE_RENEG: true admin(29209): PATH_TRANSLATED: /srv/web/mail/news admin(29209): SSL_SERVER_I_DN_C: US admin(29209): SSL_COMPRESS_METHOD: NULL admin(29209): SSL_SERVER_M_VERSION: 3 admin(29209): SSL_SERVER_I_DN_O: Let's Encrypt admin(29209): SERVER_ADDR: 192.0.2.2 admin(29209): DOCUMENT_ROOT: /srv/web/mail admin(29209): SERVER_PORT: 443 admin(29209): SSL_VERSION_LIBRARY: OpenSSL/1.0.1f admin(29209): PYTHONPATH: /var/lib/mailman admin(29209): SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/subscribe admin(29209): SERVER_ADMIN: webmaster at example.com admin(29209): SSL_SESSION_RESUMED: Initial admin(29209): SSL_SERVER_M_SERIAL: ... admin(29209): SSL_SERVER_A_SIG: sha256WithRSAEncryption admin(29209): HTTP_DNT: 1 admin(29209): HTTP_HOST: mail.example.com admin(29209): SCRIPT_NAME: /cgi-bin/mailman/subscribe admin(29209): HTTPS: on admin(29209): HTTP_CACHE_CONTROL: max-age=0 admin(29209): REQUEST_URI: /cgi-bin/mailman/subscribe/news admin(29209): HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 admin(29209): SSL_SERVER_S_DN_CN: mail.example.com admin(29209): GATEWAY_INTERFACE: CGI/1.1 admin(29209): SSL_SERVER_I_DN_CN: Let's Encrypt Authority X3 admin(29209): REMOTE_PORT: 40456 admin(29209): HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5 admin(29209): REQUEST_SCHEME: https admin(29209): SSL_SERVER_V_END: Jul 16 16:42:00 2016 GMT admin(29209): CONTENT_TYPE: text/plain;charset=UTF-8 admin(29209): SSL_PROTOCOL: TLSv1.2 admin(29209): SSL_CIPHER_USEKEYSIZE: 128 admin(29209): HTTP_ACCEPT_ENCODING: gzip, deflate, br admin(29209): SSL_SERVER_I_DN: CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US ** Affects: mailman (Ubuntu) Importance: Undecided Status: New ** Project changed: mailman => mailman (Ubuntu) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602608 Title: mailman crash for subscription in webinterface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1602608/+subscriptions From mark at msapiro.net Wed Jul 13 13:10:43 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 17:10:43 -0000 Subject: [Bug 1602779] [NEW] Some German language templates are utf-8 encoded Message-ID: <20160713171043.14113.66799.malonedeb@soybean.canonical.com> Public bug reported: The templates/de files adminaddrchgack.txt masthead.txt nomoretoday.txt probe.txt refuse.txt subauth.txt are incorrectly encoded as utf-8 instead of iso-8859.1. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602779 Title: Some German language templates are utf-8 encoded To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602779/+subscriptions From 1602779 at bugs.launchpad.net Wed Jul 13 13:14:00 2016 From: 1602779 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 13 Jul 2016 17:14:00 -0000 Subject: [Bug 1602779] Re: Some German language templates are utf-8 encoded References: <20160713171043.14113.66799.malonedeb@soybean.canonical.com> Message-ID: <20160713171402.30253.79814.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602779 Title: Some German language templates are utf-8 encoded To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602779/+subscriptions From mark at msapiro.net Wed Jul 13 13:14:05 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 17:14:05 -0000 Subject: [Bug 1602779] Re: Some German language templates are utf-8 encoded References: <20160713171043.14113.66799.malonedeb@soybean.canonical.com> Message-ID: <20160713171406.18671.20417.launchpad@wampee.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602779 Title: Some German language templates are utf-8 encoded To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602779/+subscriptions From 1602608 at bugs.launchpad.net Wed Jul 13 16:23:04 2016 From: 1602608 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 13 Jul 2016 20:23:04 -0000 Subject: [Bug 1602608] [NEW] mailman crash for subscription in webinterface References: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Message-ID: <20160713202304.23484.60266.launchpad@gac.canonical.com> You have been subscribed to a public bug: A Traceback from mailman's logs for a subscription. The bug can be triggered with the following post-data: language='' Jul 11 20:29:34 2016 admin(29209): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(29209): [----- Mailman Version: 2.1.16 -----] admin(29209): [----- Traceback ------] admin(29209): Traceback (most recent call last): admin(29209): File "/var/lib/mailman/scripts/driver", line 117, in run_main admin(29209): main() admin(29209): File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 73, in main admin(29209): language = cgidata.getvalue('language') admin(29209): File "/usr/lib/python2.7/cgi.py", line 548, in getvalue admin(29209): if key in self: admin(29209): File "/usr/lib/python2.7/cgi.py", line 594, in __contains__ admin(29209): raise TypeError, "not indexable" admin(29209): TypeError: not indexable admin(29209): [----- Python Information -----] admin(29209): sys.version = 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] admin(29209): sys.executable = /usr/bin/python admin(29209): sys.prefix = /usr admin(29209): sys.exec_prefix = /usr admin(29209): sys.path = ['/var/lib/mailman/pythonlib', '/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(29209): sys.platform = linux2 admin(29209): [----- Environment Variables -----] admin(29209): SSL_VERSION_INTERFACE: mod_ssl/2.4.7 admin(29209): HTTP_REFERER: https://mail.example.com/cgi-bin/mailman/subscribe/news admin(29209): SSL_CIPHER_EXPORT: false admin(29209): CONTEXT_DOCUMENT_ROOT: /usr/lib/cgi-bin/ admin(29209): SERVER_SOFTWARE: Apache admin(29209): CONTEXT_PREFIX: /cgi-bin/ admin(29209): SSL_SERVER_A_KEY: rsaEncryption admin(29209): QUERY_STRING: admin(29209): SERVER_SIGNATURE: admin(29209): REQUEST_METHOD: POST admin(29209): PATH_INFO: /news admin(29209): SERVER_PROTOCOL: HTTP/1.1 admin(29209): SSL_SERVER_S_DN: CN=mail.example.com admin(29209): SSL_CIPHER: ECDHE-RSA-AES128-GCM-SHA256 admin(29209): SSL_SERVER_V_START: Apr 17 16:42:00 2016 GMT admin(29209): SSL_TLS_SNI: mail.example.com admin(29209): CONTENT_LENGTH: 106 admin(29209): SSL_CLIENT_VERIFY: NONE admin(29209): HTTP_USER_AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 admin(29209): HTTP_CONNECTION: keep-alive admin(29209): HTTP_COOKIE: PHPSESSID=... admin(29209): SERVER_NAME: mail.example.com admin(29209): REMOTE_ADDR: 192.0.2.1 admin(29209): SSL_CIPHER_ALGKEYSIZE: 128 admin(29209): SSL_SECURE_RENEG: true admin(29209): PATH_TRANSLATED: /srv/web/mail/news admin(29209): SSL_SERVER_I_DN_C: US admin(29209): SSL_COMPRESS_METHOD: NULL admin(29209): SSL_SERVER_M_VERSION: 3 admin(29209): SSL_SERVER_I_DN_O: Let's Encrypt admin(29209): SERVER_ADDR: 192.0.2.2 admin(29209): DOCUMENT_ROOT: /srv/web/mail admin(29209): SERVER_PORT: 443 admin(29209): SSL_VERSION_LIBRARY: OpenSSL/1.0.1f admin(29209): PYTHONPATH: /var/lib/mailman admin(29209): SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/subscribe admin(29209): SERVER_ADMIN: webmaster at example.com admin(29209): SSL_SESSION_RESUMED: Initial admin(29209): SSL_SERVER_M_SERIAL: ... admin(29209): SSL_SERVER_A_SIG: sha256WithRSAEncryption admin(29209): HTTP_DNT: 1 admin(29209): HTTP_HOST: mail.example.com admin(29209): SCRIPT_NAME: /cgi-bin/mailman/subscribe admin(29209): HTTPS: on admin(29209): HTTP_CACHE_CONTROL: max-age=0 admin(29209): REQUEST_URI: /cgi-bin/mailman/subscribe/news admin(29209): HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 admin(29209): SSL_SERVER_S_DN_CN: mail.example.com admin(29209): GATEWAY_INTERFACE: CGI/1.1 admin(29209): SSL_SERVER_I_DN_CN: Let's Encrypt Authority X3 admin(29209): REMOTE_PORT: 40456 admin(29209): HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5 admin(29209): REQUEST_SCHEME: https admin(29209): SSL_SERVER_V_END: Jul 16 16:42:00 2016 GMT admin(29209): CONTENT_TYPE: text/plain;charset=UTF-8 admin(29209): SSL_PROTOCOL: TLSv1.2 admin(29209): SSL_CIPHER_USEKEYSIZE: 128 admin(29209): HTTP_ACCEPT_ENCODING: gzip, deflate, br admin(29209): SSL_SERVER_I_DN: CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US ** Affects: mailman Importance: Undecided Assignee: Mark Sapiro (msapiro) Status: Incomplete -- mailman crash for subscription in webinterface https://bugs.launchpad.net/bugs/1602608 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Wed Jul 13 16:23:02 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 20:23:02 -0000 Subject: [Bug 1602608] Re: mailman crash for subscription in webinterface References: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Message-ID: <20160713202302.23484.59803.malone@gac.canonical.com> I see how this can occur if you have your own page that POSTs to the subscribe CGI with no post data or post data consisting of all blank values, but I don't see how it occurs with a post from the listinfo subscribe form. Can you explain exactly what the scenario is that triggers this error? ** Package changed: mailman (Ubuntu) => mailman ** Changed in: mailman Status: New => Incomplete ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602608 Title: mailman crash for subscription in webinterface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602608/+subscriptions From 1602608 at bugs.launchpad.net Thu Jul 14 03:45:26 2016 From: 1602608 at bugs.launchpad.net (Sebastian Wagner) Date: Thu, 14 Jul 2016 07:45:26 -0000 Subject: [Bug 1602608] Re: mailman crash for subscription in webinterface References: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Message-ID: <20160714074526.14144.8654.malone@soybean.canonical.com> Does it matter where the request comes from? Anyone can send post- requests to the mailman page (subscribers, bots, hackers etc) and mailman should not fail in any case IMHO. > Can you explain exactly what the scenario is that triggers this error? This is the minimal example I could find: curl https://mail.example.com/cgi-bin/mailman/subscribe/news -d "language='" -H "Content-Type: text/plain;charset=UTF-8" You can of course add as many other data as you want. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602608 Title: mailman crash for subscription in webinterface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602608/+subscriptions From 1602608 at bugs.launchpad.net Thu Jul 14 17:46:57 2016 From: 1602608 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 14 Jul 2016 21:46:57 -0000 Subject: [Bug 1602608] Re: mailman crash for subscription in webinterface References: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Message-ID: <20160714214659.14112.77770.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602608 Title: mailman crash for subscription in webinterface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602608/+subscriptions From mark at msapiro.net Thu Jul 14 18:01:49 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Jul 2016 22:01:49 -0000 Subject: [Bug 1602608] Re: mailman crash for subscription in webinterface References: <20160713101125.14797.9509.malonedeb@soybean.canonical.com> Message-ID: <20160714220150.18204.31482.malone@wampee.canonical.com> Actually, the problem is both simpler and more wide spread than you report. The underlying issue is the Content-Type: text/plain header sent with the POST request. It doesn't matter what if anything the data is. 'language' is a red herring. It only appears in the tracebacks from the subscribe CGI because that is what's being requested in the subscribe CGI's first call to the getvalue method of the cgi.FieldStorage instance. The way the Python cgi module works, the FieldStorage instance has different properties depending on the Content-Type: header in the POST. If the content type is application/x-www-form-urlencoded as would be the case in a normal POST from a browser the FieldStorage instance is a dictionary-like mapping of key, value pairs that can be retrieved via the getvalue method. If the content type is text/plain, the FieldStorage instance just has a string value and the getvalue method throws TypeError. This actually affects every one of Mailman's CGIs, not just subscribe, and without knowing how the error was triggered, I probably wouldn't have determined the cause. In the spirit of not throwing uncaught exceptions, even when people, web crawlers, etc. unwittingly or maliciously craft defective requests, I have committed http://bazaar.launchpad.net/~mailman- coders/mailman/2.1/revision/1663 to return an error document with a 400 status for such requests. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: Incomplete => Fix Committed ** Changed in: mailman Milestone: None => 2.1.23 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1602608 Title: mailman crash for subscription in webinterface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602608/+subscriptions From mark at msapiro.net Thu Jul 14 22:59:02 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 02:59:02 -0000 Subject: [Bug 558155] Re: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. References: <20100408090656.1687.59831.launchpad@loganberry.canonical.com> Message-ID: <20160715025902.31039.1621.malone@chaenomeles.canonical.com> I have committed another change at http://bazaar.launchpad.net/~mailman- coders/mailman/2.1/revision/1664 which does the conversion to unicode and the unicode normalization, so everything in this patch has now been committed, albeit in a somewhat different way. Refer to the NEWS item in rev 1664 for more details. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558155 Title: i18n: Header Filter Rules (& fix) - rules don't match if header characters aren't representable in cset of list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558155/+subscriptions From abletec at gmail.com Mon Jul 18 19:00:14 2016 From: abletec at gmail.com (Jackie McBride) Date: Mon, 18 Jul 2016 23:00:14 -0000 Subject: [Bug 1604181] [NEW] mangled reply-to: header when a reply-to: header exists Message-ID: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Public bug reported: I'm trying to set my list up such that folks reply to the list, but can also view a poster's email in order to reply personally if they desire. I've set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When someone has a reply-to: address set, I get 3 addresses--the list address, the poster's address, & a mangled address that consists of the poster's address prior to the @ sign & the fqdn of the list following it. So if my list address is mylist at mysub.domain.org, & my poster w/the reply-to: setting's email is poster at somedomain.com, I'd get addresses as: mylist at mysub.domain.org poster at mysub.domain.org (which there is no such address) & poster at somedomain.com. I'm running Mailman 2.1.16. Has this perchance been fixed in subsequent versions? ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Mon Jul 18 21:13:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 01:13:46 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719011347.16427.78766.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Mon Jul 18 21:40:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 01:40:13 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719014013.22617.13290.malone@chaenomeles.canonical.com> When you say you get 3 addresses, do you mean all 3 addresses are in Reply-To: or do you mean that when you 'reply' in your MUA (and what is that?) the reply is addressed to those 3 addresses. It sounds as if you may have set from_is_list to Munge From for this list., but I'm not sure. I've never seen anything like poster at mysub.domain.org being put in Reply-To: by Mailman. Possibly the original post had Reply-Tp: poster (i.e. poster without a domain and your MTA rewrote the unqualified address by adding your domain. If from_is_list to Munge From, a message from the list with first_strip_reply_to = Yes, reply_goes_to_list = This list and Mailman 2.1.16 that was sent To: list at example.com From: bob at example.net should have headers From: bob via list Reply-To: , plus anything else in Bob's original Reply-To: The current release is similar except will be added to Cc: rather than Reply-To: There have been ongoing changes in this area in almost every release since 2.1.16, but without understanding more about exactly what you are seeing, I can't say if this is something that's been 'fixed' or a bug or intended behavior. See http://bazaar.launchpad.net/~mailman- coders/mailman/2.1/view/head:/NEWS for all the changes since 2.1.16. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 00:06:12 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 04:06:12 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719040612.4126.34923.malone@wampee.canonical.com> Hi, Mark, & thanks for your reply. My header is set to munge from, & the reply-to: is set to 'this list. I use PostFix,. I'm sorry for the spam munging of the addresses--I know it makes them kind of hard to figure out--but a couple of these addresses are real, & I'd prefer my list not be bombarded by spambots if it can be helped. The list address is: midimag dash ex at mailman dot midimag dash xt dot org The poster's address is: info at accessibilitytraining dot co dot uk He has a reply to: header set in his email client, which is set to his address. In addition to the list address & his address, the address that appears in the email header as well is: Accessibility at mailman dot midimag dash xt dot org which is a thoroughly bogus address. Got any ideas? Quite frankly, I'm baffled. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 00:20:12 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 04:20:12 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719042012.855.27717.malone@gac.canonical.com> Hi, Mark, & thanks for your reply. My header is set to 'munge from' & reply-to: is set to 'this list'. I'm using Postfix. I apologize in advance--I'm going to munge these addresses, because some of them are real. The scenario is as follows. The list address is midimag dash ex at mailman dot midimag dash xt dot org The poster's address is info at accessibilitytraining dot co dot uk He has a reply-to: header set in his email client w/the above co.uk address. When he replies to the list, the reply-to: header contains the list address &, instead of his email address, there's an address Accessibility at mailman dot midimag dash xt dot org instead of his actual email address. Also, the a in accessibility is capitalized, but that's not the way his email address appears. I hope you have some ideas, cuz I'm totally baffled. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 02:12:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 06:12:15 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719061215.9091.11112.malone@soybean.canonical.com> I note you are telling me two different things in Comments #2 and #3. Comment #2 says In addition to the list address & his address, the address that appears in the email header as well is: Accessibility at mailman dot midimag dash xt dot org which is a thoroughly bogus address. which says there are 3 addresses in (I assume) Reply-To: of the post from Mailman. Comment #3 says the reply-to: header contains the list address &, instead of his email address, there's an address Accessibility at mailman dot midimag dash xt dot org instead of his actual email address. which says there are only 2 addresses in Reply-To: of the post from Mailman. I'd like to see the raw headers of the mail from the list. If you don't want to post them here, you can mail them to mark at msapiro.net. Here's an example of full headers of a mail to a list: >From mark at msapiro.net Mon Jul 18 22:57:00 2016 Date: Mon, 18 Jul 2016 22:57:00 -0700 From: Mark Sapiro To: list1 at msapiro.net Subject: Test mail Message-ID: <20160719055700.GA10944 at msapiro.net> Reply-To: mark at msapiro.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Status: RO Content-Length: 147 Lines: 4 And the headers of the mail from the list >From list1-bounces+mark=msapiro.net at msapiro.net Mon Jul 18 22:57:14 2016 Return-Path: X-Original-To: mark at msapiro.net Delivered-To: mark at msapiro.net Received: from [127.0.1.1] (localhost [127.0.0.1]) by msapiro.net (Postfix) with ESMTP id E6AC234028D for ; Mon, 18 Jul 2016 22:57:10 -0700 (PDT) X-Original-To: list1 at msapiro.net Delivered-To: list1 at msapiro.net Received: by msapiro.net (Postfix, from userid 1000) id DEC133402D7; Mon, 18 Jul 2016 22:57:00 -0700 (PDT) Date: Mon, 18 Jul 2016 22:57:00 -0700 To: list1 at msapiro.net Message-ID: <20160719055700.GA10944 at msapiro.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-msapiro-MailScanner: Found to be clean X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0, required 6, autolearn=not spam, NO_RELAYS -0.00, URIBL_BLOCKED 0.00) X-Spam-Status: No Subject: [List1] Test mail X-BeenThere: list1 at msapiro.net X-Mailman-Version: 2.1.22 Precedence: list List-Id: My List one List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Mark Sapiro via List1 Reply-To: mark at msapiro.net, My List one Cc: Mark Sapiro Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: list1-bounces+mark=msapiro.net at msapiro.net Sender: List1 X-msapiro-MailScanner-ID: E6AC234028D.AFCF3 X-msapiro-MailScanner: Found to be clean X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-0.999, required 6, autolearn=not spam, ALL_TRUSTED -1.00, URIBL_BLOCKED 0.00) X-msapiro-MailScanner-From: list1-bounces+mark=msapiro.net at msapiro.net X-Spam-Status: No Status: O Content-Length: 275 Lines: 9 This is Mailman 2.1.22+, but I think the only difference from 2.1.16 is the original From: would be added to Reply-To: instead of Cc: except the address is already there because of the original Reply-To: and first_strip_reply_to = No so it wouldn't be added a second time. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 11:12:18 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 15:12:18 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719061215.9091.11112.malone@soybean.canonical.com> Message-ID: Hi, Mark. Thanks for the private email. I promise I won't abuse it. Here is the header. Note particularly the reply-to:Reply-To: midimag-ex at mailman.midimag-xt.org, Accessibility at mailman.midimag-xt.org, Phil Muir This was a direct copy-paste, & it's weird that the Accessibility at mailman.midimag-xt.org address contains an uppercase letter. Do you have any idea what is occurring? https://mail.google.com/mail/u/0/h/rzsloxyya12s/?th=156001d8e1dccb49v=om Delivered-To: abletec at gmail.com Received: by 10.37.22.2 with SMTP id 2csp1271120ybw; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) X-Received: by 10.66.144.200 with SMTP id so8mr10577521pab.94.1468880752243; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) Return-Path: Received: from mailman.midimag-xt.org (mailman.midimag-xt.org. [107.170.199.86]) by mx.google.com with ESMTP id ro7si28933425pab.251.2016.07.18.15.25.51; Mon, 18 Jul 2016 15:25:52 -0700 (PDT) Received-SPF: pass (google.com: domain of midimag-ex-bounces at mailman.midimag-xt.org designates 107.170.199.86 as permitted sender) client-ip=107.170.199.86; Authentication-Results: mx.google.com; dkim=fail header.i=@mailman.midimag-xt.org; spf=pass (google.com: domain of midimag-ex-bounces at mailman.midimag-xt.org designates 107.170.199.86 as permitted sender) smtp.mailfrom=midimag-ex-bounces at mailman.midimag-xt.org Received: from mailman.midimag-xt.org (localhost [127.0.0.1]) by mailman.midimag-xt.org (Postfix) with ESMTP id 14E1412403B; Mon, 18 Jul 2016 15:25:51 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailman.midimag-xt.org; s=mailman; t=1468880751; bh=LWN5eghNrqijU7VjrNrEV2Wej3+KA03rqZ77M+Cv4+Y=; h=In-Reply-To:References:Date:To:Subject:From:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Sender:From; b=Qb2gdCszjPsfJU8z/Qy48U+sXvRUY6RetxvxhAlCa73r0XRKsH6S97bdXA+//He6w B9lYmU7pHWP5W32Mserx2bMFzrNYh1HzFFsJhvwzwaNtpDqe3ovPjsInb7/YKcQ3xI De0WpTiAar0u/+qEKajU3ZuwSSv2nfPR6aH5O0js= X-Original-To: midimag-ex at mailman.midimag-xt.org Delivered-To: midimag-ex at mailman.midimag-xt.org Received: from outbound44.dataflame.com (outbound44.dataflame.com [91.103.219.62]) by mailman.midimag-xt.org (Postfix) with ESMTPS id 726BF12402A for ; Mon, 18 Jul 2016 15:25:40 -0700 (MST) X-Virus-Scanned: by SpamTitan at dataflame.co.uk Received: from [2.216.153.142] (port=60675 helo=android-6c0a3f0408928b1b) by primrose.dataflame.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1bPGyg-002oKs-Lc for midimag-ex at mailman.midimag-xt.org; Mon, 18 Jul 2016 23:25:32 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Date: Mon, 18 Jul 2016 23:25:31 +0100 To: midimag-ex at mailman.midimag-xt.org Message-ID: X-OutGoing-Spam-Status: No, score=-2.6 X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Subject: Re: [Midimag-ex] 1 last experiment X-BeenThere: midimag-ex at mailman.midimag-xt.org X-Mailman-Version: 2.1.16 Precedence: list From: Phil Muir via Midimag-ex Reply-To: midimag-ex at mailman.midimag-xt.org, Accessibility at mailman.midimag-xt.org, Phil Muir List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: midimag-ex-bounces at mailman.midimag-xt.org Sender: "Midimag-ex" R290IHRoaXMgdGhyZWFkIGhlcmUgZnJvbSB0aGUgbGlzdC4gIEhpdCByZXBseS4KCk9uIDE4IEp1 bHkgMjAxNiAyMzoxNjo1MyBCU1QsIEtlaXRoIEhpbnRvbiB2aWEgTWlkaW1hZy1leCA8bWlkaW1h Zy1leEBtYWlsbWFuLm1pZGltYWcteHQub3JnPiB3cm90ZToKPk9rYXksIHJlc3BvbmRpbmcgdG8g dGhpcyB0byBzZWUgd2hhdCB5b3UgYWxsIGdldC4KPgo+SGF2ZSBmdW4sCj5LZWl0aAo+Cj5Qcy4K PkkgZGlkIG5vdCBoaXQgcmVwbHkgdG8gYWxsLCBzbyBsZXQncyBzZSBpZiBldmVyeWJvZHkgc2Vl cyB0aGlzIHJhbmRvbQo+bWVzc2FnZSBibG9iIHRoaW5neS4KPgo+T24gNy8xOC8xNiwgSmFja2ll IE1jQnJpZGUgdmlhIE1pZGltYWctZXgKPjxtaWRpbWFnLWV4QG1haWxtYW4ubWlkaW1hZy14dC5v cmc+IHdyb3RlOgo+PiBXZWxsIGxldCdzIHNlZSB3aGF0IHRoaXMgZG9lcy4KPj4KPj4gLS0KPj4g SmFja2llIE1jQnJpZGUKPj4gV2Vic2l0ZSBIb3N0aW5nLCBSZXBhaXIsICYgRGV2ZWxvcG1lbnQK Pj4gQXV0aG9yIG9mIHRoZSBVcGNvbWluZyBCb29rCj4+ICJNeSBTaXRlJ3MgQmVlbiBIYWNrZWQs IE5vdyB3aGF0PzogQSBHdWlkZSB0byBQcmV2ZW50aW5nIGFuZCBGaXhpbmcgYQo+PiBDb21wcm9t aXNlZCBXZWJzaXRlIgo+PiB3d3cuYnJpZ2h0ZXItdmlzaW9uLmNvbSBXaGVyZSBWaXNpb25hcmll cyAmIFRlY2hub2xvZ3kgVW5pdGUgZm9yIEdvb2QKPj4gX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18KPj4gTWlkaW1hZy1leCBtYWlsaW5nIGxpc3QKPj4gTWlk aW1hZy1leEBtYWlsbWFuLm1pZGltYWcteHQub3JnCj4+IGh0dHA6Ly9tYWlsbWFuLm1pZGltYWct eHQub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taWRpbWFnLWV4Cj4+Cj5fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+TWlkaW1hZy1leCBtYWlsaW5n IGxpc3QKPk1pZGltYWctZXhAbWFpbG1hbi5taWRpbWFnLXh0Lm9yZwo+aHR0cDovL21haWxtYW4u bWlkaW1hZy14dC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pZGltYWctZXgKCi0tIApS ZWdhcmRzLApBY2Nlc3NpYmlsaXR5IFRyYWluaW5nClRlbGVwaG9uZTogVUsgKzQ0LTE3NDctMjI4 LTQ1OQpNb2JpbGU6IFVLICs0NC03OTY4LTEzNi0yNDYKRS1tYWlsOgppbmZvQGFjY2Vzc2liaWxp dHl0cmFpbmluZy5jby51awpVUkw6Cmh0dHA6Ly93d3cuYWNjZXNzaWJpbGl0eXRyYWluaW5nLmNv LnVrCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pZGlt YWctZXggbWFpbGluZyBsaXN0Ck1pZGltYWctZXhAbWFpbG1hbi5taWRpbWFnLXh0Lm9yZwpodHRw Oi8vbWFpbG1hbi5taWRpbWFnLXh0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlkaW1h Zy1leAo= On 7/18/16, Mark Sapiro wrote: > I note you are telling me two different things in Comments #2 and #3. > > Comment #2 says > In addition to the list address & his address, the address that appears in > the email header as well is: > Accessibility at mailman dot midimag dash xt dot org > which is a thoroughly bogus address. > > which says there are 3 addresses in (I assume) Reply-To: of the post > from Mailman. > > Comment #3 says > the reply-to: header contains the list address &, instead of his email > address, there's an address Accessibility at mailman dot midimag dash xt dot > org instead of his actual email address. > > which says there are only 2 addresses in Reply-To: of the post from > Mailman. > > I'd like to see the raw headers of the mail from the list. If you don't > want to post them here, you can mail them to mark at msapiro.net. > > Here's an example of full headers of a mail to a list: > > >From mark at msapiro.net Mon Jul 18 22:57:00 2016 > Date: Mon, 18 Jul 2016 22:57:00 -0700 > From: Mark Sapiro > To: list1 at msapiro.net > Subject: Test mail > Message-ID: <20160719055700.GA10944 at msapiro.net> > Reply-To: mark at msapiro.net > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.5.24 (2015-08-30) > Status: RO > Content-Length: 147 > Lines: 4 > > > And the headers of the mail from the list > > >From list1-bounces+mark=msapiro.net at msapiro.net Mon Jul 18 22:57:14 2016 > Return-Path: > X-Original-To: mark at msapiro.net > Delivered-To: mark at msapiro.net > Received: from [127.0.1.1] (localhost [127.0.0.1]) > by msapiro.net (Postfix) with ESMTP id E6AC234028D > for ; Mon, 18 Jul 2016 22:57:10 -0700 (PDT) > X-Original-To: list1 at msapiro.net > Delivered-To: list1 at msapiro.net > Received: by msapiro.net (Postfix, from userid 1000) > id DEC133402D7; Mon, 18 Jul 2016 22:57:00 -0700 (PDT) > Date: Mon, 18 Jul 2016 22:57:00 -0700 > To: list1 at msapiro.net > Message-ID: <20160719055700.GA10944 at msapiro.net> > MIME-Version: 1.0 > Content-Disposition: inline > User-Agent: Mutt/1.5.24 (2015-08-30) > X-msapiro-MailScanner: Found to be clean > X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, > score=0, > required 6, autolearn=not spam, > NO_RELAYS -0.00, URIBL_BLOCKED 0.00) > X-Spam-Status: No > Subject: [List1] Test mail > X-BeenThere: list1 at msapiro.net > X-Mailman-Version: 2.1.22 > Precedence: list > List-Id: My List one > List-Unsubscribe: , > > List-Archive: > List-Post: > List-Help: > List-Subscribe: , > > From: Mark Sapiro via List1 > Reply-To: mark at msapiro.net, My List one > Cc: Mark Sapiro > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Errors-To: list1-bounces+mark=msapiro.net at msapiro.net > Sender: List1 > X-msapiro-MailScanner-ID: E6AC234028D.AFCF3 > X-msapiro-MailScanner: Found to be clean > X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, > score=-0.999, required 6, autolearn=not spam, ALL_TRUSTED -1.00, > URIBL_BLOCKED 0.00) > X-msapiro-MailScanner-From: list1-bounces+mark=msapiro.net at msapiro.net > X-Spam-Status: No > Status: O > Content-Length: 275 > Lines: 9 > > This is Mailman 2.1.22+, but I think the only difference from 2.1.16 is > the original From: would be added to Reply-To: instead of Cc: except the > address is already there because of the original Reply-To: and > first_strip_reply_to = No so it wouldn't be added a second time. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1604181 > > Title: > mangled reply-to: header when a reply-to: header exists > > Status in GNU Mailman: > Incomplete > > Bug description: > I'm trying to set my list up such that folks reply to the list, but can > also view a poster's email in order to reply personally if they desire. I've > set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When > someone has a reply-to: address set, I get 3 addresses--the list address, > the poster's address, & a mangled address that consists of the poster's > address prior to the @ sign & the fqdn of the list following it. So if my > list address is mylist at mysub.domain.org, & my poster w/the reply-to: > setting's email is poster at somedomain.com, I'd get addresses as: > mylist at mysub.domain.org > poster at mysub.domain.org (which there is no such address) & > poster at somedomain.com. > > I'm running Mailman 2.1.16. Has this perchance been fixed in > subsequent versions? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 13:44:07 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 17:44:07 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719174407.820.88436.malone@gac.canonical.com> Does this occur only with posts from this one person? Do you know what's in his original Reply-To: (ask him to Bcc: you on his next post)? Have you tried first_strip_reply_to = Yes? Is this a distribution package Mailman (if so, which one)? If Mailman is installed from source, I recommend upgrading to 2.1.22 or later. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 13:57:20 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 17:57:20 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719174407.820.88436.malone@gac.canonical.com> Message-ID: Hi, Mark. "Have you tried first_strip_reply_to = Yes?" Yes. But what it also does in most cases is to strip the poster's address, which is not what I want. "Is this a distribution package Mailman (if so, which one)?" Ubuntu. I'll ask him to bcc me & send it along. I'm going to test to see if I can duplicate this w/other reply-to: settings. On 7/19/16, Mark Sapiro wrote: > Does this occur only with posts from this one person? Do you know what's > in his original Reply-To: (ask him to Bcc: you on his next post)? > > Have you tried first_strip_reply_to = Yes? > > Is this a distribution package Mailman (if so, which one)? > > If Mailman is installed from source, I recommend upgrading to 2.1.22 or > later. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1604181 > > Title: > mangled reply-to: header when a reply-to: header exists > > Status in GNU Mailman: > Incomplete > > Bug description: > I'm trying to set my list up such that folks reply to the list, but can > also view a poster's email in order to reply personally if they desire. I've > set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When > someone has a reply-to: address set, I get 3 addresses--the list address, > the poster's address, & a mangled address that consists of the poster's > address prior to the @ sign & the fqdn of the list following it. So if my > list address is mylist at mysub.domain.org, & my poster w/the reply-to: > setting's email is poster at somedomain.com, I'd get addresses as: > mylist at mysub.domain.org > poster at mysub.domain.org (which there is no such address) & > poster at somedomain.com. > > I'm running Mailman 2.1.16. Has this perchance been fixed in > subsequent versions? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 14:42:28 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 18:42:28 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719174407.820.88436.malone@gac.canonical.com> Message-ID: Mark, if he just emails me, the header looks like: Delivered-To: abletec at gmail.com Received: by 10.37.22.2 with SMTP id 2csp1699972ybw; Tue, 19 Jul 2016 11:05:45 -0700 (PDT) X-Received: by 10.28.138.18 with SMTP id m18mr6127346wmd.63.1468951545029; Tue, 19 Jul 2016 11:05:45 -0700 (PDT) Return-Path: Received: from outbound37.dataflame.com (outbound37.dataflame.com. [91.103.219.55]) by mx.google.com with ESMTPS id c184si21512657wmd.123.2016.07.19.11.05.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jul 2016 11:05:44 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning info at accessibilitytraining.co.uk does not designate 91.103.219.55 as permitted sender) client-ip=91.103.219.55; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning info at accessibilitytraining.co.uk does not designate 91.103.219.55 as permitted sender) smtp.mailfrom=info at accessibilitytraining.co.uk X-Virus-Scanned: by SpamTitan at dataflame.co.uk Received: from [2.216.153.142] (port=65112 helo=phils15inchmac) by primrose.dataflame.com with esmtpa (Exim 4.87) (envelope-from ) id 1bPZOg-000i3A-OZ for abletec at gmail.com; Tue, 19 Jul 2016 19:05:37 +0100 Reply-To: From: "Phil Muir" To: "'Jackie McBride'" References: In-Reply-To: Subject: RE: mailman & midimag Date: Tue, 19 Jul 2016 19:05:35 +0100 Organization: P J Muir Productions Message-ID: <90AAC4C3777C4759866B77EAC830392C at phils15inchmac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AdHh55cmAQuwq+ZrRRCmrWPI1V6WCgAAGE0g X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609 X-OutGoing-Spam-Status: No, score=-2.9 On 7/19/16, Jackie McBride wrote: > Hi, Mark. > "Have you tried first_strip_reply_to = Yes?" > Yes. But what it also does in most cases is to strip the poster's > address, which is not what I want. > > "Is this a distribution package Mailman (if so, which one)?" > Ubuntu. > > I'll ask him to bcc me & send it along. I'm going to test to see if I > can duplicate this w/other reply-to: settings. > > On 7/19/16, Mark Sapiro wrote: >> Does this occur only with posts from this one person? Do you know what's >> in his original Reply-To: (ask him to Bcc: you on his next post)? >> >> Have you tried first_strip_reply_to = Yes? >> >> Is this a distribution package Mailman (if so, which one)? >> >> If Mailman is installed from source, I recommend upgrading to 2.1.22 or >> later. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1604181 >> >> Title: >> mangled reply-to: header when a reply-to: header exists >> >> Status in GNU Mailman: >> Incomplete >> >> Bug description: >> I'm trying to set my list up such that folks reply to the list, but can >> also view a poster's email in order to reply personally if they desire. >> I've >> set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. >> When >> someone has a reply-to: address set, I get 3 addresses--the list address, >> the poster's address, & a mangled address that consists of the poster's >> address prior to the @ sign & the fqdn of the list following it. So if my >> list address is mylist at mysub.domain.org, & my poster w/the reply-to: >> setting's email is poster at somedomain.com, I'd get addresses as: >> mylist at mysub.domain.org >> poster at mysub.domain.org (which there is no such address) & >> poster at somedomain.com. >> >> I'm running Mailman 2.1.16. Has this perchance been fixed in >> subsequent versions? >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions >> > > > -- > Jackie McBride > Website Hosting, Repair, & Development > Author of the Upcoming Book > "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a > Compromised Website" > www.brighter-vision.com Where Visionaries & Technology Unite for Good > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 15:21:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 19:21:12 -0000 Subject: [Bug 1604544] [NEW] Letter links on admin Membership List rendered as Unicodes. Message-ID: <20160719192112.8736.9447.malonedeb@soybean.canonical.com> Public bug reported: Following a search which returned more than admin_member_chunksize hits, the letter links on the admin Membership List are Unicodes and renderd as u'http... which doesn't work. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604544 Title: Letter links on admin Membership List rendered as Unicodes. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604544/+subscriptions From 1604544 at bugs.launchpad.net Tue Jul 19 15:28:31 2016 From: 1604544 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 19 Jul 2016 19:28:31 -0000 Subject: [Bug 1604544] Re: Letter links on admin Membership List rendered as Unicodes. References: <20160719192112.8736.9447.malonedeb@soybean.canonical.com> Message-ID: <20160719192839.26040.9240.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604544 Title: Letter links on admin Membership List rendered as Unicodes. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604544/+subscriptions From mark at msapiro.net Tue Jul 19 15:28:41 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 19:28:41 -0000 Subject: [Bug 1604544] Re: Letter links on admin Membership List rendered as Unicodes. References: <20160719192112.8736.9447.malonedeb@soybean.canonical.com> Message-ID: <20160719192841.9194.5838.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604544 Title: Letter links on admin Membership List rendered as Unicodes. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604544/+subscriptions From mark at msapiro.net Tue Jul 19 16:07:07 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 20:07:07 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719200707.785.86331.malone@gac.canonical.com> Again, is this only with posts from this one person or from everyone? In Mailman 2.1.16 with from_is_list = Mung From, first_strip_reply_to = Yes and reply_to_list = This list, the posters original From: should be added to Reply-To: (in the latest versions, it will be added to Cc: in this case). And is this a distro's Mailman package, and if so, which? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 16:52:57 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 20:52:57 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719200707.785.86331.malone@gac.canonical.com> Message-ID: So far, I think it's this 1 person's, Mark, but I really need to do some more thorough checking. As mentioned in the last post, it's a Ubuntu distribution of Mailman. On 7/19/16, Mark Sapiro wrote: > Again, is this only with posts from this one person or from everyone? > > In Mailman 2.1.16 with from_is_list = Mung From, first_strip_reply_to = > Yes and reply_to_list = This list, the posters original From: should be > added to Reply-To: (in the latest versions, it will be added to Cc: in > this case). > > And is this a distro's Mailman package, and if so, which? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1604181 > > Title: > mangled reply-to: header when a reply-to: header exists > > Status in GNU Mailman: > Incomplete > > Bug description: > I'm trying to set my list up such that folks reply to the list, but can > also view a poster's email in order to reply personally if they desire. I've > set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When > someone has a reply-to: address set, I get 3 addresses--the list address, > the poster's address, & a mangled address that consists of the poster's > address prior to the @ sign & the fqdn of the list following it. So if my > list address is mylist at mysub.domain.org, & my poster w/the reply-to: > setting's email is poster at somedomain.com, I'd get addresses as: > mylist at mysub.domain.org > poster at mysub.domain.org (which there is no such address) & > poster at somedomain.com. > > I'm running Mailman 2.1.16. Has this perchance been fixed in > subsequent versions? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 17:26:18 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 21:26:18 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719200707.785.86331.malone@gac.canonical.com> Message-ID: Hey Mark, I may have found something. It appears that when this poster sends email via Outlook, everything is fine. But when he uses k-9 on his Android, it's not. I've asked him to post again w/his phone to confirm this. That could prove interesting--& perhaps even helpful. I'll get back. On 7/19/16, Jackie McBride wrote: > So far, I think it's this 1 person's, Mark, but I really need to do > some more thorough checking. As mentioned in the last post, it's a > Ubuntu distribution of Mailman. > > On 7/19/16, Mark Sapiro wrote: >> Again, is this only with posts from this one person or from everyone? >> >> In Mailman 2.1.16 with from_is_list = Mung From, first_strip_reply_to = >> Yes and reply_to_list = This list, the posters original From: should be >> added to Reply-To: (in the latest versions, it will be added to Cc: in >> this case). >> >> And is this a distro's Mailman package, and if so, which? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1604181 >> >> Title: >> mangled reply-to: header when a reply-to: header exists >> >> Status in GNU Mailman: >> Incomplete >> >> Bug description: >> I'm trying to set my list up such that folks reply to the list, but can >> also view a poster's email in order to reply personally if they desire. >> I've >> set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. >> When >> someone has a reply-to: address set, I get 3 addresses--the list address, >> the poster's address, & a mangled address that consists of the poster's >> address prior to the @ sign & the fqdn of the list following it. So if my >> list address is mylist at mysub.domain.org, & my poster w/the reply-to: >> setting's email is poster at somedomain.com, I'd get addresses as: >> mylist at mysub.domain.org >> poster at mysub.domain.org (which there is no such address) & >> poster at somedomain.com. >> >> I'm running Mailman 2.1.16. Has this perchance been fixed in >> subsequent versions? >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions >> > > > -- > Jackie McBride > Website Hosting, Repair, & Development > Author of the Upcoming Book > "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a > Compromised Website" > www.brighter-vision.com Where Visionaries & Technology Unite for Good > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 17:33:59 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 21:33:59 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719213400.5393.62797.malone@wampee.canonical.com> Sorry, I missed your Ubuntu comment the first time. I don't see any patches at http://archive.ubuntu.com/ubuntu/pool/main/m/mailman/mailman_2.1.16-2ubuntu0.1.debian.tar.gz that would affect this. I can try to duplicate this with the 2.1.16 base, but I have to build it so it won't be right away. However, I still think it might be something in his original Reply-To: which I haven't yet seen. The message you posted at https://bugs.launchpad.net/mailman/+bug/1604181/comments/8 was sent from "X-Mailer: Microsoft Office Outlook 11" and his list post at https://bugs.launchpad.net/mailman/+bug/1604181/comments/5 was sent from "User-Agent: K-9 Mail for Android" What does his Reply-To: look like in a message from his phone? If it looks something like Reply-To: Accessibility, ... that could explain this. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 17:41:26 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 21:41:26 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719214126.3571.55171.malone@chaenomeles.canonical.com> I hadn't seen https://bugs.launchpad.net/mailman/+bug/1604181/comments/11 when I wrote https://bugs.launchpad.net/mailman/+bug/1604181/comments/12, but I'm now certain it's something in the Reply-To: header from the phone. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From abletec at gmail.com Tue Jul 19 18:06:06 2016 From: abletec at gmail.com (Jackie McBride) Date: Tue, 19 Jul 2016 22:06:06 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> <20160719214126.3571.55171.malone@chaenomeles.canonical.com> Message-ID: Mark, this list member lives in the UK, & it's late there now, but hopefully he'll do as I request & post w/his phone to the list at his earliest convenience. I do suspect it is something w/the phone reply-to: header, though I can't say I understand precisely what at this point. Seems as though we arrived at the same conclusion independently lol. Talk about a head-banger! Kind of interesting, though. I'm not familiar w/k-9--is this a user agent you've seen? It'll be interesting to see if this is an isolated event due to a misconfigured reply-to: header or if there are others who are experiencing anything remotely similar. I had looked at Ubuntu & couldn't find anything more recent than the version I already have. But I'm not entirely certain that a later version would address something like this anyway. I'd have installed it from source if I thought it would've, truth be told. On 7/19/16, Mark Sapiro wrote: > I hadn't seen > https://bugs.launchpad.net/mailman/+bug/1604181/comments/11 when I wrote > https://bugs.launchpad.net/mailman/+bug/1604181/comments/12, but I'm now > certain it's something in the Reply-To: header from the phone. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1604181 > > Title: > mangled reply-to: header when a reply-to: header exists > > Status in GNU Mailman: > Incomplete > > Bug description: > I'm trying to set my list up such that folks reply to the list, but can > also view a poster's email in order to reply personally if they desire. I've > set 'Reply-to:' to list, & I didn't strip the first 'reply-to:' header. When > someone has a reply-to: address set, I get 3 addresses--the list address, > the poster's address, & a mangled address that consists of the poster's > address prior to the @ sign & the fqdn of the list following it. So if my > list address is mylist at mysub.domain.org, & my poster w/the reply-to: > setting's email is poster at somedomain.com, I'd get addresses as: > mylist at mysub.domain.org > poster at mysub.domain.org (which there is no such address) & > poster at somedomain.com. > > I'm running Mailman 2.1.16. Has this perchance been fixed in > subsequent versions? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions > -- Jackie McBride Website Hosting, Repair, & Development Author of the Upcoming Book "My Site's Been Hacked, Now what?: A Guide to Preventing and Fixing a Compromised Website" www.brighter-vision.com Where Visionaries & Technology Unite for Good -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions From mark at msapiro.net Tue Jul 19 18:31:58 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 22:31:58 -0000 Subject: [Bug 1604181] Re: mangled reply-to: header when a reply-to: header exists References: <20160718230014.15359.94712.malonedeb@gac.canonical.com> Message-ID: <20160719223158.3869.56037.malone@chaenomeles.canonical.com> What we want to see is an email from his phone, not one from the list sant from his phone. I.e., we want to see the original Reply-To: from the phone. I actually use K-9 Mail on my Android phone. I think it is excellent as mobile device MUAs go. But K-9 isn't the issue. The issue is what he has set as the Reply-To: address in the account he's sending from. For Ubuntu packages, see http://packages.ubuntu.com/search?keywords=mailman. Also see about upgrading from source, but I don't think that will change this behavior although 2.1.18+ will allow you to Munge From only from domains with DMARC policy. Setting first_strip_reply_to = Yes will probably fix this for you and will still add the original From: to Reply-To:. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1604181 Title: mangled reply-to: header when a reply-to: header exists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1604181/+subscriptions