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

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

by Shashikanth Komandoor

I am extremely *sorry* Mark. As I was put under pressure with a timeline, I have reminded you over anxiety. I should not have disturbed such a good helper. Sorry once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 9:24 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 6:27 PM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Any suggestions over my earlier email? I am waiting for your > > reply. > > > Be patient. I am a volunteer and I have a life outside of Mailman. > > > -- > 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 & Regards, Shashi Kanth.K 9052671936

5 years, 9 months

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

by Mark Sapiro

On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > How to find out the versions of the each and every component > of the mailman 3 like mailman core, mailmancilent, postorius, > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > after installation? cd to the directory in which you cloned the gitlab project for the component and do `git log` > If I am running an old mailmanclient or older version of any > other mailman component, please suggest how to upgrade either one or > multiple components based on the requirement. Is there any link that > would help me to upgrade ? > > I have used the > link https://docs.mailman3.org/en/latest/devsetup.html to install the > mailman 3 components. I expected that the procedure followed in this > link would install the latest versions of the mailman 3 components. > Please correct me if I am wrong. Is there any latest version > compatibility table ? If you installed each of mailman, mailmanclient, django-mailman3, postorius and hyperkitty according to instructions like $ cd ~/mailman $ git clone https://gitlab.com/mailman/mailmanclient.git Then set up mailmanclient: $ cd mailmanclient $ python setup.py develop $ cd .. from that document, you should have the latest version. If that is the case, `git log` in the mailmanclient directory should begin like commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, origin/master, origin/HEAD) Merge: ff39dd8 8670751 Author: Abhilash Raj <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 commit 8670751caff689733751ef323ef521c4a3fa1237 Author: Abhilash Raj <raj.abhilash1(a)gmail.com> Date: Wed Oct 14 17:36:58 2020 -0700 Use GHCR for the CI image commit ff39dd8f03a820f442f2251553c444370df3b914 Merge: 80ebed4 76d44e1 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Fri Aug 7 19:35:05 2020 +0000 Merge branch 'invite' into 'master' Add support for inviting an email address to join a list. See merge request mailman/mailmanclient!129 or if you did this before Oct 15, maybe it starts with commit ff39dd8f03a820f442f2251553c444370df3b914 The particular commit you need for your issue is commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 Merge: c8dcb1e 28d1c3a Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Sat May 16 08:02:21 2020 +0000 Merge branch 'held-count' into 'master' Add a new get_held_count() API to get a count of held messages. See merge request mailman/mailmanclient!122 Note that unless you intend to do actual development of Mailman 3, you should be following <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather than <https://docs.mailman3.org/en/latest/devsetup.html>. -- 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: Uncaught runner exception

by Wolfgang Bock

Yes, and I made all the tests as discribed here: https://workaround.org/ispmail/buster/relaying-through-postfix/ including the swaks test mentioned before output of sudo netstat -lntup | grep ":25" tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20660/master tcp6 0 0 :::25 :::* LISTEN 20660/master output of sudo lsof -i :25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 20660 root 13u IPv4 1474228 0t0 TCP *:smtp (LISTEN) master 20660 root 14u IPv6 1474229 0t0 TCP *:smtp (LISTEN) Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 7. April 2020 21:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 3:22 AM, Wolfgang Bock via Mailman-users wrote: > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost > on port 25 > > I have no idea what to do for solving my problems. Can you successfully telnet localhost 25 from a shell on the server? -- 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/

6 years, 4 months

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/5/26 06:30, Chihurumnaya Ibiam via Mailman-users wrote: > > Yes, postfix_lmtp table is set in transport_maps, virtual_mailbox_maps, > > relay_domains, local_recipient_maps. > > I'm coming in late here so I may have missed things, but ... > If you actually have virtual_mailbox_domains and virtual_mailbox_maps, > see > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht... I don't have those, postfix isn't configured to use a virtual interface. > > No, I'm not running mailman as root, it's run as mailman. > > Seeing as that's the case, would I still need to change lmtp_port? > > The lmtp_port setting determines what port mailman listens on and what > port is in the lmtp: entries in postfix_lmtp. Id should absolutely NOT > be the same port dovecot listens on and the default 8024 is a good value. Yes, I commented the setting out and it now defaults to 8024. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/16/23 19:20, Mike Wertheim wrote: > I'm running an email list on mailman3. > > My users are getting inundated by messages saying that their subscriptions > have been disabled due to their bounce score exceeding the mailing list's > bounce_score_threshold. > > But there is nothing wrong with these users' email accounts. They are all > perfectly fine. Apparently the issue is somehow related to spam. Is spam being posted to your list? If so, you should ensure that Default action to take when a member posts to the list is set to Hold for moderation so that spammers can't subscribe to your list and post without the post being reviewed by a moderator. Then if the post is on topic, the moderator can set the user's moderation action to Default processing when accepting the post so subsequent posts won't be held. Also set `verp_probes: yes` in the [mta] section of mailman.cfg. Then when a user's score reaches threshhold, a probe message is sent and delivery is only disabled if the probe bounces which it probably won't if the issue is spam bounces. > Whenever I (as admin) get these emails, I just unsubscribe the user and > then re-subscribe them. But also, the user gets confused and emails me > about it, which unnecessarily takes up their time and mine. That should be unnecessary. Just click on the member in the members list and set the member's Delivery status to Enabled. However, this may not work because of https://gitlab.com/mailman/mailman/-/issues/1061 which is not fixed until the next release, but enabling verp_probes will avoid that issue. > The relevant list settings are currently... > bounce score threshold: 5 > bounce info stale after: 7d > bounce disabled warning interval: 7d > bounce disable warnings: 5 > > What's the best way to fix this? I'm considering reducing "bounce > info stale after" to "2d" and/or increasing "bounce disabled warning > interval" to "90d". Increasing "bounce disabled warning interval" or "bounce disable warnings" won't help because the user's delivery will still be disabled. It will just take longer for them to eventually be removed. Reducing "bounce info stale after" to "2d" might help as long as the list gets good posts more frequently than that, but the best way to deal with this is to enable verp_probes and then only consider other things if that doesn't help. -- 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: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 7:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 7:28 AM, Odhiambo Washington wrote: > > On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > >> core than the one reading that mailman.cfg and the one Postorius is > >> talking to. > >> > > > > How can I track the one it's talking to? > > > Try `/opt/mailman/mm/venv/bin/mailman info` > So this command's output pointed to /opt/mailman/var/etc/mailman.cfg instead of my file that is in /opt/mailman/mm/mailman.cfg According to the HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> I am following, mailman.cfg should be in /opt/mailman/mm/. Now I am wondering what I am missing again. Did something change? Should I place all my config files in /opt/mailman/var/etc/ instead of /opt/mailman/mm/ ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

4 years

[MM3-users] Re: The doubled entries issue

by Mark Sapiro

On 11/13/23 10:06, Lars Bjørndal wrote: > > On Sun, Nov 12, 2023 at 08:07:59AM -0800, Mark Sapiro wrote: >> for info. However, that script cannot be run as is by `mailman shell --run`. >> It can be run by invoking `mailman shell` interactively and copying and >> pasting it, > > Yes, that worked, e.g. no error messages. >> or if your Mailman is installed in a venv it can be run with the >> venv active by `python ./fix-doubled-entries.py`. > > I have mailman installed in venv, but got the following when trying that: > > "python fix-doubled-entries.py" need the IListManager interface but can't find it. I see that that's actually expected. In order to run that script with the Python in the venv, you'd need to add ``` from mailman.core import initialize initialize.initialize() ``` to the script to properly set up the Zope components. >> However, that script will not fix your issue because you don't have multiple >> mhonarc entries for a list. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and as it says, Tell us more about the "duplicate entries" error, and if >> possible copy it exactly from where you found it originally, including any >> traceback. > > Here's the entries in the mailman.log file: > ... > Nov 11 09:18:47 2023 (1715) Uncaught runner exception: Multiple rows were found when one or none was required > Nov 11 09:18:47 2023 (1715) Traceback (most recent call last): > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/runners/outgoing.py", line 111, in _dispose > self._func(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/deliver.py", line 89, in deliver > refused = agent.deliver(mlist, msg, msgdata) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/base.py", line 167, in deliver > callback(mlist, message_copy, msgdata_copy) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/mta/decorating.py", line 32, in decorate > decorator.process(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/handlers/decorate.py", line 250, in process > process(mlist, msg, msgdata) > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/handlers/decorate.py", line 73, in process > for archiver in IListArchiverSet(mlist).archivers: > ^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/component/_api.py", line 167, in adapter_hook > return sitemanager.queryAdapter(object, interface, name, default) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/interface/registry.py", line 351, in queryAdapter > return self.adapters.queryAdapter(object, interface, name, default) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/database/transaction.py", line 106, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/model/mailinglist.py", line 653, in __init__ > ListArchiver.name == archiver_name).one_or_none() > ^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/orm/query.py", line 2769, in one_or_none > return self._iter().one_or_none() # type: ignore > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/engine/result.py", line 1813, in one_or_none > return self._only_one_row( > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/engine/result.py", line 816, in _only_one_row > raise exc.MultipleResultsFound( > sqlalchemy.exc.MultipleResultsFound: Multiple rows were found when one or none was required > Nov 11 09:18:47 2023 (1715) SHUNTING: 1699690727.810848+3b6f3baba5576f3d87d3ff392aba2715d4dda793 That does look like https://gitlab.com/mailman/mailman/-/issues/657, but your database query showed no duplicate mhonarc entries for a list. Possibly, it was a different archiver, or more likely considering > I don't know what fixed the problem, but when I did `mailman unshunt` the message went through. it was already fixed when you queried the database. > Will mailman notify when there's shunted messages? No. I run a daily cron that does `ls -lAR /opt/mailman/mm/var/queue/` which lists the shunt queue and the others. -- 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: List in list, mutiple reply-to addresses

by Stefan Bauer

Unfurtunately, this completely removes the reply-to: header and sets the list-address as a new and only reply-to. This way, a reply does not address the origin sender anymore :/ Am Mo., 22. Nov. 2021 um 19:17 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/22/21 6:27 AM, Stefan Bauer wrote: > > > > john receives following mail: > > > > from: iu-int@mydomain > > reply-to: mike@mydomain, iu-all@mydomain > > > > If john now hits reply in mailclient, mail goes to ALL instead of just > the > > from-address, as mailman extended the reply-to header. > > > > How can this be changed? > > > Set Settings -> Alter Messages -> First strip reply to to Yes on the > iu-int list. > > -- > 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/ >

4 years, 8 months

[MM3-users] Re: Command Emails not Working

by Mark Sapiro

On 4/22/26 10:23 AM, Brinson, Jason T via Mailman-users wrote: > As requested: > > Posfix log (journalctl -u | grep demo-list): > Apr 22 11:14:16 cc-postoffice-01 postfix/qmgr[523389]: E6943400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1853, nrcpt=1 (queue active) > Apr 22 11:14:48 cc-postoffice-01 postfix/lmtp[523634]: F1957400A9D: to=<demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f(a)mailman.cc.gatech.edu<mailto:demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.59, delays=0.5/0.01/0.01/0.07, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 089D0400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=20898, nrcpt=1 (queue active) > Apr 22 11:14:50 cc-postoffice-01 postfix/lmtp[523634]: 089D0400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 40995400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1322, nrcpt=1 (queue active) > Apr 22 11:14:52 cc-postoffice-01 postfix/qmgr[523389]: 1063C400A9D: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=21257, nrcpt=1 (queue active) > Apr 22 11:20:47 cc-postoffice-01 postfix/qmgr[523389]: 9D5E0400A3C: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1860, nrcpt=1 (queue active) > Apr 22 11:21:56 cc-postoffice-01 postfix/lmtp[526023]: EEB2640083E: to=<demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1(a)mailman.cc.gatech.edu<mailto:demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.28, delays=0.26/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C12EA40083E: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1326, nrcpt=1 (queue active) > Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C6D87400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=24425, nrcpt=1 (queue active) > Apr 22 11:21:57 cc-postoffice-01 postfix/lmtp[526023]: C6D87400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok) > Apr 22 11:21:59 cc-postoffice-01 postfix/qmgr[523389]: A72C940083E: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=24784, nrcpt=1 (queue active) I don't see any messages there about mail to=<demo-list-join(a)cc.gatech.edu> or to=<demo-list-request(a)cc.gatech.edu>. Don't use journalctl. do, e.g., grep 'demo-list-(join|request)' /var/log/mail.log and then grep the queue IDs of the messages found to see all the relevant messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 4 weeks

[MM3-users] Re: External MTA incoming mail: configuration

by Mark Sapiro

I see this reply is now moot as you have now configured list mail to go directly to the Mailman server, but ... On 8/5/24 03:44, Roland Giesler via Mailman-users wrote: > > In the logs of the MTA I see this however: warning: do not list domain > fast.za.net in BOTH virtual_mailbox_domains and relay_domains > > Mailman creates these entries, but postfix doesn't like it. I don't see > any mail delivered to the mailman yet. Is this the problem? Probably not. It is telling you that mail to the fast.za.net domain cannot both be delivered to local mailboxes (virtual_mailbox_domains) and relayed to foreign hosts (relay_domains) > In the MTA postfix main.cf: > > relay_domains = hash:/etc/mailman3/data/postfix_domains > > cat /etc/mailman3/data/postfix_domains > ... > > and also > > local_recipient_maps=$virtual_mailbox_maps, > hash:/etc/mailman3/data/postfix_lmtp > > cat /etc/mailman3/data/postfix_lmtp > ... How about transport_maps = hash:/etc/mailman3/data/postfix_lmtp > > Then there's: > virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf > > cat /etc/postfix/virtual-mailbox-domains.cf > dbpath=/home/user-data/mail/users.sqlite > query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM > aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE > source LIKE '%%@%s' > > When I run that query in sqlite3, it returns no records, so I'm not sure > how this is supposed to work. %s to me means that first argument, so is > this used in python and then %s is the argument sent to this query? See https://www.postfix.org/sqlite_table.5.html `%%` is replaced with `%` which is a SQL wildcard matching anything and `%s` is replaced by the key postfix is looking for, i.e. the domain that it is asking about. So, that query becomes SELECT 1 FROM users WHERE email LIKE '%(a)fast.za.net' UNION SELECT 1 FROM aliases WHERE source LIKE '%(a)fast.za.net' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%(a)fast.za.net' I.e, it returns true if any user or alias or auto_alias has an address ending in '@fast.za.net' and if that's true the mail to any '@fast.za.net' address including list mail will be stored locally. If you really have local users on box2.gtahardware.co.za with addresses '@fast.za.net' and you want to relay list mail to lists '@fast.za.net', you need to see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Search results for query "sapiro"