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

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/25/20 12:12 AM, Alan So wrote: > Mark Sapiro wrote: > >> In the absence of an issue at >> https://gitlab.com/mailman/mailman/-/issues, >> probably never. <hint> > > Is that anyone with a gitlab account can file an issue? If it is appropriate, I can try to file one. Yes, anyone with a gitlab account can file an issue. >> Have you asked Microsoft to fix Outlook to not create these defective >> messages? That's the real solution. > > Yes and I agree. My colleague has actually done so but it is probably not yet escalated to the appropriate tier of support. Here is the comment of my colleague: "I can submit this problem to Microsoft. However, it may take a long time to fix it or not even important enough to be fixed." At least you're trying and that's a good thing even if they don't fix it. -- 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: Welcome message template errors

by Mark Sapiro

On 4/27/24 08:32, Mark Sapiro wrote: > > More strangeness. I've now done a test on one of the production servers > I manage, and there is no error. Both the production server and the > development server are running the identical Mailman code installed in a > venv, they both have the same version of urllib3 and similar Python > versions, 3.9.16 on the development server and 3.9.10 on the production > server. Both servers are running under Ubuntu 20.04.6. The only other > difference I see is on the production server everything runs as user > mailman and on the development server everything runs as user mark. I have now reinstalled Mailman from scratch on the development server in a Python 3.12.3 venv using the heads of the gitlab branches and getting the current versions of all the dependencies and this installation gets no error. So while I still have an older venv that produces this error, I cannot duplicate the error in a new install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/18/19 2:29 PM, Manos Pitsidianakis wrote: > > Στις 2019-09-18 19:12, Mark Sapiro έγραψε: >> Is only one list affected, and is it all messages from this list or only >> some? > > Just two messages from this certain list. Subsequent messages and other > activity seems to work properly There should be entries in the mailman.log for each shunted message listing the exception with a traceback and the fact that the message was shunted. What are these entries? > Well there is no connection to postfix at all when the runner starts and > the "Cannot connect to SMTP server" log shows up. Otherwise I'd have > seen something in the postfix logs or tcpdumps in localhost. The "Cannot connect to SMTP server" log message should not occur immediately on startup unless there are queued messages. That log message should only occur on an attempt to actually send a message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/15/22 10:20, Mark Sapiro wrote: > On 9/15/22 01:22, Kimmo L wrote: >> Hi Mark! >> >> I forwarded the same shunted file to you as well, which i sent to Steve. > > > Thanks. I got it and will look further. This is very strange. The message object in the shunted pickle is missing several important headers. In particular, there is no Message-ID: and no MIME-Version: and no Content-Type: while the body contains subpart headers like ``` Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ``` and ``` Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ``` but no boundaries. This apparently confuses the Python email package so that the get_payload() method returns a list of strings rather than a list of message objects. The question is how did this happen. What does ``` mailman conf -k anonymous_list_keep_headers ``` show, and what is the content of mailman/handlers/cleanse.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 11:44, Odhiambo Washington wrote: > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Nothing in those releases per se would affect this. This is Django and >> django-allauth. Perhaps when you updated the Mailman packages, you also >> updated these dependencies. >> > > Which dependencies would those be? Django and django-allauth. > When I upgraded, the command I ran was: > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > mailman-hyperkitty django-mailman3 Do you mean --force-reinstall? pip has no --force option. I *think* --force-reinstall will upgrade dependencies. Depending on your pip version, --upgrade alone may or may not upgrade dependences. Older versions of pip will, but newer versions, at least without --force-upgrade require --upgrade-strategy eager to update dependencies. > And how do I find out what is suppressing the logging for the social > accounts? That's a django-allauth question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Heads Up - Downtime

by Mark Sapiro

On 5/19/23 18:48, Mark Sapiro wrote: > > The move was completed earlier today. Everything is up, but there are > two things that may affect mail delivery. At least some outgoing mail is > not being DKIM signed. I'm puzzled as to why. And, it's a new server > that doesn't have a reputation yet. Everything seems to be functioning well at this point. I fixed the DKIM signing issue and mail is being signed. We are still seeing a few bounces and I'm monitoring that. The last few posts were sent to 323 regular subscribers, six of whom bounced. We were listed in Spamhaus PBL, but that listing was removed yesterday. Still 3 yahoo.com addresses are bounced for being listed in Spamhaus. Maybe Yahoo will refresh its cache at some point. Also, 1 msn.com and 2 outlook.com addresses are bounced for our network being on their block list. This may be due to the Spamhaus listing or maybe not. I'll continue to monitor this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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 Mark Sapiro

On 4/25/23 6:59 AM, Mark Sapiro wrote: > On 4/25/23 3:02 AM, Andrew Hodgson wrote: >> >> You may find this script useful: >> https://www.msapiro.net/scripts/clean_users.py > > I will modify the script to enable deleting Mailman users with no > memberships even if they aren't Django users and post here when it's done. 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. The difference is when deleting Mailman users it will now delete Mailman users with no memberships whether or not there is a corresponding Django user. -- 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

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 4:08 PM, Brian Carpenter wrote: > On 2/16/21 6:13 PM, Mark Sapiro wrote: >> On 2/16/21 2:28 PM, Brian Carpenter wrote: >>> The beginning of my OP stated I was using Mailman 3.3.3. >> Then please get me a copy of the complete raw digest message so I can >> try to find the underlying issue. >> > Not sure how to do that. Do you mean have the list member forward their > garbled digest message to me? Is that what you need? Oops. Sorry for the prior content free reply. Yes the list member needs to forward the garbled digest to you to resend to me or to me directly, but if it's forwarded, it must be forwarded as an attachment, not inline, because inline forwarding will lose the headers I need to see. Alternatively, the list member can view the message source (how to do that depends on the MUA), select it in its entirety, copy and paste it into a message to you or me -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 10:02, Odhiambo Washington wrote: > On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Thus, putting >> ``` >> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' >> ``` >> in your settings will maintain compatibility with pre 3.2 versions and >> existing tables and this is the correct thing to do. >> > > Thank you very much for the clarification. Also note that for the past year or so, the files postorius/example_project/settings.py:, mailman_web/settings/base.py, hyperkitty/example_project/settings.py and mailman-suite/mailman-suite_project/settings.py have all contained DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' and if you follow https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… you will import mailman_web/settings/base.py and pick this up from mailman-web 0.0.6 and both https://wiki.list.org/x/17892066 and https://wiki.list.org/x/17891998 suggest that your settings.py should be a copy of the mailman-suite settings.py file but with DEBUG = False, the implication being that when that file changes, yours should too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 11:57 AM, Mark Dadgar wrote: > On Jun 9, 2020, at 11:34 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> ./mm3-admin: line 6: 702058 Killed django-admin $@ >>> >>> Now what? >> >> >> Run it as user `list`. > > > Same. It appears that the reference to line 6 is line 6 of your mm3-admin file which is the `django-admin $@` command. So that command is being killed by the OS for some reason, probably out of memory. Try this instead. import pytz import datetime start = datetime.datetime(2020, 1, 1).replace(tzinfo=pytz.UTC) end = datetime.datetime(2020, 2, 1).replace(tzinfo=pytz.UTC) # These are examples. The args are year, month, day. # Pick dates for start and end that overlap the start of this issue. from hyperkitty.models import Email emails = Email.objects.filter(date__range=(start,end)) for email in emails: if email.content.find('\u200b'*5) >= 0: print('Found in ml {}, hash {}'.format( email.mailinglist.name, email.message_id_hash)) This will make a much smaller query set than all the emails and should work. -- 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

Search results for query "sapiro"