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

[MM3-users] Re: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Stefan Bauer

Dear Mark, thank you for your time. After patching your script according to https://github.com/maxking/docker-mailman/issues/729#issuecomment-2447542238 It fails with /opt/mailman/venv/data# /usr/local/bin/UC_fix /opt/mailman/venv/data/mailman3web.db Traceback (most recent call last): File "/usr/local/bin/UC_fix", line 77, in <module> c.execute("delete from account_emailaddress where email = %s;", sqlite3.OperationalError: near "%": syntax error for reference: 67 for id, emails in d.items(): 68 ems = find(emails) 69 if ems: 70 em1, em2 = ems 71 if em1.lower() == em1: 72 c.execute("delete from account_emailaddress where email = %s;", 73 [em2]) 74 c.execute("""update account_emailaddress set "primary" = 't' 75 where email = %s;""", [em1]) 76 elif em2.lower() == em2: 77 c.execute("delete from account_emailaddress where email = %s;", 78 [em1]) 79 c.execute("""update account_emailaddress set "primary" = 't' 80 where email = %s;""", [em2]) 81 else: 82 print(f'No LC email for {ems}') However the sql connection itself works, and the select also reports addresses: sqlite> select email, user_id from account_emailaddress; ... John.Doe(a)my.domain|85 john.doe(a)my.domain|85 ..... Mike.Doe(a)my.domain|96 mike.doe(a)my.domain|96 .... Is there something wrong on my side? Thank you. Stefan Am Mo., 3. März 2025 um 18:40 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 3/3/25 07:52, Stefan Bauer via Mailman-users wrote: > > > > trying to update mailman3 to lastest version, we fail during > > > > mailman-web migrate with: > > > > Operations to perform: > > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, > > django_q, hyperkitty, postorius, sessions, sites, socialaccount > > Running migrations: > > Applying account.0006_emailaddress_lower...Traceback (most recent call > > last): > > File > > > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", > > line 89, in _execute > > return self.cursor.execute(sql, params) > > File > > > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", > > line 328, in execute > > return super().execute(query, params) > > sqlite3.IntegrityError: UNIQUE constraint failed: > account_emailaddress.email > > > This issue is due to changes in Django allauth to prevent creating > multiple addresses differing only in case. The problem is if you have > such multiple addresses in your account_emailaddress table, this > migration fails. There is a script at > https://www.msapiro.net/scripts/UC_fix that will fix this. You may need > to adjust the shebang and replace psycopg2 with sqlite3. > > See https://github.com/pennersr/django-allauth/issues/3019 perhaps > starting at > > https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… > > > We found a workaround to fake the migration with > > > > migrate --fake > > You should fix the issue with the DB and run the migrations. > > > Could this be some duplicate users with same mail-address? > > This is not related to Mailman users. It is Django users. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com >

1 year, 5 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote: > How about "user that installed Mailman" or "user that Mailman's runners > run as"? I installed it as root. From "man useradd" in Linux: -r, --system Create a system account. System users will be created with no aging information in /etc/shadow, and their numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the creation of groups). Note that useradd will not create a home directory for such an user, regardless of the default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options if you want a home directory for a system account to be created. Pierre -- lo ponse be lo mruli ku po'o cu ga'ezga roda lo ka dinko

8 years, 9 months

[MM3-users] Re: Starting from scratch

by Benjamin Ragheb

On Tue, Apr 10, 2018, at 12:14 AM, Mark Sapiro wrote: > If you are comfortable with 2), I think that's the better option. After > PyCon in May when we release 3.2 and the rest of the suite, you should > be able to install everything with pip and have it work. I'm not sure > what the issues are now with a pip install. Thanks, Mark. It wasn't clear to me by poking around how stable/unstable the master branches were, but if you think they should be stable enough for a hobby server, that's good enough for me. If I get things working and I'm feeling bold enough to contribute back to the documentation, are there guidelines? The Contributor Guide covers the technical stuff... should I just submit a merge request in GitLab? -- Ben

8 years, 4 months

[MM3-users] Re: mailman start - can't open file

by Mark Dale

Thanks for the pointer Mark. I've edited mailman.cfg as follows and all is well. [paths.local] var_dir: /var/tmp/mailman bin_dir: /usr/local/bin log_dir: $var_dir/logs lock_dir: $var_dir/locks data_dir: $var_dir/data cache_dir: $var_dir/cache etc_dir: $var_dir/etc messages_dir: $var_dir/messages archive_dir: $var_dir/archives template_dir: $var_dir/templates pid_file: $var_dir/master.pid lock_file: $lock_dir/master.lck [mailman] layout: local Best, Mark On 8/2/19 2:03 am, Mark Sapiro wrote: > On 2/6/19 9:58 PM, Mark Dale wrote: >> Hi All, >> >> On a new installation (pip), when starting Mailman it seems it cannot >> find the "master" file. Have I missed a configuration somewhere that >> tells it to look in "/usr/local/bin" rather than "/usr/bin"? > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-…>. >

7 years, 6 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Mon, Jan 30, 2023 at 9:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 09:46, Odhiambo Washington wrote: > > > > So, if I understand this correctly, there is no need for the addition of > > this parameter: > > > > ``` > > configuration: /path/to/postfix-mailman.cfg > > ``` > > to the mta config block in mailman.cfg in a non-docker environment, or > when > > only using hash tables?? > > > Correct. > Great. So, since the creation of that file is prominent in the doco, maybe a note can be added to that effect? Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 15.06.23 um 00:34 schrieb Mark Sapiro: >> - Then I tried settings_local.py with: >> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > That is the correct place. It should work. Did you restart the container > after making this change? > Mh, unfortunately it does not work. - I changed the file and rebuilt the container. - I also restarted all 3 containers again. - I checked in the container the settings_local.py to verify that the change "arrived" and found it. - It still sends the "reset-password"-email with postorius@$SERVE_FROM_DOMAIN as shown in the screenshot. Is there any other way to test or check it? Any more ideas? Thank you in advance. ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: image/png Name: Bildschirmfoto_2023-06-15_22-55-29.png

3 years, 2 months

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello Mark, thanks for your answer. So I had in the past registered that yahoo address withing mailman. Then I added oauth/openid to yahoo, then gave it a try. I have receieved as resut two email in the yahoo mailbox. One is sent by yahoo, notifying about account activity. The other, which I have not overseen as it was evaluated as spam, contains: You are receiving this email because you or someone else tried to signup for an account using email address: zzz(a)yahoo.com However, an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account: https://…/accounts/password/reset/ So the text "we have sent you an email for verification” but the email stating ”there is already such an account within mailman” is misleading, especially after the first message is shown to an yahoo-authenticated user. Greetings // Дилян -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman/Django-allauth integration with Yahoo Date: 06/08/24 03:01:24 On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to dpa-mailman(a)aegee.org

2 years

[MM3-users] Use WHAT-WG decoding strategy? [was: Another interesting error...]

by Stephen J. Turnbull

Mark Sapiro writes: > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence I'm pretty sure 0x87 is reserved by the later GBK standard (implemented as an encoding in GB18030) as a prefix for extensions. This is a common problem with Chinese and Japanese encodings: junky email clients use "traditional" names denoting encodings with smaller repertoires to denote modern encodings. I wonder if we shouldn't just promote all gb* to gb18030 and all Shift JIS to the most recent version, as in the WHAT-WG web encodings standard. If nobody says "that's really stupid", I'll write up a RFE later this week. I think there's already a module on PyPI we can use to implement. Steve

8 years, 3 months

[MM3-users] Re: Reset digest number and volume

by Andrew Bernard

HI Mark, I get: >>> commit() Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'commit' is not defined Andrew On 26/6/19 11:49 pm, Mark Sapiro wrote: > On 6/26/19 3:08 AM, andrew.bernard(a)gmail.com wrote: >> How to do this? After lots of testing on my pre-release beta testing list, I want the first production digest to be reset toVolume 1, Number 1. > > You can do this in `mailman shell` by setting the list's `volume` and > `next_digest_number` to 1. E.g., > > > $ ./mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the list(a)example.com mailing list >>>> m.volume = 1 >>>> m.next_digest_number = 1 >>>> commit()

7 years, 1 month

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:56 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/28/20 4:39 PM, Mark Dadgar wrote: >> >> The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py >> >> patching file email.py >> patch: **** malformed patch at line 4: import os > > > That probably isn't because of version mismatch. That would give applied > at offset or with fuzz or a reject. malformed patch means the patch file > is not formatted correctly. Here it is again as an attachment. That may > help. That gives a slightly different error: mark@mail:/usr/lib/python3/dist-packages/hyperkitty/models$ sudo patch < /tmp/patch.txt patching file email.py Hunk #1 FAILED at 24. patch: **** malformed patch at line 23: - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 1 month

Search results for query "sapiro"