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

[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, 6 months

[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

3 years, 4 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by Mark Sapiro

On 8/18/25 12:01 PM, Wikinaut wrote: > [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.av-huette.de/settings/message_acceptance > Full error stack (redacted) see https://dpaste.com/CEFXPNP67.txt > > Internal Server Error: /mailman3/lists/test2.*****/settings/message_acceptance > > As far as I remember, I removed every member of that test2 list. I think, my bug report could be of interest to fix a (probably) lurking bug. Everything works here, but last week I had this error That error results from having two users with email addresses that differ only in case. This could occur with older versions of Django-allauth. There is a script at https://www.msapiro.net/scripts/UC_fix to fix this and one at https://www.msapiro.net/scripts/Mult_primary to fix a possible side effect of the other. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

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

by Mark Sapiro

On 9/19/19 2:22 AM, Manos Pitsidianakis wrote: > Thank you again for your reply, Mark. > > Στις 2019-09-18 21:53, Mark Sapiro έγραψε: >> What are these entries? > > > I have these log entries, are these what you were referring to? > > https://paste.debian.net/hidden/37d863f6/ No. You referred to "shunted" mails. I assumed that mail was winding up in the shunt queue, but this is apparently not the case. >> 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. > > I think the problematic e-mails that cause this issue are stuck on the > outgoing queue. Right now there are 2 pck files and one .bak in > var/queue/out changing filenames repeatedly. What is happening is you have three messages in the out queue which are problematic. When Mailman or the out runner is restarted, for some reason the attempt to send these triggers the "Cannot connect to SMTP server" issue which is logged only once. Here's what happens: The oldest .pck file in the out queue gets picked up by the out runner and renamed to a .bak. The runner attempts to send the message and gets a socket.error exception so it requeues the message to be tried again. This removes the .bak and creates a new .pck. This process continues so the files keep getting renamed. I suggest you stop Mailman, and move the three files out of the out/ queue, and then restart Mailman. This should stop the out runner from "spinning" on these messages. Then you can examine the files with Mailman's 'bin/mailman qfile' command and see if you can identify something in the recipients list or other metadata that might be causing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > All the mentioned versions of all the components are taken from my > currently running system only in which I am facing the issue. Did you run $ cd mailmanclient $ python setup.py develop as it says at <https://docs.mailman3.org/en/latest/devsetup.html> I do not understand exactly how the various components are installed in your installation, so I can't tell you what is wrong, but the version of mailmanclient that gives you the AttributeError: 'MailingList' object has no attribute 'get_requests_count' is not the one whose latest commit is ### Mailmanclient Version ### commit aaa529808e2d61899f90509da4ea802a70d2c8ff Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master'* Use GHCR for the CI image* See merge request mailman/mailmanclient!130* because that one won't have this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Migrating archives from mailman2 to mailman3 with attachments

by Mark Sapiro

On 2/28/22 10:14, bob B via Mailman-users wrote: > So I see the process for migrating an archive from mailman2 to mailman3 > https://docs.mailman3.org/en/latest/migration.html.................. i.e python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > but does the migration handle attachments?? attachments are in > ..../archives/private/foo-list/attachments. You do not need those files. They were extracted from the messages in the foo-list.mbox file which is all you need. > I am migrating to a new server and my plan is to follow these steps but copy the config.pck. and .mbox files to the new server and import them, but then it looks like I need to copy the attachment directory? if so how do I import the attachments to mailman3? No. You do not need the attachments directory or any of the .html files. All this information is in the .mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/16/22 12:56, Quanah Gibson-Mount wrote: > > Thanks for the response. Unfortunately I'm currently stuck with the > junk shipped by Debian. Yet another reason to move to a standalone > install and avoid their broken packages. In the mean time, you can handle these issues via REST or via `mailman shell`. For example: ``` $ mailman shell -l list(a)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. >>> pendings = getUtility(IPendings) >>> sub_mgr = ISubscriptionManager(m) >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'user(a)example.com': ... continue ... sub_mgr.confirm(token) ... >>> commit() ``` The above will find the pending confirmation for user(a)example.com on the list list(a)example.com and confirm it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: About the sender of the mailing list receiving an auto-reply email

by Mark Sapiro

On 1/12/23 17:48, 朱超 wrote: > Hi, When I use the mailing list to send emails, I receive an automatic reply email, Is there a better way to block similar automatic reply emails? From: Tom I don't really understand what you mean by a better way to block similar automatic reply emails. If you are saying you get an acknowledgement of your post, there are two possibilities. Each user has an `Acknowledge posts` setting. If you are getting that, you can turn it off. Also, lists have an `Autorespond postings` setting to send an autoresponse to posts from anyone. If that's what you are seeing, a list owner can turn that off too. If you mean you don't want to receive a copy of your own post from the list, there's also a user setting to `Receive own postings` which you can turn off. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Mark Sapiro

On 6/24/23 9:44 PM, Ken Alker wrote: > How did you join the split thread? using HyperKitty's "Reattach this thread". > The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too? That was my mistake. There were two choices. I could open the reply thread containing only https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and reattach it to the original message thread now containing several messages or vice versa. I did the latter, i.e. with the result you see with the reply out of sequence at the top. Had I done the former the reply would have been out of sequence at the bottom. This would have been better, but it's now too late to change it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mark Sapiro

Stephen J. Turnbull wrote: > This is almost certainly due to a recent policy change at Gmail, where > they are requiring "from alignment"[1] but only for Gmail authors. > That is, Gmail does not publish a p=reject policy, but the effect on > Gmail recipients (only) is the same as if they did -- they all bounce > every time a Gmail user posts. Another way to prevent gmail users from having delivery disabled and being unsubscribed because of this is to enable VERP probes (set `verp_probes: yes` in the [mta] section of mailman.cfg). Since the probes are not sent from a gmail user, they won't bounce and the user's delivery won't be disabled. This is not a fix for the issue as the gmail users will still not receive posts from other gmail users, but they will receive other posts and won't get their delivery disabled by bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Search results for query "sapiro"