Spec file change, posted by Stephen A. Wood on Mon May 8 18:23:17 2006
|
| Could the "Copyright:" line in the elog.spec file be changed to "License:" for the next release? Without this change an RPM can't be built on FC4 (RPM 4.4.1). With the change, rpms can still be built in Enterprise linux 3 (RPM 4.2.3). |
Re: Spec file change, posted by Stefan Ritt on Tue May 9 08:07:00 2006
|
| Stephen A. Wood wrote: | | Could the "Copyright:" line in the elog.spec file be changed to "License:" for the next release? Without this change an RPM can't be built on FC4 (RPM 4.4.1). With the change, rpms can still be built in Enterprise linux 3 (RPM 4.2.3). |
Wow, the RPM build depends on that name? Interesting. I changed it in the SVN version, so it will be contained in the next release. |
|
Hosts Allow and Password File, posted by Jeremy Perkins on Wed Jun 21 18:36:06 2006
|
| I'm trying to set up an elog that uses a password file using the "Password file = /blah" directive as well as the "Hosts allow = myhost.mydomain" directive. I used the -v command and watched the messages and elogd is recognizing that I am connecting from an allowed host but the login page is still appearing. Is there a way to use both of these? |
|
Re: Hosts Allow and Password File, posted by Stefan Ritt on Thu Jun 22 08:09:11 2006
|
| Jeremy Perkins wrote: | | I'm trying to set up an elog that uses a password file using the "Password file = /blah" directive as well as the "Hosts allow = myhost.mydomain" directive. I used the -v command and watched the messages and elogd is recognizing that I am connecting from an allowed host but the login page is still appearing. Is there a way to use both of these? |
You misunderstand something. The "Password file = ..." statement turns on user level access, that means each user has to log in and identify himself this way in a unique way (so that you know who wore a certain logbook entry etc.). This has nothing to do with the "Hosts allow/deny" statements, which works separately. So if you combine "hosts allow" with "password file", this means that only users from the password file can log in from certain hists, but they still have to identify themselves with their username and password. If you want to log into a logbook without supplying a password from certain hosts, then you remove the "password file" statement. But then anyone from that host can write logbook entries, so you loose the user identification. |
|
Use Email From = <string>, posted by Dimitrios Tsirigkas on Wed Jul 19 12:20:34 2006
|
Hi all,
My users have complained about the multiple "I'm away from xxx until xxx" automated replies that they get when they post an entry and notifications are sent with their email in the "From" field. I would therefore like to always use the address specified in the Use Email From line of the configuration file and never the user's address. Reading from the documentation:
The option Use Email From = <string> is used for the "From:" field in the email. Since more and more email servers do not accept invalid "From:" addresses in order to reduce spam mail, it might be important that a "real" email address is used in the "From:" field. By default, the email address of the currently logged in user is used for the "From:" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option Use Email From is used for the "From:" field.
Is there a way to override that default and always use the setting of the option Use Email From?
Thanks,
Dimitris |
|
Re: Use Email From = <string>, posted by Stefan Ritt on Wed Jul 19 12:35:16 2006
|
| Dimitrios Tsirigkas wrote: | | My users have complained about the multiple "I'm away from xxx until xxx" automated replies that they get when they post an entry and notifications are sent with their email in the "From" field. |
Yes, I had the same problem with this forum.
| Dimitrios Tsirigkas wrote: | | Is there a way to override that default and always use the setting of the option Use Email From? |
Sure. You override the default by setting the Use Email From. In the forum I set it now to Use Email From = noreply@psi.ch which is a nonexisting address. While now this is ok, our former email server did not accept this because the user noreply does not exist at our institute. So you have to figure out if this works at CERN. |
|
Re: Use Email From = <string>, posted by Dimitrios Tsirigkas on Wed Jul 19 12:47:58 2006
|
| Stefan Ritt wrote: | | Sure. You override the default by setting the Use Email From. In the forum I set it now to Use Email From = noreply@psi.ch which is a nonexisting address. While now this is ok, our former email server did not accept this because the user noreply does not exist at our institute. So you have to figure out if this works at CERN. |
Thanks, Stefan! I misunderstood the documentation, thinking that the Use Email From option value was only used if the user submitting the entry had not registered an e-mail address when creating his/her elog account. This works fine. 
Cheers,
Dimitris |
Conditional E-Mail Attributes, posted by Grant Jeffcote on Fri Aug 11 21:48:01 2006
|
Stefen, is it possible to change an email option using conditional attributes?
I have a need under certain conditions to send an email in plain text (Encoding type 1) but as type 2 under other conditions, it seems when I do the conditional string is ignored and the global entry is used.
Can all email options be actioned using a conditional string, it only seems to work on some?
Shown here are some of the options that would be nice to set under 'conditions'.
Some appear to already work that way.
{2}Email attributes = xxx, xxy,
{2}Email All = dee@sdf.com, def@sdf.com,
{2}Preset text = This is a test
{2}Email Encoding = 1
{2}Use Email Subject = ELOG-ID $message id - Test Company
{2}Use Email Heading = Test Company Operations Report
{2}Use Email From = admin@sdf.com
{2}Suppress Email to users = 1
{2}Email Format = 27
{2}Suppress Email on edit = 1
{2}Suppress default = 2
{2}Display Email recipients = 1
{2}Omit Email To = 1
Any help would be appreciated. |