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

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/16/2018 09:01 AM, Aymeric Mansoux wrote: > > However, while I was testing this happily on a list that was not affected with the JSON error, I finally tested discard_held_messages() on one of the problematic list, and I get the exact same problem as when trying to view the moderation queue API: > >>>> discard_held_messages_queue('xxx(a)xxx.xxx') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "<console>", line 6, in discard_held_messages_queue > File "/usr/local/lib/python3.5/dist-packages/mailman/app/moderator.py", line 97, in handle_message > key, msgdata = requestdb.get_request(id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > > With that said, even though I cannot pass the discard action, I can export the queue without problem, so I will send you off-list a sample, because I am not sure what I should be looking for. Unfortunately, that didn't help. I was able to post all the messages in your sample to a test list and even with all the messages held, I could view them and discard them in postorius. This may not be too surprising as looking at the traceback, the exception is thrown in trying to delete the pending confirmation from the pending database. The issue is when a message is held an entry is made in the pending database with a confirmation token that can be used for example to approve or discard the message by email. There is an issue that affects MySQL databases only in that prior to the merge of <https://gitlab.com/mailman/mailman/merge_requests/333> values in the pendedkeyvalue table could be truncated (or exceptions thrown depending on MySQL settings). That appears to be the issue here. The fix was only merged in January and is not in Mailman 3.1.1. > Finally, is there another way to get rid of these messages? Are there consequences if I would use message_store.delete_message(message_id) instead of handle_message(m, req.id, Action.discard)? As I said, I think the issue is with the pendedkeyvalue table, not with the message itself. The table contains entries which are pickled versions of various things. A big issue is rule_misses. For one of your messages, the rule_misses list is ['dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation'] this gets pickled into b'\x80\x03]q\x00(X\x10\x00\x00\x00dmarc-mitigationq\x01X\n\x00\x00\x00no-sendersq\x02X\x08\x00\x00\x00approvedq\x03X\t\x00\x00\x00emergencyq\x04X\x04\x00\x00\x00loopq\x05X\x0e\x00\x00\x00banned-addressq\x06X\x11\x00\x00\x00member-moderationq\x07e.' which ultimately gets stored in the pendedkeyvalue table as a value for '_pck_rule_misses' which is '"\u0080\u0003]q\u0000(X\u0010\u0000\u0000\u0000dmarc-mitigationq\u0001X\n\u0000\u0000\u0000no-sendersq\u0002X\b\u0000\u0000\u0000approvedq\u0003X\t\u0000\u0000\u0000emergencyq\u0004X\u0004\u0000\u0000\u0000loopq\u0005X\u000e\u0000\u0000\u0000banned-addressq\u0006X\u0011\u0000\u0000\u0000member-moderationq\u0007e."' Which is longer than the VARCHAR(255) MySQL field for that value prior to <https://gitlab.com/mailman/mailman/merge_requests/333>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and DMARC Mitigate unconditionally to > Yes. > > -- > 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, 9 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Mark Sapiro

On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 10:22 AM, Nathanael Schneider wrote: > > I then created a completely new List which did not exists in mm2.1, > subscribed two addresses and sent myself an EMail. That one worked as > intended. I then deleted the whole broken list and created it cleanly, > added the same two people, sent an email and nothing. This seems strange. If I understand, you are essentially saying the two lists are the same. I.e., you created a completely new List which did not exists in mm2.1, and that one worked. Then you deleted the whole broken list and created it cleanly ... What was different between this cleanly created list and the completely new List? > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net The fact that these are the only messages says that the attempt to send that message via smtp raised no exception as exceptions would have been logged, yet you say there's nothing in the maillog so there was no connect to Postfix. What are your settings for smtp_host: and smtp_port: in the [mta] section of mailman.cfg? ... > I have no clue what to do with this. I then turned the debug module > loglevel to debug. Also nothing useful. Just an endless list of > > [...] > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop > May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 > May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd > May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic > May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction > May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit > May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 > May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > [...] > > Which also tells me nothing I can understand. It says the message in queue entry 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled but gets requeued as 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which presumably is handled and requeued again ... > I have no clue what's > going wrong. (I've turned on debugging both on the original member list > and the reduced member list. Both hang on the first delivery they do). > If I restart mailman, the message gets correctly shunted as it is > interrupted mid-delivery. My maillogs don't register any activity beside > the listpost. Any ideas what I need to do to figure out what's not > working here or where the culprit could be? Not sure if it is related to > the mailinglist being in mailman2.1 before. I have no real understanding of why this isn't working. I don't think it's likely that it has to do with the mailing list being imported from MM 2.1, but I suppose it could be. How did you create and import the list? When you say you deleted the whole broken list and created it cleanly, what did you actually do? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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, 10 months

[MM3-users] Re: hidden list is hidden even to the owner

by Mohsen Masoudfar

As always: Thanks a lot! To answer your question, I am running 1.1.2-3 # apt search postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] Web user interface to access GNU Mailman3 This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, July 1, 2020 5:43 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: hidden list is hidden even to the owner [EXTERNAL EMAIL] On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… and if you are a member as well as owner of an unadvertised list, you will see it at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…. But (here's the tricky part) if you go to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…, you will not see any unadvertised lists, not even ones you own. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 3 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. -- 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> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 11 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Abhilash Raj

On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > On 9/18/19 3:32 AM, Henrik Rasmussen wrote: > > I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). > > > > It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. > > > > I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. > > > I know nothing about Docker containers and how they communicate with > each other, but Postfix is trying to deliver mail via lmtp to > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > listening on port 8024. Either that is not the case or that port is not > exposed to Postfix on IP 172.19.199.2. Right, that is what I was wondering, you verify that by using telnet on the specified IP and Port (172.19.199.2:8024). `docker-compose ps` lists all the running containers, do you see all the containers running? You mentioned that Mailman is not receiving enough emails, do you get *any* emails from Mailman? I am trying to see if this is a perf problem or if Mailman's LMTP isn't reachable at all. > > -- > 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, 1 month

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > 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, 10 months

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Odhiambo Washington

On Thu, Dec 29, 2022 at 2:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 12:22, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 22:00, Odhiambo Washington wrote: > >>> I worke up to 959 such entries in my mailmanweb.log: > >>> > >>> ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The > >>> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > >> ... > >>> > >>> What might have been the cause of this? > >>> > >> > >> Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= > >> 1.3.5 requires mailman-hyperkitty>=1.2.0. > > > Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a > different message so that isn't it. > > There is an issue with Apache. If you search the archives of this list > for the log message you'd find it, but see the last two posts in the > thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > But why these messages all of a sudden? Did you just change something? > I found a mismatch! MAILMAN_ARCHIVER_KEY != api_key A single quote character had sneaked in while copying the key over to the next file. I will watch what happens when the archiver is run next and whether I really need the ' WSGIPassAuthorization On'. Thank you very much as always. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 9 months

Search results for query "sapiro"