Znuny and ((OTRS)) Community Edition

Well, IMO proper fix would be reworking how the command works, i.e. by making it set the setting to desired value after it finishes it's job, or adding some last resort check before popping the mentioned error message, i.e. if setting is FS, and data is not on FS, check DB, then pop the error, but y...

$ bin/otrs.Console.pl Admin::Article::StorageSwitch --help Migrate article files from one storage backend to another on the fly. Usage: otrs.Console.pl Admin::Article::StorageSwitch --target ... [--source ...] [--tickets-closed-before-date ...] [--tickets-closed-before-days ...] [--tolerant] [--mic...

I did now, and everything's working as expected

Thank you.

Please fix the docs... add a mention of this in Admin::Article::StorageSwitch.

Cheers!

Recently I upgraded from 6.3.4 to 6.4.4, and after that I migrated articles from FS to DB using Admin::Article::StorageSwitch I've noticed that attachments are missing from older tickets (I confirmed that those attachments are present in database) and clicking on 'plain format' results in "Can'...

It mostly does the job done, but not in case of these e-mails. SpamAssassin passes them through. URLs are pretty much common for each destination e-mail address, except for minor differences.

This spam started again.

What's the proper way to filter such mail?

It has URLs such as this in common.
http://cpsinterier.sk/template.php?f=11 ... BQQ&k=ABD2

What do you mean? We've received multitude spam e-mails with URLs containing hashed e-mail address. URL was pretty much the same, but was randomly broken with superficial content (&, #, and other characters that were probably filtered out by spammers after someone clicked the link). Anyway, that...

Found the bug... I had multiple postmaster filters that checked body for things like: .*V.*p.*g.*b.*H.*s.*m.*A.*W.*x.*c.*m.*r.*L.*4.*q.*X.*n.*j.* It was an anti-spam measure and it worked great for matching the spam mails, however for reasons unknown it causes perl to sometimes hang. Oh well. I've d...

After killing the process (with normal SIGTERM), I've noticed some lines were added to 'listing': entering DB::print_lineinfo 76: my $MatchedResult = ''; entering CODE(0x80ae1ef90) entering DB::Obj::_init entering CODE(0x8022f0300) entering CODE(0x8022f0378) entering CODE(0x8022f0300) entering CODE(...

Anyway, I tried running: PERLDB_OPTS="N f A L=listing" perl -d bin/otrs.Console.pl Maint::PostMaster::MailAccountFetch --force-pid --debug and it seems things die here: 672: print STDERR "\nspecials_name => $specials_name\n" if DEBUG; 673: $SWASH->{'SPECIALS'} = \%$specials_name;...

Thanks for noticing. Updated.

Direct SMTP? I thought SMTP is for sending e-mail, not receiving it. Like I've said, I've tried both IMAP and POP3, so it has something to do with contents of the message. Pointer as to what is done after mentioned debug lines happen would be nice.

Wait, what? OTRS 5 Patch Level 13 is an old system? :o - I thought 5.0.13 was the newest stable version. OS is FreeBSD, however I tried moving the installation to Debian and same thing happens. I'll try to collect more e-mail that trigger this behavior to find some commonalities, but maybe it happen...

Since some time now OTRS randomly hangs when fetching e-mail. It doesn't matter whether POP3 or IMAP is used. bin/otrs.Console.pl Maint::PostMaster::MailAccountFetch --force-pid --debug Fetching incoming mails from mail accounts... ...imap server... (IMAPS)... (...) [...cpan-lib/Net/IMAP/Simple.pm l...

Unfortunately no. I suppose I could try to "break" it again, if someone's interested in actively (as in IRC/XMPP) guiding me through debugging - I don't know perl pretty much. It seems to be a problem in MIME module.

Which is the correct forum to report bugs in 3.3 beta?

Downgrading perl to 5.16 resolved the problem.

I'm having the same problem. It's related to upgrade to perl 5.18 and rebuilding all modules. OTRS version did not change.

I want notifications about new ticker/follow-up and other events to go to agent's jabber client, instead of e-mail. I already added it the best way I could, but I would love to have it in some future-proof way that doesn't require maintenance on every release. To restate it: I already hacked it arou...

Well, I hacked around a bit, and managed to add the thing by adding preferences fields UserJabberID and UserUseJabber with options yes/no/only, and modyfying article.pm - too bad I now have another change to track during updates. Any chance of getting this upstream? It's very trivial to add XMPP sup...

Hm, could you explain in a bit more detail what do you mean with 'web services'?

Edit: Found it, looking into it.

Hi guys,

I searched and found some hack level solutions for this, but has this been officially solved or could it be implemented?