PHPJunkyard support forum

Script URL: /inc/mail/hesk_pop3.php
Version of script: 2.4.2
Hosting company: N/a
URL of phpinfo.php: N/a
URL of session_test.php: N/a
What terms did you try when SEARCHING for a solution: hesk_pop3.php, Temporary directory doesn't exist

Write your message below:

Hi All

I hope someone can help. I recebtly had to move the helpdesk to a new server. I have got in to some real issues with permissions and basically bricked the whole helpdesk

I have got everything sorted and back up and running except for POP3 fetching.

I have got to the point where when I 'test POP3 Connection' in Settings > Email through the Admin Control panel it connects fine and then if I call http://domain/support/inc/mail/hesk_pop3.php in a browser it starts the parser but I get the following error:

Connected to the POP3 server "outlook.office365.com".
User "support@domain.com" logged in.
There are 1 messages in the mail box with a total of 18130 bytes.
Parsing message 1 of 1.
We have message file, starting parser
The temporary directory "/var/www/web/support/attachments/2eac95011430b4a9a00150ffb507bddf" doesn't exist.

I am guessing this is some kind of permissions issue where it can't write the temp directory but I just cannot get unstuck.

Any ideas?

Thanks

Richard

If you look into the "attachments" folder is there a directory named "2eac95011430b4a9a00150ffb507bddf"?

If not, this indeed looks like a permissions issue (HESK cannot create a new folder within the "attachments" folder), you may want to CHMOD attachments folder to 0777 (rwxrwxrwx) and see if that helps.

Thanks, file is not present - if I CHMOD attachments directory to 0777 then I get the following error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@this.domain to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Perhaps your server doesn't allow such chmod?

I'm afraid I can't be of much help here, it is something that needs to be figured out on the server/permissions side.