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

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 16:25, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > On 03-Aug-17 17:14, Rafael Mora wrote: > > > > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > You've said you're working with labbrands.com <http://labbrands.com > >. > > > > labbrands.com <http://labbrands.com> has address > 192.185.51.89 > > mail.labbrands.com <http://mail.labbrands.com> has address > > 192.185.51.89 > > www.labbrands.com <http://www.labbrands.com> is an alias for > > labbrands.com <http://labbrands.com>. > > > > telnet proves that Exim is running on that IP address. Either you're > > running it, or hostgator is redirecting the SMTP ports. > > > > You added: > > lists.labbrands.com <http://lists.labbrands.com> has address > > 190.145.27.66 > > > > Presumably that's a different machine. > > > > So that now needs an MX record, and a firewall routing. > > > > > > I added the MX record on our hostgator hosting like this: > > image.png > > > > Is it correct??? > > > No. And sending images to the mailing list doesn't get you help. > > You set up lists.labbrands.com as a secondary server, not an independent > mail domain. This will cause you serious grief. > Ok I will remove that MX record on my hostgator hosting. Thank for your help. > > You need to get some help from a more suitable list. Setting this up is > not mailman-specific, and getting it right is more than a quick note. > > Try the Postfix documentation & mailing lists. > > > > > > > And the SPF > > records ... and spam and virus filters, and all the other stuff > > you need > > to setup an independent, public-facing smtp server. > > > > But at least you won't have to relay. > > > > Good luck. > > > > On 03-Aug-17 16:55, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > > >> I think you're confused. > > >> > > >> You already have mail.labbrands.com <http://mail.labbrands.com> > > set up as the MX record for > > >> labbrands.com <http://labbrands.com>. And it has an A record > > with the same address as your > > >> webserver. > > >> > > > I'm working with the hostgator mailserver, we are not running a > > local > > > mailserver. > > > > > > As suggested I added an A record like this: > > > [image: image.png] > > > > > > Is it correct? is it redirecting to my Ip so I can redirect it to > my > > > postfix/mm3 server? > > > > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > > >> server running on that IP address. You can't have 2 servers > > on port > > >> 25. In that case, as has been noted before, you'll need to setup > a > > >> relay in that server, not a firewall redirect. Depending on > > your MTA, > > >> you would need to relay to your internal server. And make sure > > your > > >> firewall setup allows your MTA to do this. > > >> > > >> We can see it's EXIM: > > >> > > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > > >> Trying 192.185.51.89... > > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > > (192.185.51.89). > > >> Escape character is '^]'. > > >> help > > >> 220-gator4137.hostgator.com > > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > > Aug 2017 15:47:48 > > >> -0500 > > >> 220-We do not authorize the use of this system to transport > > unsolicited, > > >> 220 and/or bulk e-mail. > > >> 214-Commands supported: > > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > > >> quit > > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > > closing connection > > >> Connection closed by foreign host. > > >> > > >> Or, consolidate all your e-mail to one server - which is a lot > > easier to > > >> manage unless you have a really big operation. Postfix is > > probably the > > >> right choice, but requires more setup. > > >> > > >> Although Mailman3 configuration is not well documented (as you've > > >> discovered), you may want to get help from someone with more > > general > > >> network and mail experience. You're now into territory that is, > as > > >> Simon indicated, not Mailman-specific. > > >> > > >> On 03-Aug-17 16:28, Rafael Mora wrote: > > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >> escribió: > > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >>>> escribió: > > >>>>>> You need to forward port 25 for SMTP mail delivery and if > > you want the > > >>>>>> web UI (Postorius and HyperKitty) accessible from the > > outside, port 80 > > >>>>>> for http and/or port 443 for https > > >>>>>> < > > >>>>>> > > >> > > > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > > >>>>>>> . > > >>>>> I mean for incoming mail redirected from my hostgator > > hosting, because > > >>>> when > > >>>>> I suscribe an email address MM3 sends a confirmation email, > > so I have > > >> to > > >>>>> reply to be suscribed to the list. > > >>>> As I said, for mail delivery you need to forward port 25 to > > the Mailman > > >>>> server. > > >>>> > > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my > local > > >> centos7 > > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > >>> > > >>> > > >>>> -- > > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > > >>>> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >>>> > > >> -- > > >> This communication may not represent my employer's views, > > >> if any, on the matters discussed. > > >> > > >> _______________________________________________ > > >> Mailman-users mailing list > > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > >> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >> > > > > -- > > This communication may not represent my employer's views, > > if any, on the matters discussed. > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > 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, 2 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Abhilash Raj

On Mon, Apr 9, 2018, at 8:59 PM, Mark Sapiro wrote: > On 04/09/2018 03:59 PM, Abhilash Raj wrote: > > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: > >> Hi, > >> > >> is there any equivalent to "Approved" header that was present in MM2 in > >> MM3 land? Google is not very helpful in that. > > > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. > > > I don't think it is broken, but it requires setting the > moderator_password attribute for the list which can be set visa REST but > I think not by mailmanclient. > Thanks Mark for clarification. > > > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > > > > > Agreed. This is a shared password. and would be sent in plain text as a > header or body line. > > It would be nice though to have some feature to enable, for example, > spoof proof posting to a one-way (announce only) list. > > One thought on how to do this would be to have a list attribute that > says posts from 'authenticated' owners and moderators can be auto > approved and authentication could be by PGP signing the post. This would > require Mailman to have the ability to verify a PGP signature from an > owner or moderator which is not currently the case. +1 on using PGP signatures for doing this and that is exactly what I was thinking :) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 6 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 11:55, Victoriano Giralt wrote: > On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: >> If the manage.py in the directory in which you ran this is the >> correct one for your Mailman Django project, I don't know why it >> didn't work. > Me neither :-( That's why I asked, and probably Guillermo, as well. > >> Is your Mailman installed in a virtualenv? If so, was the virtualenv >> activated? > No virtualenv. Mine is deployed using system python on a CentOS 7 > system, toghether with another in house developed low requirements > Django project, both served by uWSGI vassals. And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server. > > And then, all of a sudden, while I was writting this, it dawned on me! > > Postorius, Hyperkitty and django-mailman are installed with pip, so, > the end up in the site-packages directory (usually > /usr/local/lib/python3.x/site-packages), That is my case, too. > but, normally, django projects > are deployed somewhere in the web server hierarchy (/var/ww/django in > my case, due to old personal tastes), and applications properly defined > in the settings.py for the project. > > So, the message files are out of reach for manage.py. > > Changing to /usr/local/lib/python3.x/site-packages/X > (with X being postorius, hyperkitty and django_mailman3) and using > django-admin compilemessages all works! And for me as well. Thanks a lot Victoriano, I owe you a beer > > Thanks for pushing my thoughts in the right direction! > > > _______________________________________________ > 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/

4 years, 8 months

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Marc SCHAEFER

Hello, On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with any > lists. it references an entry in the django_sites table in the database. Thank you, will look into this. > As far as the comment/display name in From: is concerned, what specific > emails are you talking about? This. Sorry, I mixed From: with Subject: and the content: Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius(a)lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.com I guess it's the same SITE_ID setting in Django's DB: $ grep SITE_ID /usr/share/mailman3-web/settings.py SITE_ID = 1 However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com. I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it. > for ADMINS in your Django settings. ADMINS = ( ('Mailman Suite Admin', 'schaefer(a)alphanet.ch'), ) That looks correct. > The `mailman import21` command will properly import the Mailman 2.1 > from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user. > If you have some customization in this area, that probably won't be handled. Obviously.

1 year, 4 months

[MM3-users] Re: Caching problem with templates

by Mark

On Thu, 2025-06-26 at 18:36 -0700, Mark Sapiro wrote: > > You can delete the cached entry from the database via `mailman shell > as in > >>> cm = getUtility(ICacheManager) > >>> uri = 'the_uri_from_the_template_table' > >>> cm.get(uri, expunge=True) > >>> commit() > ``` > > You can also delete the entry from the file_cache table, but if you > do > that, the actual file containing the cached data will remain. To > remove > it, > > Rather than doing any of the above, if you want to manipulate the > database, just set the expires_on column in the file_cache table > entry > to a date in the past. > Hi Mark, Thank you for this information. I've given the options a good workout over the last couple of days and found that: 1. Deleting the cache via the mailman shell does the job, but is beyond me to script. There are numerous lists and list owners updating their templates. 2. Changing the expires_on date (to a date in the past) in the file_cache table didn't prevent the cached entry from being used; 3. What did work was removing the records in the file_cache table PLUS removing the corresponding files in var/cache/*/*/* -- for example: /opt/mailman/mm/var/cache/3a/2f/* This I was able to script in bash and cron to run every minute. A hack I know, but it's working for now. I've attached the script in case it's of use to anyone else. (mailman_clear_template_cache.txt) Note: change <USER> in the script to what suits. Does Mailman really need to cache the templates? It seems to be an unnecessary complication. Anyways it happy days again. Thank you again, very much. Your guidance was appreciated immensely as always. Best, Mark

3 months, 3 weeks

[MM3-users] Re: Moving/cloning mailman3

by Abhilash Raj

Just take a dump of the database and move to other one, almost everything is stored in database. Outside of database, if you need to move log files and currently pending emails in shunt or held queue (broken or pending emails), you need to move the 'var' directory of Core and it's configuration. If you are using docker installation, database container holds the database and '/opt/mailman/core/var' is what you are looking for. Thanks, Abhilash Raj (Apologies for top post) On October 18, 2017 1:29:58 PM PDT, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/18/2017 11:10 AM, Mark Sapiro wrote: >> On 10/18/2017 08:56 AM, Dmitry Makovey wrote: >>> Hi, >>> >>> I am drawing a blank looking for documentation for mailman3 >migrations. >>> How can one dump existing settings for mailman and import it into >>> another instance? >> >> >> The Mailman 3 command 'mailman import21' is what does this >> ><http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.ht…>, >> however there are issues in that not all 2.1 settings are imported at >> all or correctly and in at least one case on an announce only list, >the >> membership wasn't imported. >> >> I intend to work on this, but haven't got as far as even documenting >the >> problems, much less coming up with fixes. > > >isn't above more about MM2 -> MM3 moves? I can't file .pck files for >MM3 >setup thus assuming there are some other files/commands I need to >tackle >to move MM3 from host to host. > > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Thomas Krichel

Mark Sapiro writes > For older releases you can add > ``` > [runner.nntp] > start: no > ``` > to mailman.cfg Following this advice, I reverted the change I made to /usr/lib/python3/dist-packages/mailman/utilities/modules.py Then I believe I implemented Mark's suggestion root@server~# diff /etc/mailman3/mailman.cfg~ /etc/mailman3/mailman.cfg 312c312,318 < jump_chain: hold \ No newline at end of file --- > jump_chain: hold > > ## dont't start nntp because library is missing > > [runner.nntp] > start: no > ok, but root@server~# systemctl status mailman3.service × mailman3.service - Mailman3 server Loaded: loaded (/usr/lib/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-02-05 23:36:35 UTC; 9min ago Duration: 2month 3w 6d 6h 21min 31.400s Invocation: 746a7d496ddd47f6a63795e55348b6f9 Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 416285 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) Mem peak: 74.2M CPU: 1.712s Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 935, in _load_unlocked Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap_external>", line 1026, in exec_module Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed Feb 05 23:36:34 server mailman3[416285]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_gatenews.py", line 24, in <module> Feb 05 23:36:34 server mailman3[416285]: import nntplib Feb 05 23:36:34 server mailman3[416285]: ModuleNotFoundError: No module named 'nntplib' Feb 05 23:36:35 server systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 05 23:36:35 server systemd[1]: mailman3.service: Failed with result 'exit-code'. Feb 05 23:36:35 server systemd[1]: Failed to start mailman3.service - Mailman3 server. Feb 05 23:36:35 server systemd[1]: mailman3.service: Consumed 1.712s CPU time, 74.2M memory peak. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21797th day.

8 months, 2 weeks

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 30 Jun 2020, at 8:22, Florian Schulze wrote: > On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > >> On 6/29/20 1:38 AM, Florian Schulze wrote: >>> Hi! >>> >>> After upgrading to HyperKitty 1.3.x I get the following error for >>> qcluster: >>> >>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>> 300, >>> in pusher >>> task = SignedPackage.loads(task[1]) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 31, >>> in loads >>> serializer=PickleSerializer) >>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>> line >>> 38, in loads >>> return serializer().loads(data) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 44, >>> in loads >>> return pickle.loads(data) >>> AttributeError: Can't get attribute 'process_task_result' on <module >>> 'hyperkitty.tasks' from >>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>> >>> How do I recover from that? It seems like there are still persisted >>> tasks in the qcluster queue using the old code from 1.2.x with the >>> old >>> locking implementation. >> >> Have you stopped ans started qcluster since upgrading? > > Yes > >> Are you running the Django periodic jobs? > > They were disabled because of the errors (someone else did the > upgrade). I have enabled them again and will watch it and report back. The cronjobs seem to work fine, no errors so far. The queue doesn't seem to change at all. In "qmonitor" there is nothing listed and the statusline remains the same at ORM default Queued 303(118) Success 100 Failures 0 Regards, Florian Schulze

5 years, 3 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Wed, 19 Oct 2022 23:38:05 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Judging from the traceback, Onyeibo Oku's > /opt/mailman/venv/bin/mailman is quite different from mine which is > just ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: > 'mailman==3.3.5','console_scripts','mailman' __requires__ = > 'mailman==3.3.5' import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', > 'mailman')() ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv? > True mine is different: **************** /opt/mailman/venv/bin/mailman ************ #!/opt/mailman/venv/bin/python # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' import re import sys # for compatibility with easy_install; see #2198 __requires__ = 'mailman==3.3.5' try: from importlib.metadata import distribution except ImportError: try: from importlib_metadata import distribution except ImportError: from pkg_resources import load_entry_point def importlib_load_entry_point(spec, group, name): dist_name, _, _ = spec.partition('==') matches = ( entry_point for entry_point in distribution(dist_name).entry_points if entry_point.group == group and entry_point.name == name ) return next(matches).load() globals().setdefault('load_entry_point', importlib_load_entry_point) if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit(load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')()) *************** end of /opt/mailman/venv/bin/mailman *********** I have tried setting environment path (PYTHONPATH) by specifying either "Environment" or "EnvironmentFile" in /etc/systemd/system/mailmain3.service. None works. I had: EnvironmentFile=/opt/mailman/.systemd_vars where the contents of .systemd_vars are: PYTHONPATH=/usr/lib64/python310.zip:/usr/lib64/python3.10:/usr/lib64/python3.10/lib-dynload:/usr/lib64/python3.10/site-packages:/usr/lib/python3.10/site-packages:/opt/mailman/venv/lib64/python3.10/site-packages:/opt/mailman/venv/lib/python3.10/site-packages At this point, I am frustrated. Is there something else I can do to get mailman3 on this server? from a frustrated Onyeibo

2 years, 11 months

[MM3-users] Re: List description as sender

by Henrik Rasmussen

Mark Sapiro wrote: > On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: > I think your choices are: > > 1) Don't configure the list as anonymous. I've just tested it on a list which was imported from Mailman 2, but changing the list to announced doens't seem to affect the From: Thread-Topic: Test 201809241228 Date: Mon, 24 Sep 2018 10:28:32 +0000 Accept-Language: da-DK, en-US Content-Language: da-DK X-MailFrom: me(a)ku.dk X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address From: Testliste for Mailman-administratoren <project(a)lists.example.com> The list config is : { 'acceptable_aliases': [], 'admin_immed_notify': False, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': True, 'allow_list_posts': True, 'anonymous_list': True, 'archive_policy': 'never', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'project-bounces(a)lists.example.com', 'collapse_alternatives': False, 'convert_html_to_plaintext': False, 'created_at': '2014-12-05T14:16:33.126729', 'default_member_action': 'hold', 'default_nonmember_action': 'reject', 'description': 'Testliste for the Mailman administrator', 'digest_last_sent_at': '2018-09-24T10:28:39.309653', 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'project', 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'filter_content': False, 'first_strip_reply_to': True, 'fqdn_project': 'project(a)lists.example.com', 'http_etag': '"29465efe640811a7f2880b879c65c2f2651c3ac3"', 'include_rfc2369_headers': True, 'info': '', 'join_address': 'project-join(a)lists.example.com', 'last_post_at': '2018-05-25T08:10:54.222183', 'leave_address': 'project-leave(a)lists.example.com', 'list_name': 'project', 'mail_host': 'lists.example.com', 'max_message_size': 30000, 'moderator_password': None, 'next_digest_number': 17, 'no_reply_address': 'noreply(a)lists.example.com', 'owner_address': 'project-owner(a)lists.example.com', 'post_id': 91, 'posting_address': 'project(a)lists.example.com', 'posting_pipeline': 'default-posting-pipeline', 'reply_goes_to_list': 'explicit_header', 'reply_to_address': 'me(a)ku.dk', 'request_address': 'project-request(a)lists.example.com', 'send_welcome_message': True, 'subject_prefix': '[project]', 'subscription_policy': 'confirm_then_moderate', 'volume': 10} Henrik Rasmussen

7 years

Search results for query "sapiro"