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

[MM3-users] Re: List description as sender

by Mark Sapiro

On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: > It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. And it is only the From: in posts delivered to the list members if the list is anonymous. Otherwise the From: is that from the original post to the list or possibly a mumged version thereof in the case of DMARC mitigations. I think your choices are: 1) Don't configure the list as anonymous. 2) Make the list's Description what you think is appropriate for the display name part of the From: header. 3) Modify mailman/handlers/cleanse.py to use something else in the From: header of anonymized posts. 4) Submit an RFE at <https://gitlab.com/mailman/mailman/issues/new> asking for the solution you want and possibly a merge request implementing it. 5) Live with it as is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/29/20 2:00 PM, Massimo Zappalà wrote: > Hi Mark, > i've created the it templates from en. > I have make a merge request from the link that you posted before, but i was rejected because I am non a member of the project. How can I make a merge request? You need to fork Mailman Core <https://gitlab.com/mailman/mailman> into your own GitLab project space, make and commit your changes there and then submit a merge request to merge your branch back into the master. If that's what you did, I don't know what the issue is, but you can send the templates to me directly. > Anyway, I copied the files in the path indicated by you but the translated emails arrive only if I am an list administrator. Is this perhaps a permissions issue. The Mailmanuser needs to be able to read them. See <https://gitlab.com/mailman/mailman/-/issues/745> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > But I am trying to delete a list on an urgent basis. Because of which I am > getting the above said errors. I tried to delete > through the interface, through curl command and through "mailman shell" but > nothing led me to a > positive result. Is there any work around to delete the list ? What have you tried in Mailman shell? This should do it. $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> getUtility(IListManager).delete(m) >>> commit() So should just $ mailman remove list.example.com What happens if you do those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/10/21 2:32 PM, Duane Raymond wrote: > > As for the potential bug in hyperkitty, I have been referencing the hyperkitty version of this thread as I was working the problem, and while I faintly remember seeing the loop in the email on my phone, when I was referencing the hyperkitty version of your email it was not there - even when expanding the quoted text....perhaps you see the same thing via hyperkitty? Essentially it removed part of the message that was intended to be seen. That's a known issue with the HyperKitty that is installed at mailman3.org and python.org due to the patch for markdown rendering <https://gitlab.com/mailman/hyperkitty/-/merge_requests/160>. This patch is superceded by <https://gitlab.com/mailman/hyperkitty/-/merge_requests/324>, but I haven't gotten around to trying that yet. If you look at the message view at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, you'll see the missing part -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Strange issue with bounce processing

by Mark Sapiro

On 9/12/23 10:16 AM, Dan Caballero wrote: > I have a somewhat related question. > > I monitor the Mailman runner processes via cron and restart based on a drop in the number of processes. As a result I've noticed that the bounces runner process becomes defunct at varying times. For example, the cron job restarted the Mailman processes early this morning and I can see the bounce runner process is currently defunct (Z state). It appears to have become defunct after about 3 hours of CPU time. There are some relevant issues on this, some of which are fixed. See https://gitlab.com/mailman/mailman/-/issues/?state=all&search=bounce%20runn… When the runner dies, the master watcher should restart it. See https://gitlab.com/mailman/mailman/-/issues/898, fixed (maybe) by https://gitlab.com/mailman/mailman/-/merge_requests/1094 which will be in Mailman 3.3.9. However, this doesn't address why it dies in the first place. You might find some info about the death in syslog. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 10/29/23 01:57, Odhiambo Washington wrote: > > Consequent upon this django-allauth issue and the previous issue > with psycopg2, how likely is it that new MM3 installations will suffer the > effects? As noted in other replies, the django-allauth issue has been fixed in 0.58.1 and should not be an issue for anyone installing Mailman at this point. Regarding your psycopg2 issue, it was apparently fixed when you upgraded from 2.8.6 to 2.9.9. Presumably you got 2.8.6 with the command ``` (venv)$ pip install wheel mailman psycopg2-binary\<2.9 ``` shown at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… Perhaps you didn't read the following paragraph which says in part "Currently Django>=2.2,<3.1 requires psycopg2-binary<2.9. See this issue. Later versions of Django will work with psycopg2-binary 2.9.x." That said, I don't know why there was an issue with psycopg2-binary=2.8.6. I have an installation with that version and it works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/4/21 2:24 PM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to start the mailman server on a mac according to the instructions given on the website as shown - What web site? A URL to the instructions you followed would help. > $(py3) git clone git@gitlab.com:mailman/mailman.git > $(py3) cd mailman > $(py3) python setup.py develop Rather than 'python setup.py develop', do 'pip install -e ./' > $(py3) mailman start > $(py3) cd .. > > But I run into the following problem - > > Starting Mailman's master runner > Generating MTA alias maps > /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > > Can anyone help me out with this? There should be a `master` in the same bin/ directory as `mailman` which is probably not '/usr/local/opt/python(a)3.9/bin/' What does `mailman info` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/4/21 2:09 AM, David Partain via Mailman-users wrote: >> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: >>> 1. Am I correct in assuming that I can just use my favorite editor >>> (vi) to remove the offending characters from the file? > >> No. The file is a Python pickle and you can't edit it. You would need >> to get the message and the metadata from the pickle (you could at > least >> view it with the `mailman qfile` command), edit the message and then >> re-pickle the message and metadata. > > And, in my impatience, I tried it before receiving your response and > now I seem to have done silliness in my database :( New error in > mailman-web.log: > > AttributeError: 'NoneType' object has no attribute 'subject' > > Sigh. Stupid me. If you have suggestions on fixing that... Is the file you edited still in the spool directory or is it gone? If it's still there, move it aside and see if that fixes the issue. What is the full traceback accompanying that AttributeError message from the log? > Right now, my plan is simply to remove the first message in the queue > (since I assume it'll be the "broken" one) and it'll just not be in > the archive. Life's hard. Even if I unpack 'em to edit, I'll find > mail in, for example, in base64, and I'm not going to fix the mail > by decoding, editing, re-encoding, ... Nope. Examine the messages in the spool with `mailman qfile var/archive/hyperkitty/spool/filename`. If any files throw exceptions on that, move them aside. Also, if you can see any 4-byte utf-8 encodings in the output, move that aside as well. Then see what happens after that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:59 AM, Darren Smith wrote: > OK - next issue...here's the warning that I'm receiving when I run that: > > /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date > received a naive datetime (2018-04-03 07:51:25) while time zone support is > active. > RuntimeWarning) That warning comes from dateutil.parsedate, and I think it's just a warning and shouldn't affect processing. > I'm not sure that anything else occurred. The indexing took 2 seconds, and > there have been tens of thousands of emails imported since the last index. > Thoughts? I'm unsure about what happens when 'runjob update_index' runs after an import. I.e. it adds messages added since the last run, but is this based on when the message was added or on some date in the added message, so if the added messages are old, do they get indexed by 'runjob update_index'. You could easily check by doing some searches that should find them and see if they're found. -- 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: Setting moderation_action when approving a message from a non-member fails

by Mark Sapiro

On 6/13/23 05:15, Tom Smyth wrote: > > When a message is held due to it being from a non-member, I notice that > Mailman creates a non-member record for the sender automatically. This is > great! > > But if I try to set their moderation action while approving the message in > Postorius, I get: > > Failed to set moderation action: xxx(a)gmail.com is not a member address of > xxx(a)xxx.org > > Is this expected? I would like to be able to set the moderation action for > the non-member that has already been created. > > I am on Postorius v1.3.2. This is <https://gitlab.com/mailman/postorius/-/issues/448>, apparently filed by you, fixed in Postorius 1.3.4 by <https://gitlab.com/mailman/postorius/-/merge_requests/558>. Until you upgrade, you will have to set the non-member's moderation action separately from handling the held message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Search results for query "sapiro"