IMAP failing to pull mail from Exchange 2019

JonasNimmo

Using 1.18 installed 2 days ago on cPanel 112.0.4. PHP81 with IMAP loaded. MySQL v8.0.33

I'm having trouble with OST pulling IMAP email from my 2019 OnPrem Exchange. Exchange working fine and email clients can connect fine using SSL over 993. I have used the same connection settings for OST. No mail is being pulled from the mailbox and added as ticket, nor being deleted when dealt with.

I setup a cron job in cPanel in case that was the issue, and the cron job emails me upon completion.
/usr/local/bin/ea-php81 /home/helpdesk/public_html/api/cron.php

This is the output:
PHP Deprecated: Optional parameter $namespace declared before required parameter $key is implicitly treated as a required parameter in /home/helpdesk/public_html/include/class.config.php on line 198 PHP Deprecated: Return type of BaseList::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 101 PHP Deprecated: Return type of BaseList::count($mode = COUNT_NORMAL) should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 106 PHP Deprecated: Return type of ListObject::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 220 PHP Deprecated: Return type of ListObject::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 198 PHP Deprecated: Return type of ListObject::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 207 PHP Deprecated: Return type of ListObject::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.util.php on line 227 PHP Deprecated: Return type of ModelMeta::offsetExists($field) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 242 PHP Deprecated: Return type of ModelMeta::offsetGet($field) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 236 PHP Deprecated: Return type of ModelMeta::offsetSet($field, $what) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 239 PHP Deprecated: Return type of ModelMeta::offsetUnset($field) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 245 PHP Deprecated: Return type of QuerySet::getIterator($iterator = false) should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1565 PHP Deprecated: Return type of QuerySet::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1596 PHP Deprecated: Return type of QuerySet::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1599 PHP Deprecated: Return type of QuerySet::offsetSet($a, $b) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1605 PHP Deprecated: Return type of QuerySet::offsetUnset($a) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1602 PHP Deprecated: Return type of QuerySet::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1371 PHP Deprecated: Return type of CachedResultSet::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1743 PHP Deprecated: Return type of CachedResultSet::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1747 PHP Deprecated: Return type of CachedResultSet::offsetSet($a, $b) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1754 PHP Deprecated: Return type of CachedResultSet::offsetUnset($a) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 1751 PHP Deprecated: Return type of ModelInstanceManager::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2002 PHP Deprecated: Return type of CallbackSimpleIterator::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2046 PHP Deprecated: Return type of CallbackSimpleIterator::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2051 PHP Deprecated: Return type of CallbackSimpleIterator::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2036 PHP Deprecated: Return type of CallbackSimpleIterator::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2040 PHP Deprecated: Return type of CallbackSimpleIterator::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2031 PHP Deprecated: Return type of FlatArrayIterator::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2076 PHP Deprecated: Return type of HashArrayIterator::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.orm.php on line 2099 PHP Deprecated: Return type of BaseMessageStorage::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/helpdesk/public_html/include/class.message.php on line 186 PHP Fatal error: Uncaught mysqli_sql_exception: No such file or directory in /home/helpdesk/public_html/include/mysqli.php:69 Stack trace: #0 /home/helpdesk/public_html/include/mysqli.php(69): mysqli->real_connect('localhost', 'SomeRandoUser', 'SomeRandoPass', NULL, '3306', '/var/lib/mysql/...') #1 /home/helpdesk/public_html/bootstrap.php(217): db_connect('localhost', 'SomeRandoUser', 'SomeRandoPass', Array) #2 /home/helpdesk/public_html/main.inc.php(28): Bootstrap::connect() #3 /home/helpdesk/public_html/api/api.inc.php(32): require_once('/home/helpdesk/...') #4 /home/helpdesk/public_html/api/cron.php(17): require('/home/helpdesk/...') #5 {main} thrown in /home/helpdesk/public_html/include/mysqli.php on line 69

Also after turning on IMAP logging on the Exchange I see this:
2023-07-07T23:11:57.878Z,0000000000000003,0,[2403:5800:b100:100::b]:993,[2403:5800:b100:100::f234]:35172,,20,0,53,OpenSession,,, 2023-07-07T23:11:58.165Z,0000000000000003,1,[2403:5800:b100:100::b]:993,[2403:5800:b100:100::f234]:35172,ib.helpdesk,278,41,26,login,helpdesk@itsbroken.net *****,"R=OK;Msg=""Proxy:mail.sitestorage.info:1993:SSL;ProxySuccess"";ActivityContextData=19b6439f-453f-417c-b24c-59ad6f6789ba", 2023-07-07T23:14:07.622Z,0000000000000003,2,[2403:5800:b100:100::b]:993,[2403:5800:b100:100::f234]:35172,ib.helpdesk,0,46,1000,proxy,mail.sitestorage.info:1993:SSL,,

and
2023-07-07T23:11:58.025Z,0000000000000002,0,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,,30,0,53,OpenSession,,, 2023-07-07T23:11:58.036Z,0000000000000002,1,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,,1,12,195,capability,,R=OK, 2023-07-07T23:11:58.165Z,0000000000000002,2,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,ib.helpdesk,128,31,33,authenticate,PLAIN,"R=OK;Msg=""User:LegacyDn: /o=Site Storage/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=57f50ddd974b466880377f22431cee80-ItsBroken D, RecipientType: UserMailbox, RecipientTypeDetails: UserMailbox, Selected Mailbox: Display Name: ItsBroken Digital Helpdesk, Mailbox Guid: da26140f-82b7-4b7f-936a-fa188afc4bed, Database: 10c7bf17-4de0-46ee-b5f9-4ceb446e4da4, Location: ServerFqdn: mail.sitestorage.info, ServerVersion: 1942127710, DatabaseName: ItsBroken Digital, HomePublicFolderDatabaseGuid: 00000000-0000-0000-0000-000000000000"";LiveIdAR=OK;ActivityContextData=""I32:ATE.C[mail.sitestorage.info]=10,F:ATE.AL[mail.sitestorage.info]=0.3,I32:ADR.C[mail]=2,F:ADR.AL[mail]=0.81285,I32:ADS.C[mail]=9,F:ADS.AL[mail]=1.489267,Dbl:VCGS.T[MAIL]=0,Dbl:MAPI.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=6,I32:VCGS.C[MAIL]=2,Dbl:RPC.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=5,Dbl:ST.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=1,I32:RPC.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=8,I32:MAPI.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=19,I32:MB.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=8,F:MB.AL[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=0.625,I32:ROP.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=14446128,Dbl:EXR.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=1"";Budget=""Owner:Sid~S-1-5-21-150149131-1076266163-4100585620-1191~Imap~false,Conn:1,MaxConn:Unlimited,MaxBurst:3600000,Balance:3600000,Cutoff:Unlimited,RechargeRate:600000,Policy:GlobalThrottlingPolicy_b3b4cd5f-bf2b-42d2-aa19-a2d2b20e35cd,IsServiceAccount:False,LiveTime:00:00:00.0539961""", 2023-07-07T23:11:58.208Z,0000000000000002,3,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,ib.helpdesk,41,19,353,select,"""INBOX""","R=OK;Rows=5;Recent=1;UidValidity=14;UidNext=7;ActivityContextData=""Dbl:BudgUse.T[]=39.9953002929688,Dbl:MAPI.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=28,Dbl:ST.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=11,I32:MB.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=18,F:MB.AL[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=1.555556,Dbl:RPC.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=28,Dbl:STCPU.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=15,I32:RPC.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=18,I32:MAPI.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=277,I32:ROP.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=34310193,Dbl:MBLB.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=1060,Dbl:EXR.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=12"";Budget=""Owner:Sid~S-1-5-21-150149131-1076266163-4100585620-1191~Imap~false,Conn:1,MaxConn:Unlimited,MaxBurst:3600000,Balance:3599967,Cutoff:Unlimited,RechargeRate:600000,Policy:GlobalThrottlingPolicy_b3b4cd5f-bf2b-42d2-aa19-a2d2b20e35cd,IsServiceAccount:False,LiveTime:00:00:00.0964750""", 2023-07-07T23:11:58.214Z,0000000000000002,4,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,ib.helpdesk,5,16,556,list,""""" ""*""","R=OK;FolderCount=13;UidValidity=14;UidNext=7;ActivityContextData=""Dbl:BudgUse.T[]=5.02239990234375,Dbl:MAPI.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=4,Dbl:ST.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=2,I32:MB.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=3,F:MB.AL[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=1.333333,Dbl:RPC.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=4,Dbl:STCPU.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=15,I32:RPC.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=3,I32:MAPI.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=7,I32:ROP.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=5417482,Dbl:EXR.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=2"";Budget=""Owner:Sid~S-1-5-21-150149131-1076266163-4100585620-1191~Imap~false,Conn:1,MaxConn:Unlimited,MaxBurst:3600000,Balance:3599963,Cutoff:Unlimited,RechargeRate:600000,Policy:GlobalThrottlingPolicy_b3b4cd5f-bf2b-42d2-aa19-a2d2b20e35cd,IsServiceAccount:False,LiveTime:00:00:00.1029960""", 2023-07-07T23:14:07.622Z,0000000000000002,5,[fe80::e497:bc27:eb4a:b353%11]:1993,[fe80::e497:bc27:eb4a:b353%11]:48811,ib.helpdesk,1,11,91,logout,,"R=OK;UidValidity=14;UidNext=7;ActivityContextData=""Dbl:BudgUse.T[]=1.01049995422363,Dbl:MAPI.T[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=0,I32:MB.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=0,F:MB.AL[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=0,I32:MAPI.C[mail.10c7bf17-4de0-46ee-b5f9-4ceb446e4da4]=3"";Budget=""Owner:Sid~S-1-5-21-150149131-1076266163-4100585620-1191~Imap~false,Conn:1,MaxConn:Unlimited,MaxBurst:3600000,Balance:3599999,Cutoff:Unlimited,RechargeRate:600000,Policy:GlobalThrottlingPolicy_b3b4cd5f-bf2b-42d2-aa19-a2d2b20e35cd,IsServiceAccount:False,LiveTime:00:02:09.5109974""",

It seems to touch the mailbox upon change to the connection settings in the Admin area, then never touches it again after that.

Can someone make sense of the output for me? Or better yet, give me some pointers on how to fix or where to start looking please?

Thanks in advance,
Jonas

JonasNimmo

Ticket Solved. Unticked the "Fetch on auto-cron", saved and then ticked it again and saved. Next cron pass and tickets were all created as expected.

KevinTheJedi

JonasNimmo

You really need to configure a cron job so you don’t have to rely on auto cron:

https://docs.osticket.com/en/latest/Getting%20Started/POP3-IMAP%20Settings.html

Cheers.

JonasNimmo

KevinTheJedi
I've got CRON running every 5 mins, however it is random as to whether it picks up new mail from the IMAP mailbox or not.

The CRON email output, shown in the original post is still occurring. Outside of the dozens of deprecated PHP statements, I am still getting a mysqli exception claiming the No such file or directory exists. It inconveniently only shows part of the $socket output from the mysqli.php file. I assume it's /var/lib/mysql/mysql.sock which is the correct location of the socket file on the cPanel server.

Im interested to know what the statement <mysqli_sql_exception: No such file or directory in /home/helpdesk/public_html/include/mysqli.php:69> is referring to when it mentions there is no such file or directory.

On top of this, I also have nearly 90 second delays when submitting a ticket, or 5-7 second delays when opening a ticket. There is only on ticket in the system, and 4 agents. Install is only a couple of days old now and occupies about 6.05mb.

KevinTheJedi

JonasNimmo

You can configure your PHP to suppress warnings and deprecations and only log actual errors.

As for the mysqli error, can you try using 127.0.0.1 as the MySQL host in the ost-config instead of localhost?

As for the slowness, that definitely shouldn’t be happening on a basically fresh install. Unfortunately this can be due to many different things such as insufficient server resources, insufficient MySQL resources, if MySQL isn't optimized, maybe even the logging of warnings/deprecations is slowing it down, etc.

Cheers.

JonasNimmo

KevinTheJedi
Sorry. Forgot to add you in to the last two responses.

JonasNimmo

The change from localhost to 127 caused the opening of an existing ticket to be much quicker, but the ticket submission is still taking about 90 seconds. It also fixed the mysqli real_connect error in the cron output (now just php warnings which is fine - I'll pipe them to /dev/null once we complete the investigation.

We're running this instance on a cPanel box with 64GB ram allocated and 24 cores. We only have 6 other domains running and about 1% activity. TOP shows nearly no activity when i do a ticket submission and all the way till the submission completes. The account we setup on cPanel has no limited resources (full admin account). Are there any local php memory limits we need to change perhaps?

JonasNimmo

Just updated php for the user from 128MB to 512MB. Post data is 32MB and upload_max_filesize is 10M.
Didn't change the 90 second time out.

Can I flip it into some sort of debug mode to see where the 90 second timeout is happening?

I also notice that making any changes to the Emails > Remote Mailbox config or the Outgoing SMTP config, upon submission, they take about 90 seconds to complete also. Changing assigned agent also takes 90 seconds. Posting of an internal note takes 0 seconds. I pretty sure it has something to do with sending an email that causes the 90 second time out.

KevinTheJedi

JonasNimmo

Yes, when you create a ticket it has to notify the user and relevant agents. So if your email connection takes a minute so will the submission process.

Cheers.

JonasNimmo

That's the assumption I made. Initially I was pulling IMAP from an Exchange 2019 server and sending SMTP direct to our eFa antispam gateway. Using telnet as a test, I could connect to the exchange, list and pull the first email, with all commands coming back with immediate answers. Same test of the SMTP sending an email and all responses were immediate, including the final . send command. I could perform both inside the time it would take from ost to add a reply to a ticket.

To make sure it wasnt the exchange or eFa, I created an email account on cPanel and updated the config of the email in ost. So now with ost sending to localhost, the timeout of 90 seconds is still unaffected. I know for sure that cPanel has no mail delay issues as we have other php/jquery based systems that send and receive emails immediately.

What I did notice on tailing the maillog on both eFa and cPanel was that ost always makes its first connection attempt to the smtp at the 78 second mark. At that moment, the entire smtp chatter and relay happens within 14ms, with mail delivery completing and outlook receiving the email about 7 seconds prior to ost updating the interface to show it has completed the transaction.

Just for laughs, I'm going to move the installation to a subfolder, create a new DB and create a new installation. I'll test the email aspect as the first action to see if an absolute brand new install creates the same issue.

KevinTheJedi

JonasNimmo

To test if it’s the email process post a Reply and set the Reply-To option to Do Not Email Reply. For Ticket creation set the Ticket Notice option to Do Not Send Alert and maybe temporarily disable the agent alerts or create it under a department with alerts disabled. That way you can disable any outgoing email and test the performance solely of the system.

Cheers.

JonasNimmo

Thank you. I will do that after I roll back later. Ive dropped a new installation in for now. Just about to test now. I'll try your suggestions in this install too if I have the same issue.

JonasNimmo

Set me on fire! The new installation has no issues at all. Tickets create immediately, and emails move immediately. I set it up exactly the same as the original install. Swapped installs to the original one so I could test your suggestions. Tested a new ticket before I made changes...what do you know?? It just worked first go. Ticket opened in a second and email arrived immediately. Go figure huh.

Sorry for the long winded mess around mate. I know how busy you must be. I do appreciate the help tho. Love the product, enough to burn an entire day trying to get it to work...worth it in the long run. I will be recommending this to anyone and everyone who needs a ticketing system.

KevinTheJedi

JonasNimmo

Hey no worries at all! Glad you got it working!

Cheers.