ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 119 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 118, 119, 120 ... 806, 807, 808 Next

Mon Mar 10 17:58:06 2008

mike cianci

mike2.cianci@comcast.net

Question

Windows

2.7.3

Re: still having email problems

Stefan Ritt wrote:

The transcript below looks all ok to me, so it's most likely that the email went to your Spam folder.

mike cianci wrote:

I no longer get an error message when I try to send an email (I get the "email sent" message) but the email never arrives.

Thank you (in advance) for any help.

My elog.log looks like:

10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} NEW entry #0
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} Email from ELog@desktoppc to mike2.cianci@comcast.net, SMTP host desktoppc
10-Mar-2008 07:05:31 [127.0.0.1] {Centaur} 220 smtp.comcast.net Microsoft ESMTP MAIL Service, Version: 6.0.2600.2180 ready at Mon, 10 Mar 2008 07:05:31 -0800
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur}
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} HELO desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 smtp.comcast.net Hello [192.168.1.101]
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} MAIL FROM: ELog@desktoppc
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.0 ELog@desktoppc....Sender OK
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} RCPT TO: <mike2.cianci@comcast.net>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.1.5 mike2.cianci@comcast.net
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} DATA
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 354 Start mail input; end with <CRLF>.<CRLF>
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} Date: Mon, 10 Mar 2008 07:05:31 -0800
To: mike2.cianci@comcast.net
From: ELog <ELog@desktoppc>
User-Agent: Elog Version 2.7.3
Subject: New ELOG entry
Message-ID: <Centaur-23@desktoppc>
X-Elog-URL: http://localhost:8080/Centaur/23
X-Elog-submit-type: web|elog
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG - Test</title>
<link rel="stylesheet" type="text/css" href="http://localhost:8080/Centaur/default.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body>
<table class="frame" cellpadding="0" cellspacing="0">
<tr><td><table class="listframe" width="100%" cellspacing="0" cellpadding="0">
<tr><td class="title1">
A new ELOG entry has been submitted:</td></tr>
<tr><td class="attribhead">
<input type=hidden name="Author" value="mike">
<input type=hidden name="Instrument" value="Ginger">
<input type=hidden name="Category" value="Problem">
<input type=hidden name="Test" value="General">
<input type=hidden name="Subject" value="Test">
<input type=hidden name=browsing value=1>
Logbook: <b>Centaur</b>  Message ID: <a href="http://localhost:8080/Centaur/23"><b>23</b></a>    Entry time: <b>03/10/08 07:05:31</b>
</td></tr>
<tr><td><table width="100%" cellpadding="0" cellspacing="0"><tr><td nowrap class="attribname">Author:</td><td class="attribvalue">
mike </td>
</tr><tr><td nowrap class="attribname">Instrument:</td><td class="attribvalue">
Ginger </td>
</tr><tr><td nowrap class="attribname">Category:</td><td class="attribvalue">
Problem </td>
</tr><tr><td nowrap class="attribname">Test:</td><td class="attribvalue">
General </td>
</tr><tr><td nowrap class="attribname">Subject:</td><td class="attribvalue">
Test </td>
</tr></table></td></tr>
</table>
</td></tr>
<tr><td class="messageframe"><p>This is a Test</p></td></tr>

</table>
<center><a class="bottomlink" title="Goto ELOG home page" href="https://midas.psi.ch/elog/">ELOG V2.7.3-2058</a></center></body></html>

.
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 250 2.6.0 <Centaur-23@desktoppc> Queued mail for delivery
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} QUIT
10-Mar-2008 07:05:32 [127.0.0.1] {Centaur} 221 2.0.0 smtp.comcast.net Service closing transmission channel

I checked for a spam filter and found none. I have also tried this on three different computers (with different email accounts) and still no luck.

65785

Mon Mar 10 18:31:58 2008

Re: still having email problems

mike cianci wrote:

Stefan Ritt wrote:

The transcript below looks all ok to me, so it's most likely that the email went to your Spam folder.

mike cianci wrote:

I no longer get an error message when I try to send an email (I get the "email sent" message) but the email never arrives.

Thank you (in advance) for any help.

My elog.log looks like:

</table>
<center><a class="bottomlink" title="Goto ELOG home page" href="https://midas.psi.ch/elog/">ELOG V2.7.3-2058</a></center></body></html>

I checked for a spam filter and found none. I have also tried this on three different computers (with different email accounts) and still no luck.

Please use a valid email address for sender. All free email provider don't accept an invalid address, because of security against Spam problem.

Use Email From = xx@xxx.xx

67183

Fri Feb 10 17:18:25 2012

John Doroshenko

doroshenko@physics.rutgers.edu

Olaf Kasten wrote:

Hi there,

I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't connect to the elog server with ssl = 1 in elogd.cfg.

I tested with Firefox 3.6 and IE 7 installations and there are no problems.

I guess it's a bug. Does someone have a suggestion to solve that problem?

Thx. Olaf

Hi!

This just started happening here also. Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome. SAFARI works. Occurs in 2.8.0 and a newly built (even after

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

67184

Sat Feb 11 05:43:33 2012

Andreas Luedeke

andreas.luedeke@psi.ch

John Doroshenko wrote:

Olaf Kasten wrote:

Hi there,

I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't connect to the elog server with ssl = 1 in elogd.cfg.

I tested with Firefox 3.6 and IE 7 installations and there are no problems.

I guess it's a bug. Does someone have a suggestion to solve that problem?

Thx. Olaf

Hi!

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

Hi everyone,

it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong:

Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked.
Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall.

I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host.

To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.

I hope this settles the matter.

Cheers

Andreas

PS: I've solved this with the help of google : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls

67186

Sat Feb 11 22:05:36 2012

Andreas Luedeke wrote:

John Doroshenko wrote:

Olaf Kasten wrote:

Hi there,

I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't connect to the elog server with ssl = 1 in elogd.cfg.

I tested with Firefox 3.6 and IE 7 installations and there are no problems.

I guess it's a bug. Does someone have a suggestion to solve that problem?

Thx. Olaf

Hi!

ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog

with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?

Thanks,

-John

Hi everyone,

it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong:

Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked.
Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall.

I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host.

To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.

I hope this settles the matter.

Cheers

Andreas

⇄

Detect language » English

PS: I've solved this with the help of google : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls

Hi all,

it is NOT the firewall. First off, I don't use a firewall. 2. I AM our computing division. 3. if it were the firewall blocking the access, why do I see "TCP connection broken" in the elog log file? 4. it's not working on port 443 either.

Something's flaky in elog's https implementation. For me it's not a big deal any more, as I use an apache reverse proxy in production now anyway, but other people may not.

thanks,

-Christian

67188

Sat Feb 11 22:19:07 2012

Andreas Luedeke

andreas.luedeke@psi.ch

Christian Herzog wrote:

Andreas Luedeke wrote:

[...]

Hi everyone,

it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong:

Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked.
Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall.

I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host.

To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.

[...]

[...] it is NOT the firewall. First off, I don't use a firewall. 2. I AM our computing division. 3. if it were the firewall blocking the access, why do I see "TCP connection broken" in the elog log file? 4. it's not working on port 443 either.

Something's flaky in elog's https implementation. For me it's not a big deal any more, as I use an apache reverse proxy in production now anyway, but other people may not. [...]

Just for curiosity: did you try to start the non-working web-browser locally on the server?

67189

Sat Feb 11 22:27:15 2012

well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables.

67190

Sat Feb 11 22:37:34 2012

Andreas Luedeke

andreas.luedeke@psi.ch

> well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables.

Strange: I thought I was able to reproduce your problem, but no: whatever browser I try I can access ELOG with SSL if
browser and ELOG are running on the same host. Same as you: clean install but no problem occurs. I haven't tried on a
newer operating system yet. Still I tend to believe that it would not reproduce your problem. Maybe I'll try at home
with ubuntu. Let's first wait what the other two report: if those problems are not related to firewall issues, Stefan
will likely see into it anyway.

Goto page Previous 1, 2, 3 ... 118, 119, 120 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6