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

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. There is also the issue that these days some Mail clients will try to create a preview of all the URLs if they can and it would inadvertently GET the URL resulting in the un-subscription. > > -- > 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

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/12/25 12:44, Henry Hartley via Mailman-users wrote: > > Here's what I mean when I say I'm doing this "in venv" > > I've become the mailman user: sudo su - mailman > The .bashrc for that user includes: source /opt/mailman/venv/bin/activate > The prompt has (venv) at the left end of it: (venv) mailman@wz-prd-tpmd-1:~$ So your venv is active. That is good. > All pip commands have been run in this state. I did first install setuptools with apt install python3-setuptools and that installed version 68.1.2-2ubuntu1.2. Which installed it in some /usr/<maybe local here>/lib/pythonxx/dist-packages or maybe site-packages directory which is probably not goint to be consulted by the python in your venv. > Note that I'm still not sure the firewall is completely out of the picture, since I do have to include the --trusted-host and --proxy options. Some things install, though, so I think that's OK. > > When I do this at the (venv) prompt, asking to install both setuptools and mailman-web: > > pip install --proxy http://webproxyta.westat.com:3128 --trusted-host pypi.org setuptools mailman-web > > The first line of the output is: > > Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) So setuptools 80.9.0 is installed in your venv which is good. > And that's followed by downloading (or using a cached version) of 11 items before I get the subprocess error. > > (venv) mailman@wz-prd-tpmd-1:~$ /opt/mailman/venv/bin/pip install --proxy http://webproxyta.westat.com:3128 --trusted-host pypi.org setuptools mailman-web > Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) > Collecting mailman-web > Downloading mailman_web-0.0.9-py3-none-any.whl.metadata (3.2 kB) > Collecting django<4.3,>=4.0 (from mailman-web) > Downloading django-4.2.23-py3-none-any.whl.metadata (4.2 kB) > Collecting hyperkitty (from mailman-web) > Downloading hyperkitty-1.3.12-py3-none-any.whl.metadata (3.6 kB) > Collecting postorius (from mailman-web) > Downloading postorius-1.3.13-py3-none-any.whl.metadata (2.9 kB) > Collecting whoosh (from mailman-web) > Downloading Whoosh-2.7.4-py2.py3-none-any.whl.metadata (3.1 kB) > Collecting asgiref<4,>=3.6.0 (from django<4.3,>=4.0->mailman-web) > Downloading asgiref-3.8.1-py3-none-any.whl.metadata (9.3 kB) > Collecting sqlparse>=0.3.1 (from django<4.3,>=4.0->mailman-web) > Downloading sqlparse-0.5.3-py3-none-any.whl.metadata (3.9 kB) > Collecting django-compressor>=1.3 (from hyperkitty->mailman-web) > Downloading django_compressor-4.5.1-py2.py3-none-any.whl.metadata (5.0 kB) > Collecting django-extensions>=1.3.7 (from hyperkitty->mailman-web) > Downloading django_extensions-4.1-py3-none-any.whl.metadata (6.1 kB) > Collecting django-gravatar2>=1.0.6 (from hyperkitty->mailman-web) > Downloading django_gravatar2-1.4.5-py2.py3-none-any.whl.metadata (4.3 kB) > Collecting django-haystack>=2.8.0 (from hyperkitty->mailman-web) > Downloading django_haystack-3.3.0.tar.gz (467 kB) > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 467.3/467.3 kB 22.3 MB/s eta 0:00:00 The above is collecting mailman-web and its dependencies. > Installing build dependencies ... error > error: subprocess-exited-with-error > > × pip subprocess to install build dependencies did not run successfully. > │ exit code: 1 > ╰─> [2 lines of output] > ERROR: Could not find a version that satisfies the requirement setuptools>=61.2 (from versions: none) > ERROR: No matching distribution found for setuptools>=61.2 > [end of output] > > note: This error originates from a subprocess, and is likely not a problem with pip. > error: subprocess-exited-with-error > > × pip subprocess to install build dependencies did not run successfully. > │ exit code: 1 > ╰─> See above for output. > > note: This error originates from a subprocess, and is likely not a problem with pip. And this is all from a pip subprocess which is trying to build install build dependencies. I.e., this error is not necessarily related to django-haystack or any other specific package, but is saying it can't find a setuptools package to satisfy the build requirements. This in turn may be that the subprocess doesn't see your --proxy option. I think the issue may be that normally pip installs build requirements in an isolated temporary directory so as not to create potential conflicts with installed packages. See <https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-…>. Specifying --no-build-isolation on the pip command will disable this. See <https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-no-build-isolation>. If you specify --no-build-isolation on the pip command, it should use setuptools and wheel from your venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

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

by Onyeibo Oku

On Wed, 12 Oct 2022 17:52:47 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: Thanks Eggert and Sapiro. > > As Eggert suggests, see > https://docs.mailman3.org/en/latest/install/virtualenv.html and > follow that. I already started out on the above route. Its an adaptation because I am running Fedora. I had no problem with system-wide installations via dnf package management. However, some parts of the documentation does not add up. > You don't need to download the source from GitLab. > Following that doc will get the latest releases from PyPI via pip. > Those are still somewhat out of date - we really should make new > releases - so if you want the latest from GitLab, there are a couple > of ways to do it. Perhaps the easiest is to just run the various `pip > install` commands as documented and then upgrade Mailman core in your > venv with ``` > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > ``` > and update the various mailman web packages with > ``` > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > ``` > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > postorius, hyperkitty. I.e., run it 5 times, once for each value of > xxx. > I will come to this eventually (assuming that does not break things later). I aim to get it all working with regular pip packages first. I have installed mailman core already. Fedora expects mailman files to reside at /usr/lib/mailman. It appears to ship with a mailman unix user. I adapted to those system defaults. Now I observe that "su - mailman" gives me the proper prompt but .bashrc doesn't kick in. I still have to manually change to the virtual environment despite setting the automatic change in .bashrc. However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". Is this normal? Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which should correspond to "/usr/lib/mailman/mm/var/*" on my instance. However, I don't see any instructions on how to get the "/mm" folder and the associated sub-folders. I just have "/usr/lib/mailman" I am lost "pip list" within the venv environment confirms that I have "mailman 3.3.5". What am I missing? Regards Onyeibo

3 years, 10 months

[MM3-users] Re: How to fix lists with characters errors?

by Helio Loureiro

Hi, it is python 3.10. Problem is... some mailing lists were created long ago, with python2 something. Most probably 2.5. And the tables on mysql were set to latin1. That I know. Question now is how to fix this. Any suggestion? What is the table? I probably can run some script for these specific lists that have the failure, import data as latim-1, and update back to the table as utf-8. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 20:53, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/22/24 05:37, Helio Loureiro wrote: > > Hi, > > > > I just found several lists have the issue like this regarding charset: > > > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members > ... > > Traceback (most recent call last): > ... > > line 109, in display_members > > print(f'{address.display_name} <{address.original_email}>', > > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > > position 9: ordinal not in range(256) > > > There is something in your python that has set the encoding for stdout > to latin1 instead of the default utf-8. E.g. > ``` > $ python3.10 > Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> name = 'abc\u0142def' > >>> print (f'{name}') > abcłdef > >>> import sys > >>> sys.stdout.reconfigure(encoding='latin1') > >>> print (f'{name}') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 3: ordinal not in range(256) > >>> > ``` > > -- > 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 helio(a)loureiro.eng.br >

2 years, 4 months

[MM3-users] Re: Speed/progress of update_index_one_list?

by Philip Colmer

We've now completed the indexing of our lists, some of which are quite large (100K+ messages per list). I wanted to share our findings of using Xapian to do this. Firstly, using "-v 2", e.g. "mailman-web update_index_one_list -v 2 <email address>", causes the command to print out the progress being made in batches of 1,000 messages. Secondly, Xapian is single-threaded. It only allows one writer at a time. Therefore, we focussed on speed of the hard drives and, on the advice received from the Xapian list, memory. Since we were using AWS EC2 with EBS storage, I elected to move the EBS storage from gp2 to gp3 - which has a higher base I/O figure - and I selected a r6i.8xlarge as this guaranteed 10Gb throughput to the EBS storage. It also delivered 32 vCPU and 256GB RAM. It was possibly overkill but it did the job (see below) and we've now switched back to a t3a.xlarge. Speed-wise, with the above configuration, the system indexed a list of nearly 85K messages in 46 minutes. I hope that is helpful information to anyone else who finds themselves migrating large Mailman 2 archives. Regards Philip On Fri, 14 Jan 2022 at 17:33, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/22 12:38 AM, Philip Colmer wrote: > > I have now switched to Xapian but, in a way, my original questions still > > stand. Is there a way of monitoring the progress of > > "update_index_one_list"? What can I do to the specification of the server > > to make that process go (much) faster? > > > > HyperKitty does the indexing by calling the Haystack update_index > command. See > > https://django-haystack.readthedocs.io/en/master/management_commands.html#u… > > This command has options such as --verbosity and --workers. I think > verbosity is set from the option provided to update_index_one_list and > if set to 2 will give some progress info. > > workers could increase parallelism but is unconditionally passed by > hyperkitty as 0 > > > -- > 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, 6 months

[MM3-users] Re: Another interesting error...

by Darren Smith

OK chalk another one up to a python newbie... commit() was the magic sauce that we needed. The error 500 is no longer happening on that mailing list. We have three different lists so far that have gotten into this state, and we are going to work on the other two to make sure that this all works. FYI if this is fixed somehow in a later release (later than 3.1.0) we are working on migrating to the latest mailman code. -Darren On Mon, Apr 23, 2018 at 4:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 02:59 PM, Darren Smith wrote: > > Well, using the mailman shell we were able to find the request that was > > causing the problem - it was apparently a spam message that had some > > chinese characters in it. > > > I am trying to duplicate this issue in a test environment. I can create > a message with an invalid RFC 2047 encoded subject, i.e., > > Subject: =?gb2312?Q?=ff=fe=de=21=a2?= > > and send it to a list where it gets held, but I don't get a 500 in > postorius and I see the held message with a raw (not decoded) header. > > I think there were some recent changes that affect this. I'll look some > more. > > > > We used the shell to delete the held request... > > > > And postorius is still giving me an error 500. > > > > If I'm not mistaken the held messages are kept in .pck files - do you > know > > if when postorius asks for held messages through the API, does mailman go > > to the database or to the .pck? I would actually suspect the latter, or > > removing the request should have fixed the problem. > > > They were held in .pck files in Mailman 2.1, but not in Mailman 3. They > should just be in the database and deleting them via mailman shell > should delete them as long as you quit the shell or commit(). > > -- > 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/ >

8 years, 3 months

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Abhilash Raj

On Wed, Apr 17, 2019, at 8:18 AM, Mark Sapiro wrote: > On 4/17/19 8:10 AM, Abhilash Raj wrote: > > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: > >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: > >>> > >>> Which version of Hyperkitty are you using? > >>> > >>> Did you upgrade the version of Hyperkitty when you migrated to the > >>> new host? > >> > >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple > >> releases), so it's hyperkitty 1.1.4. > >> > >> I didn't upgrade anything with the move. > > > > I am not sure where does Debian packaged version store it's fulltext index, but > > I am assuming the move somehow makes Hyperkitty not be able to read the > > index. > > > I think this is a known incompatibility between the Python 2.7 and > Python 3 versions of Whoosh. I *think* 1.1.x releases were based on Python 2.7, so that part looks right to me. > > From the tracebacks, the current HyperKitty is running under Python 2.7. > If the prior server was running HyperKitty with Python 3, that would > explain this. Given that 1.1.x supports only 2.7 and Ubuntu doesn't have 1.2 release, it is unlikely Python 3 was used. > > > Can you try removing and re-building the entire index? I don't know again > > the right command for Django there, but the hyperkitty command you want > > to run is called `rebuild_index`. For source package, something like: > > > > $ python manage.py rebuild_index > > > > Do note that this will take a lot of time if you have a big archive. > > > If this is the incompatibility, rebuilding the index will fix it. > > -- > 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)

7 years, 4 months

[MM3-users] Re: including a template failed

by Wolfgang Bock

Dear Mark, Q: Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? A: No Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? A: was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Now another problem occurs: Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool ... 'localhost' doesn't match either of 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', 'domain-04.de', 'www.domain-04.de'"))) Port 25 entry results from the manual regarding the postfix configuration: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml e.g.: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 01:05 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: including a template failed On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the > following errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on > port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max > retries exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list: > member :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to > establish a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- 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/

5 years, 10 months

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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/

5 years

[MM3-users] Re: update_index

by Darren Smith

OK - next issue...here's the warning that I'm receiving when I run that: /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date received a naive datetime (2018-04-03 07:51:25) while time zone support is active. RuntimeWarning) I'm not sure that anything else occurred. The indexing took 2 seconds, and there have been tens of thousands of emails imported since the last index. Thoughts? -Darren On Tue, Apr 3, 2018 at 10:55 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Holy cow I think that's exactly what the problem is. I will give that a > try and let you know what happens! > > On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/03/2018 09:02 AM, Darren Smith wrote: >> > Hello, >> > >> > If I'm reading the docs correctly, when we run manage.py update_index, >> it >> > should be an incremental index of new emails that have been added since >> the >> > last time update_index was run - can anyone confirm that this is the >> > expected behavior? Or is there another command line option that I am >> > missing? >> >> >> There are two ways to run update_index. >> >> Hyperkitty's update_index is incremental and is run by >> >> manage.py runjob update_index >> >> Running >> >> manage.py update_index >> >> runs haystack's update_index which with no options does a full update. Run >> >> manage.py update_index --help >> >> to see the options. The incremental 'manage.py runjob update_index' >> should be run every minute by 'manage.py runjobs minutely' assuming cron >> is running the periodic Django jobs, so running either update_index job >> manually shouldn't be necessary >> >> >> ... >> > So...can anyone help with how to get the update_index to do only emails >> > added since the last time the update_index was run? >> >> >> manage.py runjob update_index >> >> -- >> 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/ >> > >

8 years, 4 months

Search results for query "sapiro"