Already subscribed to squid-users@squid-cache.org
Hi! This is the ezmlm program. I'm managing the squid-users@squid-cache.org mailing list. I'm working for my owner, who can be reached at squid-users-ow...@squid-cache.org. The address arch...@mail-archive.com was already on the squid-users mailing list when I received your request, and remains a subscriber. If you have trouble posting to the list then please note that the list only accepts plain text email, not HTML email. If you receive a strange error message mentioning multipart/alternative then your email program sends HTML email and must be reconfigured to send plain-text before you can post messages to the list. You will still be able to receive messages via the list however. --- Administrative commands for the squid-users list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: For help and a description of available commands, send a message to: To subscribe to the list, send a message to: To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to: or for the digest to: For addition or removal of addresses, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete the transaction. If you need to get in touch with the human owner of this list, please send a message to: Please include a FORWARDED list message with ALL HEADERS intact to make it easier to help you. --- Enclosed is a copy of the request I received. Return-Path: Received: (qmail 33572 invoked by uid 26); 11 May 2014 05:07:06 - Received: from mail-archive.com (mail-archive.com [72.52.77.8]) by squid-cache.org (8.14.3/8.14.2) with ESMTP id s4B5755r033568 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Sat, 10 May 2014 23:07:06 -0600 (MDT) (envelope-from arch...@mail-archive.com) Received: from archive by mail-archive.com with local (Exim 4.76) (envelope-from ) id 1WjLyc-00055R-3m for squid-users-sc.1399784615.jlglkpckfmmbmjkjijcn-archive=mail-archive@squid-cache.org; Sat, 10 May 2014 22:07:06 -0700 Subject: subscribe To: X-Mailer: mail (GNU Mailutils 2.2) Message-Id: From: The Mail Archive Date: Sat, 10 May 2014 22:07:06 -0700
confirm subscribe to squid-users@squid-cache.org
Hi! This is the ezmlm program. I'm managing the
squid-users@squid-cache.org mailing list.
I'm working for my owner, who can be reached
at squid-users-ow...@squid-cache.org.
This is an automated response from the squid-cache.org list server
to confirm the requested action.
If you did not send the subscribe request below then please ignore
this message and no harm will be done.
To confirm that you would like
arch...@mail-archive.com
added to the squid-users mailing list, please send
an empty reply to this address:
squid-users-sc.1399784615.jlglkpckfmmbmjkjijcn-archive=mail-archive@squid-cache.org
Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.
This confirmation serves two purposes. First, it verifies that I am able
to get mail through to you. Second, it protects you in case someone
forges a subscription request in your name.
--- Administrative commands for the squid-users list ---
I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:
For help and a description of available commands, send a message to:
To subscribe to the list, send a message to:
To remove your address from the list, just send a message to
the address in the ``List-Unsubscribe'' header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
or for the digest to:
For addition or removal of addresses, I'll send a confirmation
message to that address. When you receive it, simply reply to it
to complete the transaction.
If you need to get in touch with the human owner of this list,
please send a message to:
Please include a FORWARDED list message with ALL HEADERS intact
to make it easier to help you.
--- Enclosed is a copy of the request I received.
Return-Path:
Received: (qmail 33123 invoked by uid 26); 11 May 2014 05:03:35 -
Received: from mail-archive.com (mail-archive.com [72.52.77.8])
by squid-cache.org (8.14.3/8.14.2) with ESMTP id s4B53YHo033119
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT)
for ; Sat, 10 May 2014 23:03:35
-0600 (MDT)
(envelope-from arch...@mail-archive.com)
Received: from root by mail-archive.com with local (Exim 4.76)
(envelope-from )
id 1WjLvD-0003HI-2c
for squid-users-subscr...@squid-cache.org; Sat, 10 May 2014 22:03:35
-0700
From: arch...@mail-archive.com
Subject: subscribe
To:
X-Mailer: mail (GNU Mailutils 2.2)
Message-Id:
Date: Sat, 10 May 2014 22:03:35 -0700
subscribe
[squid-users] RE: MedHelp 43953
Canadian Doctor Loretta Blount Best Price On Net March 82% OFF! http://www.google.net/pagead/iclk?sa=l&ai=kzrhz&num=822234&adurl=http://www.sugarfrom.com
Re: [squid-users] SO_FAIL
> actuall i had stable1 and it use to work fine. > i upgrated to stable5, and got this problem It seems that I have the same or a very similar problem: No problems using squid-2.5.STABLE4-20040120 and before. Object are written on disk and logged with SWAPOUT in store.log. Using squid-2.5.STABLE5-20040609 or squid-2.5.STABLE6-20040709 there is always an SO_FAIL entry in store.log and no cache objects are written to disk. Permissions are not the problem. Debugging shows that Squid calculated the dirno to -1 (see storeSwapOutStart): 2004/07/09 15:36:46| storeSwapOut: http://ta-nea.dolnet.gr/data/D2004/D0709/2el10c.gif 2004/07/09 15:36:46| storeSwapOut: store_status = STORE_PENDING 2004/07/09 15:36:46| storeSwapOut: mem->inmem_lo = 0 2004/07/09 15:36:46| storeSwapOut: mem->inmem_hi = 115992 2004/07/09 15:36:46| storeSwapOut: swapout.queue_offset = 0 2004/07/09 15:36:46| storeSwapOut: lowest_offset = 105568 2004/07/09 15:36:46| storeSwapOut: swapout_size = 115992 2004/07/09 15:36:46| storeSwapOutStart: Begin SwapOut 'http://ta-nea.dolnet.gr/data/D2004/D0709/2el10c.gif' to dirno -1, fileno 2004/07/09 15:36:46| storeSwapMetaBuild: http://ta-nea.dolnet.gr/data/D2004/D0709/2el10c.gif 2004/07/09 15:36:46| storeCreate: no valid swapdirs for this object There is only one cache_dir entry in the config file: cache_dir ufs /home/squid/cache 25000 100 256 The configuration file, configure parameters, compiler and operating system are exactly the same. As I can't found a solution, I made a rollback to STABLE4. Operating System: IRIX 6.5.22 System: SGI Origin 200 Compiler: MIPSpro Compilers: Version 7.41 Heiko Heiko Schlichting| Freie Universität Berlin [EMAIL PROTECTED] | Zentraleinrichtung für Datenverarbeitung (ZEDAT) Telefon +49 30 838-54327 | Fabeckstraße 32 Telefax +49 30 838454327 | 14195 Berlin
test
²}¨êelÙé7À~ÏAœ?.a.ô?'šÇî:w»]ÕO!`C!#»ãíUxî(F_¬^u÷Rs¥’Ÿ/p÷0ƒ\X"“}yh—•Ðçæ?ƒ2) )?L”j|ØBé}Wì86õŽ#ƒN¥Ö{²>åwÇ.øçp°V¾Ïó®?×#öG>&½½ÇöyìŠ(É\Žü"Ô&>œùŠà?<"¡UÙ?¢¦ü—$mÇ #išÄ]ýðk…ŒL3„¥?(‡Ö¹X®öQòs'þæ
9‡Mcã(哤8I?~]¬˜Æêâ{ù†§P'«(ÊZT4.Øi~ìÔ27Ã]pÄ_\VsDâáS¡ibDr‚
[D>«„¶ÌaOè?ˆL?Ø;™ïs?ŽX6Hl¨¸Å¾º²dJéãŠò«®!ü»š?–ÔÒ<¢¸îJ§ŒÚ$û¿/Œ’Œ8By?±œgAÙöBÀ{‚‘ðŸ…òìnòš[æS´—kq
UÇÄþ‚lÉÙç?Æä0?xÕ%…ÛfYM°yÆ2ñ0PZö¤XjûŒÀs#±dÛZLR|tǘ[h‚¶
L3âOû]ƒSLá¸tÚlÑ?`QáLÄõ?è'‘Û£ˆv4L«–bœð(·?«¢?•R?~í½jÑ}ŒUÀºhÓ°mí‡#
$ò_ž„ùúqºÐ!ü?r0å¿$}ó¿5‡?¥n© Æ{'>ì?0œÇžš5ó*«ÅPÞv\ƒæÎaþt&·×û«Œ$
¿7™Õû¸#5CWÍ'÷-qé&m-F¥™Ã!#ŠçË·äĆ©Ö7˜·î£[z’'‡²¨ß˜,¡)X4rsåä mS#kîg{EÝlÚéc?Ô]žÀ'ãè³ä
~dô?pÕ ¢DÚ¦Ðþs‘Ä®xO|?—eB¥Ç4š‹õo¶ï}žvxn¹ÒÉ‚;ˆPÞ•Ðí1b»u"¾}ÃS™bâã
ŽœÅñÆ8’ôÒ!Ä]úä,vR8\yçšÖÇ0÷:&ÕÒ¦zÀ¦`Üì^mZ|pó¢ìo§2Œò΂Á$¬Ôq‹}<>
Re: [squid-users] squid_ldap_auth
Ok still stumped, I run the following as asked with the following output: ldapsearch -x -h 10.61.1.248 -b "" -s base "" namingContexts # extended LDIF # # LDAPv3 # base <> with scope base # filter: (objectclass=*) # requesting: namingContexts # # dn: namingContexts: DC=bdmn,DC=foo,DC=com namingContexts: CN=Schema,CN=Configuration,DC=foo,DC=com namingContexts: CN=Configuration,DC=foo,DC=com # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 I then added in my squid conf file, I commented the ncsa_auth line below and added the ldap_auth line. #auth_param basic program /usr/local/squid/bin/squid ncsa_auth /usr/local/squid/etc/passwd auth_param basic program /usr/local/squid/bin/squid_ldap_auth -u cn -b cn=users,dc=bdmn,dc=foo,dc=com 10.61.1.248 auth_param basic children 5 I am still unable to authenticate. I also tried auth_param basic program /usr/local/squid/bin/squid_ldap_auth -b dc=bdmn,dc=foo,dc=com 10.61.1.248 Thanks On Nov 5, 2003, at 10:08 AM, Henrik Nordstrom wrote: On Wed, 5 Nov 2003 [EMAIL PROTECTED] wrote: I could use some guidence configuring my squid installation with a Windows 2000 Active Directory forrest. I have read the past posts as well as the man page. I am very new to LDAP and will admit have not gotten my arms around it yet. My windows domain lives in an Active Directory Forrest my corporate offices mantains. My domain lives at bdmdom.corp.com. I am trying to connect and authenticate against my Exchange server at my location. I have Admin rights over my domain. Can someone please point me in the correct direction or provide the squid config for an LDAP connection to Windows 2000? The first step is figuring out the Base DN of your AD server. This is usually the domain directly translated into dn components dn=bdmdom, dn=corp, dn=com it might also be possible to ask the AD server what it's naming contexts are: ldapsearch -x -h your.ad.server -b "" -s base "" namingContexts then, if your AD allows for anonymous searches you should be able to use the example from the squid_ldap_auth manual as is, just replacing the base DN. If your AD does not allow anonymous searches then a dummy account is needed to be created, and some digging required to find the LDAP name of this account. The LDAP name of the account can probably be found in the MSAD administration tool as a property of the account, if not you can try to guess what it is. Guessing is usually not to hard as there is a very close relation between AD structure and LDAP DN names of objects in that structure, where each container is named with a cn attribute in LDAP. Thus if you have the user "squid" in the container "users" then the LDAP DN of this user should be "cn=squid, cn=users, dc=bdmdom, dn=corp, dn=com". It is strongly adviced to use ldapsearch and other LDAP navigation tools to familarise yourself a little with how the AD looks like via LDAP. Things do get a whole lot more obvious once one has looked at the AD tree via LDAP a little. Regards Henrik
