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

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by IEM Network Operation Center (IOhannes m zmölnig)

thanks again, Mark, for your detailed answer. On 3/15/22 17:21, Mark Sapiro wrote: > See https://gitlab.com/mailman/mailman/-/issues/901 > > You can add something like > ``` > Alternatively, you can confirm by going to the URL > > https://$domain/mailman3/lists/$list_id/confirm/?token=$token > ``` hmm. the list-url (e.g. where you can subscribe to the list) for my instance looks like https://$domain/postorius/lists/$list_id/ (that is: it spells "postorius" rather than "mailman3"). so i guess the URL should be https://$domain/postorius/lists/$list_id/confirm/?token=$token, which unfortunately returns 404. also, my postorius/urls.py does not contain an url-pattern for "confirm", unlike the current one as found on <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> so i guess this was not possible yet with postorius 1.2.4 > to the list:user:action:subscribe template. Note that `$domain` may not > be appropriate here because it is the email domain which may not be the > web domain. > >> also: the confirmation mail says that the subject must be kept intact. >> however, i noticed that the actual "From" address of the confirmation >> mail already contains the token. > > The current template > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… > doesn't say that. yes. the *current* template. but not the template that came with mailman3 3.2.1 > >> finally: what else is required to approve the confirmation? will the >> sender's email-address be taken into account? (e.g. if they subscribed >> "foo+mylist(a)example.com" but send the confirmation-reply from >> "foo(a)example.com", will that still work? > > > Yes. Only the token is required. > cool thanks. together with the not-yet-expired tokens, i think i can create some ad-hoc web-service that translates URLs to confirmation replies. mfd IOhannes

3 years, 2 months

[MM3-users]Re: Sass and where to find core rest logs

by Simon Hanna

On 05/05/2016 04:15 AM, Mark Sapiro wrote: > On 05/04/2016 09:45 AM, Andrew Hodgson wrote: > >> Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv. >> >> I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on? > > > There are the web server logs and there is the mailman-web configured in > LOGGING:handlers:file in (using bundler) > mailman-bundler/mailman-web/production.py (or testing.py). The > production default is /var/log/mailman-web/mailman-web.log; the testing > default is /opt/mailman/var/mailman-web/hyperkitty.log. > You might also get a 500 error because of a django error. If you have debugging enabled, you should see the trace in the browser. If not, then you should get an email (If you configured am admin email) Otherwise the files above should contain information about it. > >> The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default. > > > I think the bundler doc is out of date on this. > Hyperkitty switched from less to sass. Which sass compiler you use is irrelevant. You can use the ruby implementation (but it pulls in ruby as a dep). I am using the C preprocessor from libsass.org I will go over the docs and see if that section is unclear.

9 years

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 22:18]: > On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > >yes. > >the *current* template. > >but not the template that came with mailman3 3.2.1 > > Which is over 3 years old. > > You should really be taking up these issues with Debian. Maybe if > they got enough pressure from users, they would update their > package. Debian (as all distributions) freezes their packages when releasing, that's why it's called stable. If someone wants newer packages, it's possible to use stable-backports (see below). Debian oldstable has mailman3 version 3.2.1. Debian stable has mailman3 version 3.3.1. So, in this case, the version in Debian oldstable is used. Which is, well, a bit behind stable, because oldstable is one release behind from the current stable. From (any) software point of view, distributions are always too old. However, having a frozen version of packages has great benefits for admins and reduces efforts. That's why distributions exists. As I said multiple times (also here), my recommendation is: if the software in the distribution works for you, use it. If not, use your own. However, don't assume that pressure works here at all - distributions are freezing packages for very good reason. As Debian is an volunteer effort, however it is always possible to help the distribution and get what you want by that. A good way is stable-backports, because this allows the admin to select to have single packages from the more current testing branch of Debian. However, this only happens if someone does the necessary handholding. So far nobody volunteered for mailman, therefor mailman isn't in stable-backports. If I'd like to have a current mailman on Debian, that would be my path forward (together with running Debian stable, not oldstable); but that's not an easy one if you are not involved with debian yet. Andi

3 years, 2 months

[MM3-users] Re: moving list from mm3 -> mm3

by Stephen J. Turnbull

Jens Günther writes: > Am 09.12.23 um 00:27 schrieb Mark Sapiro: > > You need a PUT command, not POST. Try the above with `-X PUT`. > > With the `-X PUT`-command, there is the following error: > {"title": "400 Bad Request", "description": "Unexpected parameters: > bounces_address, created_at, digest_last_sent_at, fqdn_listname, > http_etag, join_address, last_post_at, leave_address, list_name, > mail_host, next_digest_number, no_reply_address, owner_address, post_id, > posting_address, request_address, usenet_watermark, volume"} You should post the exact command or interactive conversation you're using. My guess is that the REST API is expecting a single JSON object, and you sent it multiple parameters. Have you played with the REST API interactively? The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… is really quite good as a tutorial. It's not a full API reference, and not organized that way, although the table of contents is very useful for what it does mention. But I think what you need (if you want to explore it that deeply) is a tutorial to get a "feel" for how the REST API "likes to talk". > Is there another way to preserve these information about the > members? You can query the REST API (you might need to fetch the subscriber roster, then iterate over that to get the details), or you can dump the database table (or the whole database) using SQL-based utilities like psql (Postgres, I forget the MySQL equivalent). > (in general I don't think a lot of people put in effort to > customize there memeberships ... and furthermore they would need to > register, right?) Not sure what you mean by "register", but every address that writes to Mailman gets a temporary user until a "real" user claims it via the mailbox ownership dance. If they receive mail in a mailbox, they've done the ownership dance for that mailbox. If you don't preserve that record, they'll have to do it again. Steve

1 year, 4 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Gerald Vogt

On 23.10.24 00:09, Mark Sapiro wrote: > How are you creating the template? If you are creating it via Postorius, Yes, via Postorius created using the url https://lists.example.org/mailman3/lists/community.lists.example.com/templa… > what is your setting for POSTORIUS_TEMPLATE_BASE_URL and what does the I did not set POSTORIUS_TEMPLATE_BASE_URL in settings.py. > entry in the template table in the database look like? in mailman.template: mailman=# select * from template where id = 6; 6|list:user:action:subscribe|community.lists.example.com|http://localhost:8… in mailmanweb.template: mailmanweb=# select * from postorius_emailtemplate where id = 6; 6|list:user:action:subscribe|test1234||2024-09-09 13:52:22.377792+02|2024-10-14 15:11:43.029873+02|list|community.lists.example.com > POSTORIUS_TEMPLATE_BASE_URL should be the same URL you use to access > Postorius up to but not including the `/postorius/` or `/mailman3/` > part. I.e, for this list whose info page is at https:// > lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/, the > setting is > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` For testing I have set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' to the URL of our main domain, however, if I test an anonymous subscribe through the list info page I still get the timeout error ``` HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) ``` Logs still show the same behaviour: the request for the template comes into the server but is finished and logged after 5 seconds: 127.0.0.1 - - [23/Oct/2024:05:51:38 +0000] "GET /mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3" The tcpdump of the tcp conection also looks the same: the response is pushed with the termination of the connection. I can access http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. So it still looks to me as if the response is stuck in the tcp buffers of the connection and not pushed immediately, but only once the requestor times out after 5 seconds and closes the connection. Thanks, Gerald

6 months, 3 weeks

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Am 02.09.2017 um 01:57 schrieb Mark Sapiro: > On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. > > > > Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> > Recipient filters -> acceptable_aliases. It has nothing to do with > submitters. It is a list of other addresses that can be in the To: or > Cc: of a post to avoid and "implicit destination" hold if the list > posting address is not there. However, the point here is that this bug makes the entire configuration tab unusable. I could live WITHOUT acceptable_aliases. This bug spoils the possibility to set ANY message acceptance settings _easily_. Of course, I can work around: * delete the text field for acceptable aliases before hitting submit * insert a fance @ character there, and give a damn about the fancy stuff mailman3 does with this However, the possibility to make an entire mailing list moderated -- ALL POSTS -- is a central point. Or not? If this is so complicated then one option might be to remove the entire "acceptable aliases" field. It does not work anyway, and spoils other useful things (read: all other settings in the "Message Acceptance" tab) The point is not so much what this particular setting is for, but: it is broken for more than a year now and spoils other useful settings in the configuration dialog that it is located at. The "Message Acceptance" dialog is a central point IMHO. You make have another opinion about that. Cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 8 months

[MM3-users] Re: Archiver "prototype" and disabling archiving at all

by Abhilash Raj

On Thu, Mar 28, 2019, at 9:18 AM, Torge Riedel wrote: > Am 24.03.19 um 16:49 schrieb Mark Sapiro: > > On 3/24/19 5:40 AM, Torge Riedel wrote: > >> in the settings of a mailing list I can choose two archivers: > >> "Hyperkitty" and "prototype". What is this archive "prototype" and how > >> can I disable/remove/deinstall it? And how can I disable archiving at > >> all, so no archiver can be chosen in the settings. > > > > The prototype archiver stores messages individually in > > var/archives/prototype/LIST_NAME/. > > > > You can disable the prototype archiver by putting > > > > [archiver.prototype] > > enable: no > > > > in your mailman.cfg. To disable all archiving, just remove all the > > [archiver.*] sections from your mailman.cfg or set them to 'enable: no' > > > > > Hi Mark, > > thanks. This disabled the archivers, but there is still the "Archives" > link on top of the page. Is it possible to remove it? Cause there is > nothing to see there. I tried commenting "'hyperkitty'," in > INSTALLED_APPS, but then I got a 500. INSTALLED_APPS = ( 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django_gravatar', 'allauth', 'allauth.account', 'allauth.socialaccount', ) This is how it should look like if you want to remove Hyperkitty. There are a few other settings you should remove. https://gitlab.com/mailman/postorius/blob/master/example_project/settings.py This is a Postorius only configuration for reference. > _______________________________________________ > 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, 1 month

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/2/24 03:42, Odhiambo Washington wrote: > > I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. > > I can see from Django Admin UI that the archives are still intact. > > I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke > > Is there a way to move the archives from the old list to the new list? > > > Change the `name` and `list_id` in the list's entry in the > `hyperkitty_mailinglist` table in the database. If there is already an > entry there for the new list, delete it > > ``` mysql> select id, name, list_id from hyperkitty_mailinglist; +----+----------------------------+----------------------------+ | id | name | list_id | +----+----------------------------+----------------------------+ | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | | 2 | list(a)nog.ke | list.nog.ke | | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | | 13 | list(a)lists.nog.ke | list.lists.nog.ke | +----+----------------------------+----------------------------+ 13 rows in set (0.00 sec) mysql> delete from hyperkitty_mailinglist where id = 13; ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) ``` Is there an easier way? I need to delete id=13 then rename id=2 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year

[MM3-users] Re: archiving problem & updates

by Christian Stalberg

I see two messages waiting to be archived. Below is excerpt from the logfile: Feb 10 13:40:49 2021 (974) held message approved, message-id: <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A(a)mail.gmail.com> [10/Feb/2021:13:40:49 +0000] "POST /3.1/lists/ncpoa(a)lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Feb 10 13:40:55 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:55 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M Feb 10 13:40:56 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:56 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:56 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M [10/Feb/2021:13:41:38 +0000] "GET /3.1/domains HTTP/1.1" 200 321 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "GET /3.1/domains/lists.ccalternatives.org HTTP/1.1" 200 216 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "POST /3.1/lists/find HTTP/1.1" 200 1013 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/config HTTP/1.1" 200 3173 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/member/christian%40safecomputing.o rg HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, February 18, 2021 10:33 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: archiving problem & updates On 2/18/21 10:00 AM, Christian Stalberg via Mailman-users wrote: > Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? Start by looking at Mailman's logs and also see if there are messages to be archived in Mailman's var/archives/hyperkitty/spool/ directory. > Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? There are some instructions at <https://docs.mailman3.org/en/latest/upgrade-3.2.html>. Bug fixes are listed in each project's 'news', e.g., <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. html> for Mailman core and <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html> for HyperKitty. -- 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, 2 months

[MM3-users] Re: Mailing list resends same email multiple times

by 朱超

在 2023-03-10 04:54:28，"Mark Sapiro" <mark(a)msapiro.net> 写道： >On 3/9/23 04:18, 朱超 wrote: >> Hello, I need your help. There have question about Scenes: >> >> Add mailbox a and mailbox b to mailing lists c and mailing lists d, and send mail to mailing list c and mailing list d through mailbox b , among which a has received many mails sent by b, check the log and find: The file about path:/opt/mailman /var/queue/bounces has the content of retrying mail, but I turned off process bounces. >> >> Mailing list sends mail via exim, logs found in exim： 023-03-09 00:54:47 1pa4YR-001xk5-0y <= <> R=1pa4YM-001xje-1F U=exim P=local S=7672 T="Mail delivery failed: returning message to sender" from <> > >I need more information. Even though the list isn't brocessing bounces, >bounces will still be returned to the -bounces address and queued in >/opt/mailman/var/queue/bounces. If they remain there, the bounce runner >is not processing them. If the list's bounce processing is turned off, >the bounce runner should just dequeue the message and discard it. > >If multiple messages go to the list, something is returning them to the >list posting address instead of the list-bounces address. > Yes, You are right, I found the real reason and found that someone intercepted the mail sent through the mailing list, and then reposted the mail to the mailing list, resulting in multiple sending of mail. I only need to add spf detection in mta. Thanks Mark. >-- >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 tom_toworld(a)163.com

2 years, 2 months

Search results for query "sapiro"