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

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 11:27, dap1--- via Mailman-users wrote: > Yes, everything is from the virtual environment and there were no errors reported anywhere during the process. > > <venv> $ ls -l /opt/mailman/var/etc > total 4 > -rw-rw---- 1 mailman mailman 501 Oct 19 11:07 mailman.cfg > > The sqlite line bothered me from the beginning. Shouldn't it be mysql? I'm still concerned that `mailman info` reports the config at /opt/mailman/var/etc/mailman.cfg instead of /etc/mailman3/mailman.cfg. The database is sqlite because thats what's defined in /opt/mailman/var/etc/mailman.cfg. Did you create /etc/mailman3/mailman.cfg? what does diff /etc/mailman3/mailman.cfg /opt/mailman/var/etc/mailman.cfg give? You are not seeing the list in mysql because Mailman core is using the sqlite db at /opt/mailman/var/data/mailman.db > <venv> $ ls -l /opt/mailman/var/data > total 300 > -rw-rw---- 1 mailman mailman 274432 Nov 1 14:40 mailman.db > -rw-rw---- 1 mailman mailman 343 Nov 1 14:39 postfix_domains > -rw-r----- 1 mailman mailman 12288 Nov 1 14:39 postfix_domains.db > -rw-rw---- 1 mailman mailman 1003 Nov 1 14:39 postfix_lmtp > -rw-r----- 1 mailman mailman 12288 Nov 1 14:39 postfix_lmtp.db The postfix files are good, but the mailman.db is spurious because the mailman.cfg that the mailman command is using most likely doesn't define a [database] section and gets the default from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… The [database] you have defined in mailman.cfg as [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman:pppppppp@localhost/mailman?charset=utf8mb4&use_unicode=1 is presumably defined in /etc/mailman3/mailman.cfg which isn't being used. What is the content of /opt/mailman/venv/bin/mailman? Do you have the environment variable MAILMAN_CONFIG_FILE set? > I did this import command: > > <venv> $ mailman import21 lllllllllllll(a)ddddddddd.net /tmp/config.pck Which works but imports to the list defined in the sqlite database at /opt/mailman/var/data/mailman.db. > This was the hyperkitty command: > > <venv> $ mailman-web hyperkitty_import -l lllllllllllll(a)ddddddddd.net /tmp/lllllllllllll.mbox > > <venv> $ mailman-web diffsettings|grep DATABASES > DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmanweb', 'USER': 'mailma > n', 'PASSWORD': 'ppppppppp', 'HOST': 'localhost', 'PORT': '3306', 'OPTIONS': {'charset': 'utf8mb4'}, > 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'CONN_HEALTH_CHECKS': False, 'TIME_ > ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': N > one}}} This looks correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This my settings.py email config: #DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' # Change this when you have a real email backend # EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Mailing <mailing(a)labbrands.com>' El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 6 months

[MM3-users] Re: Maximum number of recipients error

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:57 AM, Mark Sapiro wrote: > On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > > > "An error occured: Unknown attribute: max_num_recipients" > > > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? > > > It works for me. It was added by > <https://gitlab.com/mailman/postorius/merge_requests/358>, but it > requires Mailman core >= 3.2.1. What's in the docker image you're using? > This may be an issue for <https://github.com/maxking/docker-mailman>. It is an issue for images repo. I haven't yet updated to the latest releases, sorry! > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 11 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

and: When I put the stanza >> [language.en] into the mailman.cfg, the service doesn’t restart: … PermissionError: [Errno 13] Permission denied: '//var/templates' somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Mark Sapiro wrote: >> >> You can change this for English by putting >> >> [language.en] >> charset: utf-8 >> >> in your mailman.cfg. This works because us-ascii is a proper subset of >> utf-8. > > > I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. > _______________________________________________ > 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/

7 years, 1 month

[Test] Re: setting up the mailman-users@mailman3.org list

by Mark Sapiro

> I think we are very close to going live with a > mailman-users(a)mailman3.org list. > > I am comfortable that between Postorius and mailman shell I can create > and configure the list. The HyperKitty issues that were blockers for me > have been fixed. > > The one remaining blocker that I see[1] is that Google login doesn't > work. This is reported here > https://gitlab.com/mailman/hyperkitty/issues/73 I have been playing with this. I gave up on Google OpenID and tried configuring Google OAuth2 and Twitter OAuth. I've actually got Google working, so bang on it some. I'm close with Twitter, the issue is it gets all the way back but something is missing when HyperKitty tries to get the user record. The last few lines of the traceback are: File "/usr/local/lib/python2.7/dist-packages/HyperKitty-1.0.4-py2.7.egg/hyperkitty/lib/mailman.py", line 155, in add_user_to_mailman mm_user = profile.get_mailman_user() File "/usr/local/lib/python2.7/dist-packages/HyperKitty-1.0.4-py2.7.egg/hyperkitty/models/profile.py", line 91, in get_mailman_user mm_user = mm_client.get_user(self.user.email) File "/usr/local/lib/python2.7/dist-packages/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 514, in get_user return User(self._connection, content['self_link'], content) KeyError: u'self_link'

9 years, 10 months

[MM3-users] Re: Post-installation documentation?

by David Newman

On 11/26/21 10:21 AM, Mark Sapiro wrote: > On 11/26/21 9:49 AM, David Newman wrote: >> On 11/25/21 1:16 PM, Mark Sapiro wrote: >>> >>> What django admin command are you running? >> >> As the mailman user, with venv activated: >> >> (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com >> /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox > > > hyperkitty_import is not a command. it is a subcommand to the django > administration command. You need to run > ``` > mailman-web hyperkitty_import -l testlist(a)lists.domain.com > /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox Bingo. Thank you! When running the subsequent 'mailman-web update_index_one_list' command to index the imported archive, the command failed with a permissions error on '/opt/mailman/web/fulltext_index' because that directory didn't yet exist. Creating that directory and chown'ing it to mailman resolved that. I'm still getting an error from the list page when clicking archives, but I'll investigate further and open a new thread if needed. Let's close this already overly long thread here. Thanks *very* much for your patience in resolving the import issue. If nothing else this is good fodder for an eventual admin guide. dn

4 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can I use it for mailing lists? like MailChimp? El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:07 PM, Rafael Mora wrote: > > I want to use Mailman to send emails to our customers. > > > So you need to create a list and add your customers as members. > > Please note that Mailman is not a substitute for a customer relations > management system. It can be used in that way, but a true CRM system has > advantages ove Mailman. Mailman is primarily designed to support > discussion lists such as this one. > > > > I´m getting this error when I click on sign up and log in: > > > > FilterError at /accounts/login/ > > /bin/sh: sassc: command not found > > > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

[MM3-users] Re: footer message

by Henrik Rasmussen

From lists imported by import21, the colon in the files are substituted with underscores. Instead of list:member:regular:footer.txt the file are called list_member_regular_footer.txt And I wonder why having a footer text makes the mail contain the original HTML message sent to the list as attachment both in .txt and .html and the footer-text from list_member_regular_footer.txt as inline message. 'collapse_alternatives': False, 'convert_html_to_plaintext': False, 'filter_content': False, 'include_rfc2369_headers': True, 'posting_pipeline': 'default-posting-pipeline', -- Henrik Rasmussen her(a)adm.ku.dk University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 1. september 2018 20:17 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: footer message On 09/01/2018 10:51 AM, Abhijith PA via Mailman-users wrote: > > If I understand correctly, temp@lists.example.com:member:regular:footer > file need to created for /temp mailinglist/ ? Not exactly. Assuming default settings and English the file would go in Mailman's var/ directory at var/templates/lists/temp.lists.example.com/en/list:member:regular:footer.txt -- 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/

7 years, 5 months

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > 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 huhamails(a)gmail.com >

10 months, 2 weeks

[MM3-users] Re: installation choices for mm3

by Mark Sapiro

On 5/16/19 10:33 AM, John Griessen wrote: > I've been reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > > and see that a virtual is recommended, which is not something I have > done yet, and wonder > if just putting the mm3 on a different server is easier? I am the author of that document. I started with virtualenv because my first Mailman 3 installation used the now obsolete mailman-bundler and it installed things in virtualenvs. It is not at all necessary to use virtualenv. Note that the first paragraph of the "Installation" section in that document says: For these installs, I opted to install the entire Mailman suite in a virtualenv. The biggest motivation for this choice was the fact that there are already production lists on both servers and using a virtualenv allowed me to do a lot of the work in advance without interfering with the production install. Possibly influenced by these experiences, I am now using virtualenv for all installs. There are pros and cons to using a virtualenv. The big plus is it isolates your installation and avoids conflicts due to the installed software requiring versions of dependencies that are different from those that might be installed and required system wide. It also avoids the need to install as root although things like web server and MTA configuration still require root. The downside is a potentially larger footprint in the file system. > I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, > mm2, nsd on it. Another server has just web pages and nsd doing backup > DNS for mail1.cibolo.us DNS server. I could do a straight debian > install of mailman3-full on the 2nd server > and keep it simple, let debian setup a blank database installation, > right? Has anyone seen a good write up on how to do that on a debian > server step by step? I can't speak to the installation of the Debian package. It should be straightforward, but I don't really know. The one potential glitch is if you don't have an MTA on the Mailman server. This is doable. Mailman has it's own LMTP server to receive mail and can be configured to use a remote MTA to deliver mail. Mailman also generates transport mappings to control delivery of mail to Mailman and these get updated when lists are added or deleted. There is a configurable postmap_command which is invoked when the maps are updated to update the .db files. That can point to a shell script to rsync the files to the other server if needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Search results for query "sapiro"