Attributes = Author, Type, Category, Subject, Revisions
Show Attributes = Author, Type, Category, Subject, Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject

Attributes = Author, Type, Category, Subject
Show Attributes = Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject

(abc|def).*(abc|def)

(abc.*def)|(def.*abc)

I think I found out what the problem was and e-mail notification now works.

Apparently 'MAIL FROM' syntax used by my ISP expects the address to be within <>.

Adding those in the config file fixes the problem:

Use Email From = <user@domain>

Note that the documentation indicates that the brackets should not be there and I'm not sure if this is a bug or not yet. According to this link the brackets should be there but I think to be consistent with other e-mail related attributes in the config file, they should be added by ELOG.

The 'Email' attibute however seems to work fine without the brackests. I.e.

Email All = user@doman

is OK.

I'm not very familiar with SMTP but I was fiddling around with this some time ago setting up a postfix MT. I eventually succeeded with my ISP, but not with gmail's SMTP. Apperently there are differences with the log-in procedure.

Maybe various differences in login procedure could be handled by allowing ELOG to optionally to use an external program like mailto to handle it's mailing?

SMTP external = 0|1

I think I understand (and actually appreciate) the policy of not depending on external programs. Just a suggestion...

BR

/Michael

Stefan,

To solve the problem I suggest following change to elogd.c (2.7.5 2159).

Create a list of elog cookies, and store only these as parameters. Example diff:

---
$ diff elog/src/elogd.c elogd_niho.c
26557a26558
>    const char *cookie_list[] = { "upwd", "unm", "elmode", "urem", "wpwd", "apwd", "uname", NULL };
26603c26604,26610
<          setparam(str, cookie);
---
>          for(i=0; cookie_list[i]; i++) {
>             if(strcmp(cookie_list[i], str) == 0) {
>                setparam(str, cookie);
>                break;
>             }
>          }
>
---

In a more readable fashion:
int process_http_request(const char *request, int i_conn)
{
...
const char *cookie_list[] = { "upwd", "unm", "elmode", "urem", "wpwd", "apwd", "uname", NULL };
...
...
...
         /* store cookie as parameter */
         for(i=0; cookie_list[i]; i++) {
            if(strcmp(cookie_list[i], str) == 0) {
               setparam(str, cookie);
               break;
            }
         }

...

Not sure if I got all the cookies used by elog.

BR, niklas

An update:

I got rid of the version from the Ubuntu repo and installed the latest source release instead (2.7.5-2130).

The error is now a little bit different:

Error sending Email via "smtp.glocalnet.net": Syntax error in parameters or arguments to MAIL command

A snippet from the console output:

250-DELIVERBY 300
250 SIZE
AUTH LOGIN
`±è·    ♦Username:
cmhqNzY0aEB0bmluZXQuc2U=
Password:
ajh6N2E4
235 LOGIN authentication successful
MAIL FROM: theproject@kato.homelinux.org
501 Syntax error in parameters or arguments to MAIL command
==== Return ================================

BR /Michael

Hello, I'm having problems with e-mail notifications.

When I try submitting a new post, I get the following error:

Error sending Email via "smtp.glocalnet.net"

The error message doesn't give a lot of hints...

My config file contains the following lines:

[global]
SMTP host = smtp.glocalnet.net
SMTP username = rhj764h@tninet.se
SMTP Password = xxx

...

[BugZ]

...

Email All = somebody@gmail.com
Use Email From = theproject@kato.homelinux.org

The password was created by invoking elogd with the -t option containing the true password. I've tried enter the correct password manually in the config, but the error message is the same.

Below follows a cut&paste of the console output when invoking with the -v option (addresses manually edited to avoid spam):

Email ALL to somebody@gmail.com

timezone: -3600, offset: 3600


Email from theproject@kato.homelinux.org to somebody@gmail.com, SMTP host smtp
.glocalnet.net:
220 mta3.glocalnet.net ESMTP Service ready
EHLO kato.homelinux.org
250-mta3.glocalnet.net
250-DSN
250-8BITMIME
250-PIPELINING
250-HELP
250-AUTH=LOGIN
250-AUTH LOGIN CRAM-MD5 PLAIN
250-X-CP-DELIVER-AFTER
250-DELIVERBY 300
250 SIZE
==== Return ================================
HTTP/1.1 302 Found
Server: ELOG HTTP 2.6.3-1762
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Location: http://kato.homelinux.org/elog-tinker/BugZ/6?error=Error+sending+Email
+via+<i>"smtp.glocalnet.net"</i>
Content-Length: 20

I can't make any sense of this. Please advise.

Regards

/Michael Ambrus

> > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > > 
> > > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > > Is is possible the corporate elog server is running behind apache or in some
> > > > other proxy config while the one you are having issues with is being connected
> > > > to directly by chrome?
> > >
> > > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > > URL to Google Chrome developers to see if it's a bug in the browser or not.
> > 
> > I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> > was some sort of cookie issue IIRC the log entry.
> > 
> > So build a new elogd and you should be all set.
> > 
> > - rouilj
> 
> Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

I installed the latest Windows build (didn't realize I missed a build in November), and it now works in Chrome.  Thanks!

> > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > 
> > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > Is is possible the corporate elog server is running behind apache or in some
> > > other proxy config while the one you are having issues with is being connected
> > > to directly by chrome?
> >
> > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > URL to Google Chrome developers to see if it's a bug in the browser or not.
> 
> I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> was some sort of cookie issue IIRC the log entry.
> 
> So build a new elogd and you should be all set.
> 
> - rouilj

Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.