Re: Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Andreas Luedeke on Tue Dec 11 09:00:36 2012
|
Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?
Kind Regards
Andreas |
|
Re: Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Ron Beekman on Tue Dec 11 09:43:33 2012
|
> Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?
Hi Andreas,
Thank you very much for your reply. Thsi problem occurs also with the latest ELOG version 2.9.2
It would be nice if the timeout value(s) can be edited via the elogd.cfg file. Maybe this can be added in a new
version.
Best regards,
Ron |
|
Re: Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Stefan Ritt on Tue Dec 11 09:45:25 2012
|
| Ron Beekman wrote: |
|
Hello,
We use ELOG for many years and enjoy it's functions every day!
Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages
We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.
We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.
We had this error in the past and found out that the cause of this error lies in (network) time-outs.
Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?
Any replies are highly appreciated!
T I A !
|
Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log? |
|
Re: Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Ron Beekman on Tue Dec 11 10:17:11 2012
|
| Stefan Ritt wrote: |
|
| Ron Beekman wrote: |
|
Hello,
We use ELOG for many years and enjoy it's functions every day!
Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages
We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.
We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.
We had this error in the past and found out that the cause of this error lies in (network) time-outs.
Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?
Any replies are highly appreciated!
T I A !
|
Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log?
|
Hello Stefan,
Thanks you for entering this thread !
Fortunately, we were able to solve the problem. A reboot of the DNS server used by the MTA (Mail Transfer Agent Server) to check the from and to address did the trick.
This server now responds within the timeout period in ELOG.
It still would be handy if you could add a parameter to the config file that allows us to fiddle with the timeout value. The DNS server used by the MTA has to deal with heavy load.
Best regards,
Ron
|
FCKEditor doesn't show up in Windows 8?, posted by John Haggerty on Wed Feb 20 02:45:45 2013
|
After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure out how to debug FCKEditor. Any ideas? |
|
Re: FCKEditor doesn't show up in Windows 8?, posted by Stefan Ritt on Wed Feb 20 09:32:52 2013
|
| John Haggerty wrote: |
|
After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure out how to debug FCKEditor. Any ideas?
|
Thanks for reporting that problem. Indeed the elog292-1.exe distribution has a bug in the directory structure. I fixed that in elog292-2.exe, which you can download from here:
http://midas.psi.ch/elog/download/windows/elog292-2.exe |
|
Re: FCKEditor doesn't show up in Windows 8?, posted by John Haggerty on Thu Feb 21 02:01:59 2013
|
| Stefan Ritt wrote: |
|
| John Haggerty wrote: |
|
After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure out how to debug FCKEditor. Any ideas?
|
Thanks for reporting that problem. Indeed the elog292-1.exe distribution has a bug in the directory structure. I fixed that in elog292-2.exe, which you can download from here:
http://midas.psi.ch/elog/download/windows/elog292-2.exe
|
Thank you.. that version works fine for me. |
elogd crashes with malloc() memory corruption, posted by Mark Bergman on Fri Mar 1 16:35:21 2013
|
I'm having an issue with ELog 2.9.2 revision 2455 where it crashes consistently with:
*** glibc detected *** /usr/local/sbin/elogd: malloc(): memory corruption: 0x0000000014977210 ***
(the address varies). The crash seems to be triggered by the attempt to email a log entry. The log entry itself is saved. If I open the existing message for editing, make no changes, then Submit the message (in order to send email), the daemon crashes.
The behavior is consistent on multiple servers, each running CentOS5.9.
|