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

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/11/24 23:33, Markus Grandpré wrote: > Dear Mr. Sapiro, > > on our test system we noticed the problem that after importing a mailing > list archive from a Mailman system v2.1 into a Mailman system v3.3.8, > e-mails are no longer distributed via this mailing list. E-mails that > are written to the list find their way into the archive, but they are > not sent to any member of the list. > > Before the archive was imported, writing an e-mail to the list and > distributing this e-mail via the list was not a problem. Unfortunately, > we cannot find any indication of this issue in the log of the mailman > system v3.3.8. Please help us to further analyze and solve this problem, > as we are planning to import 188 archives into our new productive > mailman system v3.3.8 during the next months. Nothing in HyperKitty should affect Mail delivery from the list. The symptom you see could result in a file in Mailman's mailman/templates/lists/<THIS.LISTS.ID>/<LC>/ directory not being readable by the Mailman user. Check ownership and permissions on everything in var/templates/ See the latter part of the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Note that if this is the issue, something other than hyperkitty_import did it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Auth question

by Mark Sapiro

On 04/09/2017 12:23 PM, David Krantz wrote: > > Now everything works for me except > the archiver. There I get strange errors where it requires > authentication. I _have_ set MAILMAN_ARCHIVER_KEY (in production.py) > and api_key in mailman_hyperkitty.conf to the same value within single > quotes. This is probably something extremely silly that my jetlagged > brain cannot see. In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in production.py or wherever, you have set MAILMAN_ARCHIVER_KEY = 'arch_secret' in mailman_hyperkitty.conf you set [general] ... api_key: arch_secret No quotes around the api_key value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 02:05 PM, Rafael Mora wrote: > > (env2) [mailman@localhost mailman-suite_project]$ python2 manage.py > runserver > Performing system checks... > > System check identified no issues (0 silenced). > July 21, 2017 - 20:50:29 > Django version 1.11.3, using settings 'settings' > Starting development server at http://127.0.0.1:8000/ > Quit the server with CONTROL-C. And did you try to go to http://127.0.0.1:8000/ or http://localhost:8000/ from a browser on that machine? If you're truing to access it from another machine, you need to do something like python2 manage.py runserver 192.168.1.42:8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Help request, almost got it going, but ....

by Mark Sapiro

On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: > > Seemingly, at some point in the deep dungeons of the source code the > "Acceptable aliases" Text-Box is not interpreted correctly. > > Specifically, at the start it contains the string > > [] See <https://gitlab.com/mailman/postorius/issues/58>. In order to set things on this page, you need to clear the Acceptable aliases box before submitting changes. You can't actually set Acceptable aliases via Postorius until this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Weird recipient

by Mark Sapiro

On 9/5/19 3:10 AM, Andrew Bernard wrote: > Both before and after upgrading tonight, my lists send out bizarre recipients that I cannot understand. It usually happens at the end of the distribution to other valid recipients. > > Sep 5 10:05:54 www postfix/smtp[3344]: A5DF9FA14E: to=<0101016d00e302ec-4db56da5-fd69-4b5e-9327-292c55e13ea8-000000(a)us-west-2.amazonses.com>, relay=email-smtp.us-west-2.amazonaws.com[52.36.120.66]:587, delay=2.4, delays=0/0/2.2/0.22, dsn=5.0.0, status=bounced (host email-smtp.us-west-2.amazonaws.com[52.36.120.66] said: 501 Invalid MAIL FROM address provided (in reply to MAIL FROM command)) What are the other mail log entries for queue id A5DF9FA14E ? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: email command join - problem

by Mark Sapiro

On 5/28/21 5:34 AM, sky.x--- via Mailman-users wrote: > > @Peter, hmm interesting, im used Kopano webmail and message format is set to plain/text, also when i open bcc copy of raw message it looks as plain/text. I will test another client at the night hours. The QP encoding probably occurs because you have non-ascii in the message body - perhaps in a signature? If you view the raw message source of the Bcc, what do you see? In particular is there a ``` Content-Transfer-Encoding: quoted-printable ``` header? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 1/18/24 05:36, samuel.d.darwin(a)gmail.com wrote: > > However our latest plan as of this moment is to revert back to a one-server implementation. mailman-core and mailman-web will be on the same machine. Thus, the enhancement is not critical. It still seems "theoretically" useful to implement the fix, unless the documentation states "it is recommended that core and web should be on the same machine" or similar. See the fourth paragraph at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Hyperkitty stuck files

by Mark Sapiro

On 7/10/24 6:55 AM, zoltan(a)circle-interactive.co.uk wrote: > > Can this maybe be added to the installation guide? > https://docs.mailman3.org/en/latest/install/virtualenv.html That guide is for an installation using PostgreSQL. We do mention the OPTIONS setting for MySQL in multiple places. E.g., https://gitlab.com/mailman/mailman-suite/-/blame/master/mailman-suite_proje… https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… https://gitlab.com/mailman/mailman-web/-/blame/master/mailman_web/settings/… However, I just added a comment to https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… about this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: Changing display name with "mailman withlist"

by Mark Sapiro

On 7/5/17 12:29 AM, Mark Ziranski wrote: > > When executing the script as written in the manual, I get the following error: > > (venv-3.5) [root@localhost mailman]# mailman withlist -r change example(a)example.org 'new display name' > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: new display name This is a known bug <https://gitlab.com/mailman/mailman/issues/319>. I will work on a fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: footer message

by Mark Sapiro

On 08/28/2018 06:46 PM, Abhijith PA via Mailman-users wrote: > Hello. > > Is there any way to enable footer for some lists at the same time > disable for lists. I maintain an mailman3 instance and some of the lists > in it need the footer message well some not. You can make list specific templates for list:member:regular:footer and/or list:member:digest:footer. If the template is empty, no footer will be added. See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> and <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Search results for query "sapiro"