Re: [Zope] MailBoxer Problem Found...But Not Solved

2006-09-05 Thread Dieter Maurer 
beno wrote at 2006-9-4 16:41 -0400:
> ...
>Frankly, I though (and still suspect) that the fact that the site 
>2012.vi:7080 doesn't resolve because of the Pound/Squid/Zope interface 
>but 202.71.106.119:7080 does combined with the fact that I have to send 
>my email to [EMAIL PROTECTED] (mail being the SMTP) was causing the 
>problem.

What does "not resolve" mean precisely (you need to be *VERY* precise
when you report problems)?

As you use it, one would repect a DNS (Domain Name Service) problem:

It is the task of the DNS to resolve "2012.vi" into its IP address
(apparently 202.71.106.119).

If you are using virtual hosting (I do not know the Pound details,
only that of Apache), then additional requirements (beside
a working DNS) may be necessary. For Apache named virtual hosts,
e.g., not only the external DNS must map the name to the IP address
but the internal DNS as well.

> ...
>Where else should I be looking?

Maybe, you look in your neighbourhood whether you find
a knowledgable person, pay his travel to visit you and
help you in setting up the system.

There are cases, where a mailing list cannot solve all problems
and direct personal interaction becomes necessary...



-- 
Dieter
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] MailBoxer Problem Found...But Not Solved

2006-09-05 Thread Chris Withers 

beno wrote:
down. Frankly, I though (and still suspect) that the fact that the site 
2012.vi:7080 doesn't resolve because of the Pound/Squid/Zope interface 


name resolution has fuckall to do with Pound, Squid or Zope.

but 202.71.106.119:7080 does combined with the fact that I have to send 


202.71.106.119 is an ip address, therefore no name resolution is necessary.


with no luck. Where else should I be looking?


If you removed your head from your arse you might see a lot more...

*sigh*

Chris

--
Simplistix - Content Management, Zope & Python Consulting
   - http://www.simplistix.co.uk
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] MailBoxer Problem Found...But Not Solved

2006-09-05 Thread Chris Withers 

beno wrote:

Request URL http://202.71.106.119:7080/error_log/manage_workspace
Exception Type Redirect
Exception Value http://202.71.106.119:7080/error_log/manage_main



Now, that error is definitely from the email I sent. 


Bull. Although I'd be amused to see how you figured that...
Check the above urls, this is a request by you to Zope's ZMI that got 
redirected to the manage_main. In fact, it's you looking at the error 
log itself.


*sigh*


* I don't use Apache,


That's because you're an idiot. I have half a mind just to hack your 
server to prove a point. Nice of you to tell the entire list the IP and 
port where it's running...


and I'd rather not have to if I can get away with 
it. Just one more program to maintain.


Ah, lazy AND stupid. You should become a politician.


* I use Pound on my front end,


Yes, that'd be the "stupid" coming out again.

* As a result, if I want to send requests *directly* to Zope, I need to 
use the IP address. 


...which really should be firewalled off for everything other than 
localhost.


   rejoice: "|smtp2zope.py 
http://202.71.106.119:7080/rejoice.2012.vi/rejoice/manage_mailboxer 2"


Have you actually thought to check your qmail logs to see what it thinks 
is happening?


Apparently, MailBoxer doesn't like that. Apparently, it wants a web 
address, like rejoice.2012.vi, in my case. But that won't get past Pound 
:( What do? Which file should I hack to get it to accept the IP address?


The fact that MailBoxer wants to do an HTTP post like this to add a 
message is, quite frankly, scary and should make you run far away from 
it for starters.


Of course, you could just use mailman, but hey, far be it for you to 
actually listen to the advice of anyone on the lists you keep pestering.


Chris

--
Simplistix - Content Management, Zope & Python Consulting
   - http://www.simplistix.co.uk
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] MailBoxer Problem Found...But Not Solved

2006-09-04 Thread beno 

Dieter Maurer wrote:

beno wrote at 2006-9-4 10:24 -0400:
  
I believe I have traced the mailboxer problem I am having. I have caught 
the following seemingly innocuous error in the ZMI error log:


Time2006/09/04 14:16:02.371 Universal
User Name (User Id) beno (beno)
Request URL http://202.71.106.119:7080/error_log/manage_workspace
Exception Type  Redirect
Exception Value http://202.71.106.119:7080/error_log/manage_main



Not sure whether I already told *you* (or someone else) that
"Redirect" exceptions are *NORAML* behaviour and no error conditions
*AT ALL*.

Thus, reconfigure your "error_log" to ignore "Redirect" and
forget about any error analysis for them
  
I've done as you suggested. That being the case, however, I'm back to 
square one. Now, all the how-to's I've read on MailBoxer indicate it's 
easy to set up. Therefore, that suggests the problem I'm experiencing is 
probably rooted in something different about my system. The most logical 
difference to me is Pound. But it could be a combination of things, such 
as Pound, Qmail, Squid and FreeBSD. At any rate, I need to track this 
down. Frankly, I though (and still suspect) that the fact that the site 
2012.vi:7080 doesn't resolve because of the Pound/Squid/Zope interface 
but 202.71.106.119:7080 does combined with the fact that I have to send 
my email to [EMAIL PROTECTED] (mail being the SMTP) was causing the 
problem. But what I really need is to catch an error, and so far I 
haven't been able to. I've looked in

Z2.log
events.log
/var/log/squid/cache.log
/var/log/messages
/var/log/qmail/qmail-send/current
qmail-smtp/current
qmail-pop3/current
with no luck. Where else should I be looking?
TIA,
beno
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] MailBoxer Problem Found...But Not Solved

2006-09-04 Thread Dieter Maurer 
beno wrote at 2006-9-4 10:24 -0400:
>I believe I have traced the mailboxer problem I am having. I have caught 
>the following seemingly innocuous error in the ZMI error log:
>
>Time   2006/09/04 14:16:02.371 Universal
>User Name (User Id)beno (beno)
>Request URLhttp://202.71.106.119:7080/error_log/manage_workspace
>Exception Type Redirect
>Exception Valuehttp://202.71.106.119:7080/error_log/manage_main

Not sure whether I already told *you* (or someone else) that
"Redirect" exceptions are *NORAML* behaviour and no error conditions
*AT ALL*.

Thus, reconfigure your "error_log" to ignore "Redirect" and
forget about any error analysis for them



-- 
Dieter
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] MailBoxer Problem Found...But Not Solved

2006-09-04 Thread beno 

Hi;
I believe I have traced the mailboxer problem I am having. I have caught 
the following seemingly innocuous error in the ZMI error log:


Time2006/09/04 14:16:02.371 Universal
User Name (User Id) beno (beno)
Request URL http://202.71.106.119:7080/error_log/manage_workspace
Exception Type  Redirect
Exception Value http://202.71.106.119:7080/error_log/manage_main

Traceback (innermost last):

   * Module ZPublisher.Publish, line 101, in publish
   * Module ZPublisher.mapply, line 88, in mapply
   * Module ZPublisher.Publish, line 39, in call_object
   * Module App.Management, line 85, in manage_workspace

Redirect: http://202.71.106.119:7080/error_log/manage_main

Display traceback as text59 



51


 REQUEST


 form


 cookies

dtpref_rows '20'
dtpref_cols '95%'
tree-s  'eJzTyCkw5NLIKTDiClZ3hANPW3WuAmOuxEQ9AIO2B9g'
_ZopeId '79820811A2fzfXbQQGY'


 lazy items

SESSION 	>



 other

TraversalRequestNameStack   []
AUTHENTICATED_USER  beno
URL 'http://202.71.106.119:7080/error_log/manage_workspace'
SERVER_URL  'http://202.71.106.119:7080'
AUTHENTICATION_PATH ''
PUBLISHED 	at /error_log>>

URL1'http://202.71.106.119:7080/error_log'
ACTUAL_URL  'http://202.71.106.119:7080/error_log/manage_workspace'
URL0http://202.71.106.119:7080/error_log/manage_workspace
URL1http://202.71.106.119:7080/error_log
URL2http://202.71.106.119:7080
BASE0   http://202.71.106.119:7080
BASE1   http://202.71.106.119:7080
BASE2   http://202.71.106.119:7080/error_log
BASE3   http://202.71.106.119:7080/error_log/manage_workspace


 environ

HTTP_COOKIE 	'dtpref_cols="95%"; dtpref_rows="20"; 
tree-s="eJzTyCkw5NLIKTDiClZ3hANPW3WuAmOuxEQ9AIO2B9g"; 
_ZopeId="79820811A2fzfXbQQGY"'
SERVER_SOFTWARE 	'Zope/(Zope 2.7.8-final, python 2.3.5, freebsd5) 
ZServer/1.1 Plone/Unknown'

SCRIPT_NAME ''
REQUEST_METHOD  'GET'
PATH_INFO   '/error_log/manage_workspace'
SERVER_PROTOCOL 'HTTP/1.1'
channel.creation_time   1157378993
CONNECTION_TYPE 'keep-alive'
HTTP_ACCEPT_CHARSET 'ISO-8859-1,utf-8;q=0.7,*;q=0.7'
HTTP_USER_AGENT 	'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6'

HTTP_REFERER'http://202.71.106.119:7080/error_log/manage_main'
SERVER_NAME 'localhost.web.vi'
REMOTE_ADDR '67.46.93.3'
PATH_TRANSLATED '/error_log/manage_workspace'
SERVER_PORT '7080'
HTTP_HOST   '202.71.106.119:7080'
HTTP_ACCEPT 
'text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5' 


GATEWAY_INTERFACE   'CGI/1.1'
HTTP_ACCEPT_LANGUAGE'en-us,en;q=0.5'
HTTP_ACCEPT_ENCODING'gzip,deflate'
HTTP_KEEP_ALIVE '300'


Now, that error is definitely from the email I sent. Even the 
REMOTE_ADDR matches. Here's where the problem arises:
* I don't use Apache, and I'd rather not have to if I can get away with 
it. Just one more program to maintain.
* I use Pound on my front end, which passes requests to Squid, which in 
turn passes them to Zope. This is a pretty common procedure for people 
using Pound/Zope.
* As a result, if I want to send requests *directly* to Zope, I need to 
use the IP address. That's why I've entered the following in my 
/etc/aliases file (which is also now in my 
/var/qmail/aliases/.qmail-l33tm4il file, which one how-to said to use if 
qmail is your mail server, as mine is):
   rejoice: "|smtp2zope.py 
http://202.71.106.119:7080/rejoice.2012.vi/rejoice/manage_mailboxer 2"


Apparently, MailBoxer doesn't like that. Apparently, it wants a web 
address, like rejoice.2012.vi, in my case. But that won't get past Pound 
:( What do? Which file should I hack to get it to accept the IP address?

TIA,
beno
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )