Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > It has nothing to do with the ssl certificate. In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-) > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs. Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it. -Ralph

6 years, 8 months

[MM3-users] Re: Receiving 8bit-clean mail

by Stephen J. Turnbull

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. Based on the symptoms, I'm guessing this means the SMTPUTF8 extension. Mailman is not prepared for this as far as I know. That is, Mailman expects that the headers will be ASCII, possibly MIME-encoded. I'm guessing the problem is that either the host MTA or Mailman's LMTP server doesn't handle SMTPUTF8 negotiation correctly, but I do not have time to analyze for some days. Mark Sapiro writes: > It works for me. I created this message Your message doesn't have UTF-8 in the *header* as far as I can see. Steve

6 years, 1 month

[MM3-users] Re: ARC issues

by David Krantz

On Mon, Mar 2, 2020 at 7:07 PM Mark Sapiro <mark(a)msapiro.net> wrote: > I've been trying openarc > <https://github.com/trusteddomainproject/OpenARC> with Postfix as well > as Mailman's ARC. I still haven't got it all worked out - I have a > fairly convoluted mail flow with the possibility of messages being > altered before they ever get to Mailman. I do not have that problem. The ARC implementation in Mailman accepts incoming DKIM signatures etc. so that is not a problem. > There is an issue with Mailman's ARC signing in a supporting library. > See <https://github.com/ValiMail/authentication-headers/issues/5>. I have not had that issue yet, I do not think any of my users format their name that way. Good to know, though. Cheers. // David

5 years, 9 months

[MM3-users] Re: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

2 years, 9 months

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Andrew Hodgson

Mark Sapiro wrote: >The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no >memberships are deleted. Thanks, I ran this script and it did delete a load of Mailman users, I got output similar to this: <User "" (47600399411039288509336192576257642185) at 0x7fb17a6a35e0> deleted from Mailman Why aren't we seeing the actual address here? Thanks. Andrew.

2 years, 7 months

[MM3-users] Re: Upgrade

by Darren Smith

Further debugging - using the python3.6 from the virtual environment where mailman is running, it looks like it is trying to use utf-8: >>> import locale >>> import codecs >>> print(locale.getpreferredencoding()) UTF-8 >>> print(codecs.lookup(locale.getpreferredencoding()).name) utf-8 >>> Thoughts? On Mon, Apr 16, 2018 at 11:29 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > By the way, in reading the URL in the error, I attempted to set the LANG > and LC_ALL to en_US.utf8 (as was found in the error) but it still does not > work. > > > > On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton(a)gmail.com > > wrote: > >> Nice...spoke too soon. >> >> Mailman info works, but when attempting to start mailman I'm now getting >> this: >> >> Traceback (most recent call last): >> File "/opt/mailman3/conda/bin/mailman", line 11, in <module> >> sys.exit(main()) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 722, in __call__ >> return self.main(*args, **kwargs) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 676, in main >> _verify_python3_env() >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", >> line 118, in _verify_python3_env >> 'for mitigation steps.' + extra) >> RuntimeError: Click will abort further execution because Python 3 was >> configured to use ASCII as encoding for the environment. Consult >> http://click.pocoo.org/python3/for mitigation steps. >> >> This system lists a couple of UTF-8 supporting locales that >> you can pick from. The following suitable locales where >> discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion >> others) >> >> -Darren >> >> On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith < >> silas.crutherton(a)gmail.com> wrote: >> >>> Boy howdy did that work... >>> >>> Thanks! >>> >>> >>> On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>>> On 04/16/2018 10:12 AM, Darren Smith wrote: >>>> >>>> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >>>> engine/strategies.py", >>>> > line 160, in create >>>> > engineclass.__name__)) >>>> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to >>>> create_engine(), >>>> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please >>>> check that >>>> > the keyword arguments are appropriate for this combination of >>>> components." >>>> > >>>> > Anyone able to point me where to go to look for a solution for this? >>>> >>>> >>>> You need to update SQLAlchemy to >= 1.2 for this, but there is another >>>> issue that requires at least 1.2.3 (current is 1.2.6) >>>> >>>> >>>> -- >>>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >>>> San Francisco Bay Area, California better use your sense - B. Dylan >>>> _______________________________________________ >>>> Mailman-users mailing list >>>> mailman-users(a)mailman3.org >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>> >>> >>> >> >

7 years, 7 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Williams, Peter B

Hi Mark, Thanks for the help with this! Other list members will also see the e-mail as coming from user(a)invalid.domain<mailto:user@invalid.domain>. I will continue testing the other scenarios and will reply back as soon as possible. Thanks again for the help with this and have a nice day! Peter On Mon, Sep 21, 2020 at 9:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: On 9/21/20 10:49 AM, peterbw(a)gmail.com<mailto:peterbw@gmail.com> wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, "Williams, Peter" <peters_real_address(a)example.com<mailto:peters_real_address@example.com>> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org<mailto:listserv@lists.test.org>. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org<mailto:listserv@lists.test.org>; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com<mailto:test_user@gmail.com> cc: other_user(a)gmail.com<mailto:other_user@gmail.com>; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> and other_user(a)gmail.com<mailto:other_user@gmail.com> receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

[MM3-users] Re: customized welcome message

by Nils

On 12/7/23 18:17, Mark Sapiro wrote: > These messages are sent with `Content-Type: text/plain`. Any html > included in a template will be rendered as plain text. I.e., you can't > include html in templates. I didn't try to include html. It completely ignored the template I've created and sent the html source of the parent domain. Which seems totally random to me. > I see no URI setting in Postorius Settings > Automatic Responses. What > Postorius version is this? Any local mods? It's Postorius Version 1.2.4 installed through the mailman3-web package for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screenshot_20231207_214025.png Replaced multipart/alternative part with first alternative.

2 years

[MM3-users] Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, When I was seeing this, new lists weren't showing in HyperKitty. I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now. Was this working for you in the past? If so, did you do any updates recently? Derek Lambert On 2/6/19, 1:50 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Mark Sapiro wrote: > This looks like <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_mailman_hyp…> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

6 years, 10 months

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Peter Adebahr

On 7/18/20 7:46 PM, Mark Sapiro wrote: > On 7/18/20 9:30 AM, Dave Clements wrote: >> Hi all, >> >> I have just noticed a big jump in the number of emails going out with >> "***UNCHECKED***" added to the subject line. > > > This does not come from Mailman. Some milter or other process in your > MTA or elsewhere in the delivery chain is adding this to the Subject: > Hi Dave, I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf: # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; # Hope it helps :) Best regards, Peter

5 years, 4 months

Search results for query "sapiro"