Re: Email subject garbaged when set?, posted by Stefan Ritt on Fri Aug 5 12:37:42 2005
|
| Heiko Scheit wrote: | Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC. |
You are right  , thanks for this information, I overlooked it.
Now I split a long subject into separate chunks of encoded words, and my pine is happy. Update in CVS. |
|
Re: Email recall function similar to what exists say in something like Outlook, posted by Stefan Ritt on Mon Mar 9 19:00:26 2009
|
| Niall Dooley wrote: |
|
Hi,
Is there a way perhaps of implementing an email recall feature into E-Log? In other words, to recall an email before the recipient (s) read the email originating from the e-log. Something perhaps along the lines of what exists in something like Outlook.
Thks in advance.
Regards,
Niall
|
No, this is not implemented. What I usually do is to check "Suppress Email notification", submit and revise my entry. Once I'm satisfied, I edit again and do not check "Suppress Email notification" so that the email is finally sent out. |
|
Re: Email notification: "Use Email From = " always set to admin, posted by Stefan Ritt on Fri Oct 26 11:44:36 2007
|
| Alan Stone wrote: |
My current syntax is:
; Email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I had to comment out the 'Use Email From' option because all forwarded
entries to the CMS HyperNews or Fermilab ListServer appeared to originate
from me (alstone@fnal.gov), even though other users were logged in and
saving the entries to the logbook. After commenting out this line, the
entries were properly credited when forwarded, although the
There are two admins defined in the [global] section, and "alstone" is
not the first name in the "Admin user" list.
Is this a bug, or have I used this option incorrectly?
Alan |
Documentation says:
If Use Email From is present, it is always used. If not, 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 Default Email From is used for the "From:" field. Only if this option is not specified, a generic address ELOG@<hostname> is used, which might be rejected by the SMTP server however.
So if you write
Use Email From = me@some.where
then of course all emails have "me@some.where" in the From: field. If you want the email of the people logged in, you either remove this option (since it's the default anyhow), or you write explicitly
Use Email From = $user_email |
|
Re: Email notification question, posted by Stefan Ritt on Wed May 10 16:16:33 2006
|
| Kevin McCarty wrote: | Hello,
I've just set up an ELog server for my research group. (Running on Debian, package version 2.6.1+r1642-1)
I have a question about the email notifications. I read through the config file documentation, but couldn't find the answer (maybe I am just unobservant\?) Is it possible to have the email notifications contain only the title of the log entry (as well as the usual attributes), but not the full text or any attachments? I have users who are worried about their email going over quota from ELog's emails, but who nevertheless would like some kind of notification when new log entries are posted.
Thanks in advance! |
Have a look at the option Email format = <n> |
|
Re: Email notification question, posted by Kevin McCarty on Wed May 10 16:55:28 2006
|
| Stefan Ritt wrote: |
| Kevin McCarty wrote: | Hello,
I've just set up an ELog server for my research group. (Running on Debian, package version 2.6.1+r1642-1)
I have a question about the email notifications. I read through the config file documentation, but couldn't find the answer (maybe I am just unobservant\?) Is it possible to have the email notifications contain only the title of the log entry (as well as the usual attributes), but not the full text or any attachments? I have users who are worried about their email going over quota from ELog's emails, but who nevertheless would like some kind of notification when new log entries are posted.
Thanks in advance! |
Have a look at the option Email format = <n> |
Ah, thank you! Somehow I overlooked that. My apologies, and thanks for your very fast response. |
|
Re: Email notification does not work, posted by Stefan Ritt on Mon Sep 5 20:35:43 2005
|
| Dinesh Bapat wrote: | I have SMTP server that requires authentication
Whenever a new user 'self registers' to E-log, I get an automated email saying so. Hence, the SMTP setting are correct and working.
However, for any entry made to log, no email notification is generated. error '5.5.4 Invalid Address'
suppress notification checkbox is 'unchecked'
Kindly help. |
Turn on logging with
Logfile = elog.log
then you will see all communication betwen elogd and the SMTP server in the logfile. You probably will see the source of the error there.
- Stefan |
|
Re: Email notification (bug tracking system), posted by Stefan Ritt on Thu Nov 9 22:53:27 2006
|
| Bertram Metz wrote: | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo
You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754. |
Re: Email notification (bug tracking system), posted by Bertram Metz on Thu Nov 30 16:07:54 2006
|
| Stefan Ritt wrote: |
| Bertram Metz wrote: | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo
You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754. |
Thank you very much Stefan,
that works fine for me!
Bertram |
|