Re: [otrs] FQDN - set in SysConfig, but showing in answer message as localhost

Hi Michael,
Upgrading might be a worthwhile option. The problem occurs when
attempting to respond to a ticket e.g.:
http://some.host.name.com/otrs/index.pl?Action=AgentTicketCompose&ResponseID...
I can't get it to work by changing NotificationSenderEmail
from ...@
Hi Dan, I don't clearly understand your question..does the error appear when you are composing a new phone ticket or when you're closing a ticket? Try put a full valid e-mail address under "Sysconfig->Framework->Core->NotificationSenderEmail" PS: Try upgrading to otrs 2.4.5; has a whole load of new features that will make life easier!
Michael -- _____________________________________________________________ .`.`o o| ,\__ `./`r Dr. Dan Kortschak dan.kortschak at adelaide.edu.au <\/ \_O> O "|`...'.\ The trouble with the world is that the stupid are ` :\ cocksure and the intelligent are full of doubt. : \ -- Bertrand Russell
By replying to this email you implicitly accept that your response may be forwarded to other recipients, unless otherwise specified.

Hi Dan, The NotificationSenderEmail in the SysConfig is used for *notifications *that are sent out of OTRS, which is something different than regular answers to tickets. For that, the email address associated with the *queue* the ticket is in is used. otrs@localhost is the default email address on a vanilla installation, I'd recommend you to change it to the address you'd like to use, under Admin
Email Addresses. If you'd need more addresses, add them there, and associate them with the corresponding queues under Admin > Queues.
Also, while we do release minor updates often, before using updating as a cure for all it might be wise to check if your issue has been mentioned in your release notes. For instance, for the latest release notes, see here: http://otrs.org/releases/2.4.5/ If that is not the case, you can search our bug tracker to see if it has been raised before via this link: http://bugs.otrs.org/query.cgi?format=specific&bug_status=__all__ Chances are your issue is already addressed and you can find a bug ticket with a patch, or a workaround, in the bugzilla. This is for instance the case with our number one most popular ticket at the moment, concerning the default state in the AgentCompose screen: bug 4433http://bugs.otrs.org/show_bug.cgi?id=4433. If you set up an account you can also add yourself as *cc *for a particular bug meaning that you would automatically receive updates on the progress of the bug. Please raise any bugs you may encounter or enhancement requests in the bug tracker. Please note that the bug tracker is for *software bugs* - questions on configuration or usage belong here on the mailing list, where they'd have a much larger audience looking at them. Hope this helps, - Michiel Beijen R&D OTRS AG Norsk-Data-Str 1. 61352 Bad Homburg Deutschland T: +31 (0) 6457 42418 F: +49 (0) 9421 56818-18 I: http://www.otrs.com/ Business Location: Bad Homburg, Country Court: Bad Homburg, Commercial register: 10751, Tax ID: 003 240 97505 Chairman of the Board: Burchard Steinbild, Managing Board: André Mindermann (CEO), Martin Edenhofer CU@ IIR Service Desk Forum in Mainz (Germany)http://www.otrs.com/en/news-and-press/news-details/article/translate-to-engl...and get to know more about OTRS at booth no. 12 from Nov 24-25, 2009! On Tue, Nov 3, 2009 at 12:39 PM, Dan Kortschak < dan.kortschak@adelaide.edu.au> wrote:
Hi Michael,
Upgrading might be a worthwhile option. The problem occurs when attempting to respond to a ticket e.g.:
http://some.host.name.com/otrs/index.pl?Action=AgentTicketCompose&ResponseID...
I can't get it to work by changing NotificationSenderEmail from ...@
to the appropriate otrs@FQ.DN. I had assumed that would be replaced by the server's FQDN as it is elsewhere, but neither of these approaches work. The page show up as the following in both cases: Options From: OTRS System
* invalid otrs@localhost (Invalid syntax)! To:..... The setting is obviously saved as the field is subbed into the signature and is appropriate in the SysConfig backup when that is downloaded.
cheers Dan
On Tue, 2009-11-03 at 09:56 +0000, otrs-request@otrs.org wrote:
Hi Dan, I don't clearly understand your question..does the error appear when you are composing a new phone ticket or when you're closing a ticket? Try put a full valid e-mail address under "Sysconfig->Framework->Core->NotificationSenderEmail" PS: Try upgrading to otrs 2.4.5; has a whole load of new features that will make life easier!
Michael -- _____________________________________________________________ .`.`o o| ,\__ `./`r Dr. Dan Kortschak dan.kortschak at adelaide.edu.au <\/ \_O> O "|`...'.\ The trouble with the world is that the stupid are ` :\ cocksure and the intelligent are full of doubt. : \ -- Bertrand Russell
By replying to this email you implicitly accept that your response may be forwarded to other recipients, unless otherwise specified.
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
participants (2)
-
Dan Kortschak
-
Michiel Beijen