Howto force users to supply an email address when registering?, posted by Johan Nyberg on Thu Oct 20 14:15:14 2005
|
Hi,
Today I noticed that a user had registered without supplying an email address. I am using Self Register = 3, which means I recieve an email from elogd when a new user wants to register. Apparently, I forgot to check that the users email field was empty. This empty email field led to a situation in which no email notifications were sent to the users. The elogd log file looks like this for a user with a registered email address:
20-Oct-2005 12:20:21 [<snip>] {AGATA SDA} RCPT TO: <johan.nyberg@tsl.uu.se>
20-Oct-2005 12:20:21 [<snip>] {AGATA SDA} 250 Ok
while it looks like this for a user with an epmty email address:
20-Oct-2005 12:20:22 [<snip>] {AGATA SDA} RCPT TO: <>
20-Oct-2005 12:20:22 [<snip>] {AGATA SDA} 501 Bad address syntax
When elogd hits this error it stops the process of sending emails, which means that no emails
at all are sent to any of the users. After manually adding the email address of the user with an empty address,
automatic email notification work again.
Is there a way to force the users to supply an email address when they register?
Johan |
Re: Howto force users to supply an email address when registering?, posted by Stefan Ritt on Thu Oct 20 16:01:49 2005
|
| Johan Nyberg wrote: | | Is there a way to force the users to supply an email address when they register? |
I will happily implement such an email check if you supply me further information. Presume you enter an email address in the form user#domain.com (# instead @). Does your SMPT server then complain, too? What about user@com (without "domain.")? If you check all possibilities and let me know, I will put it in. |
|
Re: Howto force users to supply an email address when registering?, posted by Johan Nyberg on Sat Oct 22 00:21:03 2005
|
| Stefan Ritt wrote: |
| Johan Nyberg wrote: | | Is there a way to force the users to supply an email address when they register? |
I will happily implement such an email check if you supply me further information. Presume you enter an email address in the form user#domain.com (# instead @). Does your SMPT server then complain, too? What about user@com (without "domain.")? If you check all possibilities and let me know, I will put it in. |
Hi Stefan,
Sorry for the delayed reply. I have run some tests which I will send to you by email.
Johan |
|
Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Sun Oct 16 10:33:23 2005
|
Hi all, I get messages like this
Attachment #16 of entry #0 not found
Please use your browser's back button to go back
always when clicking on an entry in summary or threaded view. I can only read entries when browsing them in full view. How can i fix this?
regards, Christian |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Stefan Ritt on Mon Oct 17 10:18:29 2005
|
> Hi all, I get messages like this
> Attachment #16 of entry #0 not found
> Please use your browser's back button to go back
> always when clicking on an entry in summary or threaded view.
> I can only read entries when browsing them in full view. How can i fix this?
> regards, Christian
I need some more information. Can you send me your elogd.cfg, and show
me the URLs your browser displays during your navigation? |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Tue Oct 18 08:02:44 2005
|
> > Hi all, I get messages like this
> > Attachment #16 of entry #0 not found
> > Please use your browser's back button to go back
> > always when clicking on an entry in summary or threaded view.
> > I can only read entries when browsing them in full view. How can i fix this?
> > regards, Christian
>
> I need some more information. Can you send me your elogd.cfg, and show
> me the URLs your browser displays during your navigation?
Well, this is my elog.conf:
[global]
logbook tabs = 1
port = 8081 ; Automatically added in installation.
Hosts allow = localhost, jazz.cocis.de, 127.0.0.1, 192.168.
Hosts deny = ALL
[debian]
Theme = default
Comment = debian logbook
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Subst Author = $long_name
Subst Email = $user_email
Locked Attributes = Last Revision
Subst on Edit Last Revision = $date by $long_name
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Password file = /var/lib/elog/elogpasswd.pwd
Admin user = admin
Reverse sort = 1
Restrict edit = 1
Suppress Email to users = 1
This is the URL after logging in:
http://localhost:8081/debian/17?cmd=List&mode=summary
When i click on one of the entrys, i get thar error message.
URL: http://localhost:8081/debian/debian/17
It says: "Attachment #17 of entry #0 not found
Please use your browser's back button to go back"
regards, Christian |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Stefan Ritt on Tue Oct 18 08:04:29 2005
|
> This is the URL after logging in:
> http://localhost:8081/debian/17?cmd=List&mode=summary
>
> When i click on one of the entrys, i get thar error message.
> URL: http://localhost:8081/debian/debian/17
>
> It says: "Attachment #17 of entry #0 not found
> Please use your browser's back button to go back"
Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
- Stefan |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Tue Oct 18 18:13:57 2005
|
> > This is the URL after logging in:
> > http://localhost:8081/debian/17?cmd=List&mode=summary
> >
> > When i click on one of the entrys, i get thar error message.
> > URL: http://localhost:8081/debian/debian/17
> >
> > It says: "Attachment #17 of entry #0 not found
> > Please use your browser's back button to go back"
>
> Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
>
> - Stefan
Stefan,
where can we get Beta5, I can only find Beta4 on all the download locations.
-Charles- |
|
Re: Error message: "Attachment #6 of entry #0 not found", posted by Charles Duncan on Wed Oct 19 15:44:07 2005
|
> > > This is the URL after logging in:
> > > http://localhost:8081/debian/17?cmd=List&mode=summary
> > >
> > > When i click on one of the entrys, i get thar error message.
> > > URL: http://localhost:8081/debian/debian/17
> > >
> > > It says: "Attachment #17 of entry #0 not found
> > > Please use your browser's back button to go back"
> >
> > Ah, now I recognize the error. Please update to the newest beta5, it's fixed there.
> >
> > - Stefan
>
> Stefan,
>
> where can we get Beta5, I can only find Beta4 on all the download locations.
>
> -Charles-
I downloaded the source from the new web site.
-Charles- |
|
How to connect to an ELOG server running behind apache+ssl using the elog command line program?, posted by Johan Nyberg on Sat Oct 15 16:50:25 2005
|
Hi,
I need to post a large number of "old" messages to one of my logbooks and I am trying to modify the script doelog (see http://midas.psi.ch/elogs/Contributions/10) to suit my needs. I am using apache + ssl for secure logins to my ELOG server. The doelog script uses the elog utility program, which is useful for posting ELOG messages from scripts or from the command line. My problem is that I cannot talk to my ELOG server with elog.
Here is what happens:
-------------------------------------------------------------------------------------------------
$ elog -v -h my.server.org -p 443 -l mylogbook -a Category=Other-u myusername mypasswd testmsg
Successfully connected to host my.server.org, port 443
Request sent to host:
POST /mylogbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------1028A8C27FFD1021AAB342B
Host: my.host.org
User-Agent: ELOG
Content-Length: 811
Content sent to host.
Response received:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href="https://my.server.org/"><b>https://my.server.org/</b></a></blockquote></p>
<hr>
<address>Apache Server at <a href="webmaster@my.server.org">my.server.org</a> Port 443</address>
</body></html>
Error transmitting message
-------------------------------------------------------------------------------------------------------
Access to the logbook works perfectly if I use a web browser. If I can find out how to use the elog command line program to connect to my ELOG server running behind apache+ssl, I think I can change the doelog script to suit my needs. Any help is appreciated.
Johan |
|
Re: How to connect to an ELOG server running behind apache+ssl using the elog command line program?, posted by Stefan Ritt on Mon Oct 17 10:20:31 2005
|
| Johan Nyberg wrote: | | I need to post a large number of "old" messages to one of my logbooks and I am trying to modify the script doelog (see http://midas.psi.ch/elogs/Contributions/10) to suit my needs. I am using apache + ssl for secure logins to my ELOG server. The doelog script uses the elog utility program, which is useful for posting ELOG messages from scripts or from the command line. My problem is that I cannot talk to my ELOG server with elog. |
This is because elog does not support "https" through secure socket layers (SSL). Also elogd does not, that's why you use Apache as your proxy. So the only way for you to use elog is to execute it on the server, where it can directly connect to elogd without going through the ssl layer of Apache. |
|
Re: How to connect to an ELOG server running behind apache+ssl using the elog command line program?, posted by Johan Nyberg on Mon Oct 17 11:07:10 2005
|
| Stefan Ritt wrote: |
| Johan Nyberg wrote: | | I need to post a large number of "old" messages to one of my logbooks and I am trying to modify the script doelog (see http://midas.psi.ch/elogs/Contributions/10) to suit my needs. I am using apache + ssl for secure logins to my ELOG server. The doelog script uses the elog utility program, which is useful for posting ELOG messages from scripts or from the command line. My problem is that I cannot talk to my ELOG server with elog. |
This is because elog does not support "https" through secure socket layers (SSL). Also elogd does not, that's why you use Apache as your proxy. So the only way for you to use elog is to execute it on the server, where it can directly connect to elogd without going through the ssl layer of Apache. |
Hi Stefan,
Thanks for your advice. As you say I can add entries using elog to my logbooks if I do it from the server on which elogd runs, in which case ssl and apache are bypassed:
$ elog -h localhost -p 8080 ...
Thanks once again for your excellent software!
Johan |
|
New Accounts, posted by Carl Shirey on Thu Oct 13 19:15:48 2005
|
I hope you can help me Stefan.
The problem that I am having is when someone request a account on elog I received e-mail message to activate there account. I click on the link from my e-mail to activate the account it takes me to the logon page. I log on and then I get a massage that the web does not exist.
What I found out was the elog Damon stops, and I have to restart it and everything work fine.
Here is a copy of me Elog config.
Also can you tell me how you set up the Subtext and the Show new entry buttons on the main page of the elog.
Thank for your help |
|
Re: New Accounts, posted by Stefan Ritt on Thu Oct 13 21:26:31 2005
|
| Carl Shirey wrote: | I hope you can help me Stefan.
The problem that I am having is when someone request a account on elog I received e-mail message to activate there account. I click on the link from my e-mail to activate the account it takes me to the logon page. I log on and then I get a massage that the web does not exist.
What I found out was the elog Damon stops, and I have to restart it and everything work fine.
Here is a copy of me Elog config.
Also can you tell me how you set up the Subtext and the Show new entry buttons on the main page of the elog.
Thank for your help |
I tried with the current version and could not reproduce your problem. Can you try to increase the login expiration like Login expiration = 240 for ten days. If you then click to activate an account and you have been logged in less than ten days ago, you will not be asked to logon. Does the problem then still occur? |
|
Re: New Accounts, posted by Carl Shirey on Fri Oct 14 19:20:40 2005
|
| Stefan Ritt wrote: |
| Carl Shirey wrote: | I hope you can help me Stefan.
The problem that I am having is when someone request a account on elog I received e-mail message to activate there account. I click on the link from my e-mail to activate the account it takes me to the logon page. I log on and then I get a massage that the web does not exist.
What I found out was the elog Damon stops, and I have to restart it and everything work fine.
Here is a copy of me Elog config.
Also can you tell me how you set up the Subtext and the Show new entry buttons on the main page of the elog.
Thank for your help |
I tried with the current version and could not reproduce your problem. Can you try to increase the login expiration like Login expiration = 240 for ten days. If you then click to activate an account and you have been logged in less than ten days ago, you will not be asked to logon. Does the problem then still occur? |
No the problem does not occur when I am still log on. |
|
Next ELOG Release ?, posted by Alex H on Fri Oct 14 11:06:30 2005
|
Hello Stefan,
Did you have a release Date for Elog V2.6.0 ?
Thanks in Advance. |
|
Re: Next ELOG Release ?, posted by Stefan Ritt on Fri Oct 14 11:07:40 2005
|
> Hello Stefan,
> Did you have a release Date for Elog V2.6.0 ?
> Thanks in Advance.
There is still some unfinished code in the HTML email notification. I guess it will take me still some weeks to
finish that, since I'm pretty busy these days... |
Re: Next ELOG Release ?, posted by Alex H on Fri Oct 14 11:28:28 2005
|
> > Hello Stefan,
> > Did you have a release Date for Elog V2.6.0 ?
> > Thanks in Advance.
>
> There is still some unfinished code in the HTML email notification. I guess it will take me still some weeks to
> finish that, since I'm pretty busy these days...
Ok ! Thanks for the rapid answer! |
|
Long lines in printout, posted by Bertram Metz on Wed Aug 10 10:50:55 2005
|
Hi,
long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer. Does anybody know a solution for this?
Thanks,
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Mon Sep 5 20:39:15 2005
|
> long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> Does anybody know a solution for this?
Can you post an example here? If I try a
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
long line, it's shown correctly. You just have to scroll right in your browser. |
Re: Long lines in printout, posted by Bertram Metz on Mon Sep 12 10:44:51 2005 
|
> > long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> > text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> > Does anybody know a solution for this?
>
> Can you post an example here? If I try a
>
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
> long line, it's shown correctly. You just have to scroll right in your browser.
the lines are displayed as expected on the screen, but they are cut off when the browser window is printed via
the browsers print function.
This did not occur in a previous version (V2.5.6).
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Tue Sep 13 13:33:59 2005
|
Your problem is related with the fact that I changed the formatting from fixed font to proportional font ("ELCode"). This gives you three options:
- Enter your elog entries in "plain" text, which brings you back to the old mode
- Change the page setup of your browser. Mozilla Firefox has File/Page Setup/Shrink to fit page and left and right margin
- Reduce the entry window via the config setting "Message width"
|
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 10:56:29 2005
|
Hi Stefan,
I tried your suggestions with 'page shrinking' and 'message width', but they didn't help. What I do not understand is why this problem occurs only if the message text is formatted as plain text. The lines are printed correctly, if the text is formatted as EL code or as HTML.
It is of course possible to format new entries in EL code or HTML, but we have a lot of existing entries, which are formatted as plain text.
Kind regards,
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 11:19:09 2005
|
Ok, I found the problem. In the default.css file, you will find a section
.messagepre {
font-family:'lucida console',courier,monospace;
font-size:10pt;
}
Just go and delete the line with the font-size, this should fix your problem. If the font-size is fixed, the browser cannot resize the text to fit into your printing page. I still have problems with IE, but with Firefox it works fine if you select Shrink to fit page width on the page setup. |
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 13:27:02 2005
|
The lines are still cut, if printed on paper.
I played again with the 'message width' parameter, which actually the key parameter in my problem. I saw in the source, that the default value is now 112, but it was 76 in the elog version we'd used previously (V2.5.2). If I set 'message width' to 76 again, it works fine for new entries!
I wrote in the previous reply, that changing 'message width' didn't help. That seems to be the case for entries, which are re-submitted. For new entries it works.
Bertram |
|
Re: Long lines in printout, posted by Stefan Ritt on Thu Oct 13 13:51:55 2005
|
| Bertram Metz wrote: | | The lines are still cut, if printed on paper. |
Are you sure? After you change the CSS file, you have to reload the page. I just tried with the very long entry from this thread and got in the Firefox preview window the picture which I attached. The font size of the text body is shrunk such that all lines (except the one very long line) fit on the paper. |
|
Re: Long lines in printout, posted by Bertram Metz on Thu Oct 13 17:45:58 2005
|
You're right. I don't know what I've tested this afternoon 
Without the fixed font the text might get very small, if the line is too long.
I think we'll set 'message width' = 76.
Thanks a lot Stefan! |
|
Trying to remove "mailto:" from the email address, posted by Matt Kimball on Wed Oct 12 23:59:13 2005
|
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.
Thanks
Matt |
|
Re: Trying to remove "mailto:" from the email address, posted by Stefan Ritt on Thu Oct 13 08:32:20 2005
|
| Matt Kimball wrote: | | We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file. |
The "mailto:" is there for good reason. After you submit the entry, elogd converts the "mailto:" into
<a href="mailto:user@domain.com">user@domain.com</a>
so the browser shows the email address as a link. If you click it, the browser automatically opens your email client with the email address already in the "To:" field. The same works in the main text body. So if I put "mailto:stefan.ritt@psi.ch", it gets converted automatially to "stefan.ritt@psi.ch", a feature many people rely on.
Now from your request it looks to me like you want email notifications, so you put
Email System CareWare = ..., $user_email
In that case the "mailto:" gets automatically stripped during the email notification, so the user_email gets entered and will be used correctly for the notification. |
|
elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Fri Sep 23 17:27:40 2005
|
| I can't seem to connect using elog: elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt it run fine through the web interface on http://<myhost>:8080/Servers I have URL = http://<myhost>:8080 in my elogd.cfg Any clues what I'm doing wrong? Thanks for any help. ScottK |
|
Re: elog fails to connect with "cannot get host name: Success" message, posted by Stefan Ritt on Wed Oct 5 13:24:52 2005
|
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
|
Re: elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Tue Oct 11 15:09:42 2005
|
| Stefan Ritt wrote: |
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
Oops - amazing when I read the syntax correctly -- it works! Thanks for taking the time to reply to a "dumb, RTFD" question, Stefan. Thank you for making a great program!
ScottK |