Can someone explain why we get these error messages. We have no other problems
with sending email notifications.
Unmatched '' in NetWolves / Corporate Office Network Operations
Centersupp...@netwolves.com,s...@netwolves.com,rand...@netwolves.com, at
/opt/otrs/Kernel/cpan-lib/Mail
--
Stephen
supp...@netwolves.com,s...@netwolves.com,rand...@netwolves.com is an
invalid email address.
The match fail is because the content between doesn't conform to the rfc
standard for an email address (multiple @ signs for starters). You can't
put multiple comma separated email addresses in a field
On 07/23/2013 09:11 AM, Steven Carr wrote:
supp...@netwolves.com mailto:supp...@netwolves.com,s...@netwolves.com
mailto:s...@netwolves.com,rand...@netwolves.com mailto:rand...@netwolves.com is an
invalid email address.
The match fail is because the content between doesn't conform to the rfc
8:34 AM
*To:* User questions and discussions about OTRS.
*Subject:* Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl
On 07/23/2013 09:11 AM, Steven Carr wrote:
supp...@netwolves.com mailto:supp...@netwolves.com,s...@netwolves.com
mailto:s...@netwolves.com,rand...@netwolves.com mailto:rand
Hi List,
We upgraded from 2.4.x to 3.1.11. It has come to our attention by a customer
that only
one person was getting New Ticket notifications, but when a note was added all
the
people in the email field of the customer record got the update notification.
In researching this we found that if
something like
update customer_user set email=replace(email, , );
might possibly be of use. (Backup first.)
On Fri, Mar 22, 2013 at 2:58 PM, Steve Clark scl...@netwolves.com wrote:
Hi List,
We upgraded from 2.4.x to 3.1.11. It has come to our attention by a
customer that only
one person
Thanks Gerald,
I thought about that, but was hoping the routing that parses the
email addresses for Net Ticket notifacations could be corrected so the people
that enter the
email addresses don't have to worry about a space slipping in.
Obviously the routine used during add a note does not have
Hello List,
Anyone know how to identify the ticket number that is causing this error?
OTRS-otrs.PendingJobs.pl-10[481]:
[Error][Kernel::System::Ticket::TicketStateSet][Line:3944]: Need StateID or
State!
Would it not make sense to also print the ticket number in the error message?
Thanks,
--
Edit Kernel/System/Ticket.pm and change line 3944, update the message
returned, change from 'Need StateID or State!' to Need StateID or
State! Ticket: $Param{TicketID}.
Steve
On 1 February 2013 12:02, Steve Clark scl...@netwolves.com wrote:
Hello List,
Anyone know how to identify the ticket
Thanks.
On 02/01/2013 07:34 AM, Steven Carr wrote:
Edit Kernel/System/Ticket.pm and change line 3944, update the message
returned, change from 'Need StateID or State!' to Need StateID or
State! Ticket: $Param{TicketID}.
Steve
On 1 February 2013 12:02, Steve Clark scl...@netwolves.com wrote:
Edit Kernel/System/Ticket.pm and change line 3944, update the message
returned, change from 'Need StateID or State!' to Need StateID or State!
Ticket: $Param{TicketID}.
He does have a point, though. An good error message should give as much context
as possible (answering the basic journalism
Hello List,
These two values have been altered from the default and I can't seem to
get them set back to the original value.
When I click the reset icon next to the item, otrs acts like it is doing
something but when it
comes back they still have the altered value.
What am I missing?
Please ensure that those data aren't configured in Kernel/Config.pm
Have you changed the XML file (Kernel/Config/Ticket.xml)?
On 31.01.2013 16:26, Steve Clark wrote:
Hello List,
These two values have been altered from the default and I can't seem to
get them set back to the original value.
I only see them change
On 01/31/2013 10:32 AM, Renee B wrote:
Please ensure that those data aren't configured in Kernel/Config.pm
Have you changed the XML file (Kernel/Config/Ticket.xml)?
On 31.01.2013 16:26, Steve Clark wrote:
Hello List,
These two values have been altered from the default
Config/Files/Ticket.xml:ConfigItem
Name=Ticket::Frontend::CustomerTicketMessage###StateDefault Required=1
Valid=1
Config/Files/Ticket.xml:ConfigItem
Name=Ticket::Frontend::CustomerTicketZoom###StateDefault Required=1
Valid=1
Hello,
I found that if I remove them from Config/Files/ZZZAuto.pm file they show up
in sysconfig with their default values. Is it OK remove them from the ZZZAuto.pm
file?
On 01/31/2013 11:36 AM, Gerald Young wrote:
Config/Files/Ticket.xml:ConfigItem
Hello
Yes it is OK. That's the way you return them to the default value. If you
want to find out how to write them back, you can take a look at them at ZZZA
*A*uto.pm and copy them back yo ZZZAuto.pm
Leonardo Certuche
www.itconsultores.com.co
Medellín, Colombia
On 31 January 2013 11:54, Steve
There's also the possibility to either save again from Sysconfig after
removal (Ticket.xml will help repopulate) or rebuildconfig from scripts.
You may also want to be sure that OTRS has permissions within the web user
(www-data or otrs) to write to the ZZZ files.
On Thu, Jan 31, 2013 at 12:05
18 matches
Mail list logo
