Harald Ponce de Leon

Please tell me you've read that message :D I've marked the important text in bold. Your PHP binary does not include MySQL functionality. It needs to be compiled again.

This is what Google gave me in two shakes of a lambs tail: http://www.gnu.org/software/gnats/mimedecode.html You have the perl script, now you need a php/perl guru to integrate it into the helpdesk :D :lookround: ...runs away!

Since you do not have access to the php binary (due to chroot), get the server administrator to copy the binary to your home directory - then you have access to it. You could also try to compile the php binary on your server, but I doubt it would work due to the chroot environment. You can also try to FTP upload a php binary to your server, if you have a matching OS to what the server is using. It may or may not work (probably won't, but its up to you to try). Your server administrator will probably kill me now for saying that :D :lookround:

Easy :D cd ~/ mkdir bin cp /usr/bin/php ~/bin/ (ofcourse they would have to do this due to the chroot) There is nothing you can do with php binary that you can't with the php module (in apache, as a http request).

Do you have the helpdesk_departments table definition set in catalog/includes/application_top.php? (as mentioned in the installation text)

For some strange reason mysql_num_rows is returning 0 for the departments query :( A fixed osc_mail2db.php has been uploaded again to the Contribution package-set. The error for the department query was a leading space existing in the email address.

For some strange reason mysql_num_rows is returning 0 for the departments query :(

And now for my redface :oops: :D If only HTML emails are received, the body will not be inserted in the database. plain/text and plain/text+html have no problems. I will update the osc_mail2db.php script again to also insert html emails but with html tags stripped.

That is not right :( Adding recipes is not done by logging into the mail server daemon, it is done by editing mail daemon configuration files. If your server is using Sendmail or Postfix, the example in the installation text will work for you. Otherwise you will need to find out how to add recipes specific to your MTA and/or consult your server administrator.

All commands are executed the same whether in telnet or in SSH. What commands are you specifically talking about though?

I mentioned that in a previous post :) (on page three of this thread) Actually, the reason for the email is to use whatever is defined in the recipe and to have whatever there consistent when postings are sent via email or via the Contact Us page. If a backup email address is used, this would only need to be set in the recipe and not in the Contact Us php logic.

The updated osc_mail2db.php script has been uploaded: http://www.oscommerce.com/community/contributions,859 The error occured depending on how the incoming email was parsed (which is why it was not originally noticed) I apologize for any inconveniences!

Maybe you can ask here: http://www.oscommerce.de Regarding: http://www.oscommerce.com/forums/viewtopic.php...p?p=95351#95351 I just had alook and ooooops! :oops: The parse_output() call should be renamed to osc_parse_mime_decode_output() I will upload the fixed osc_mail2db.php script to the contribution. The function is defined in osc_mail2db.php. Postfix is on my local Gentoo Linux server - all configuration is done by hand :D

I think its a custom solution. Here are some more screenshots: http://www.pair.com/pair/support/mypair/mail.html

Postfix (I posted a link above to the Gentoo Linux mail setup)

/etc/mail/aliases: help: "|/usr/bin/php -q /home/projects/osCommerce/cvs/catalog/extras/helpdesk/osc_mail2db.php config=/home/projects/osCommerce/cvs/admin/admin/includes/local/configure.php All on one line. The "help" user does not have to have a user account on the server - it's just an alias. Note: Don't forget to run "newaliases" to generate a new aliases.db file :) (should be located in the same directory as the "aliases" file) No - as mentioned, configuration is server specific. You can try, but don't blame me if something breaks :D

I've locked a similar thread regarding recipe/osc_mail2db.php problems on the Features forum channel. http://www.oscommerce.com/forums/viewtopic.php?t=30806 Discussions should continue on this thread.

Here is my example at Pair: The option to choose above is "Filter" In the Mail Sent To field I would enter the mail alias entry of help, sales, info, or whatever so that the helpdesk department email address would be help _AT_ oscommerce.com, sales _AT_ oscommerce.com, info _AT_ oscommerce.com, or whatever. [the " _AT_ " string is ofcourse the @ symbol to avoid the forum creating automatic links to non existing email accounts] The Pass To field would contain the following: /usr/bin/php -q /path/to/osc_mail2db.php config=/path/to/admin/includes/configure.php Note: There is no need to enter the | here (as in "|/usr/bin/php -q ....") as this is a html based interface to the mail setup which does the magic automatically behind the scenes. ## The correct term for mail alias entry is indeed Recipe.

There is a reason why little documentation was provided with the contribution in regard to accepting incoming mails - this is very server specific and will be impossible to cover all areas. That is why when people have this working they should report back on the steps they made not only to help others out, but to also put some documentation together. I've put my bit in with the Sendmail example - that is all I did and it works for me. I will mention three types of servers: 1) Localhost (Linux. Windows probably needs a third party application). 2) Shared Server (little control over the server) 3) Dedicated Server (some control over the server) 1) It's more than likely you have no idea what to do otherwise you would not be reading up to this page on this thread :D (smile, sooner or later you will get it working) The most important thing to do is to get mails working with your localhost server. I have Gentoo Linux installed, the appropriate documentation for this can be found here: http://www.gentoo.org/doc/en/desktop.xml#doc_chap6 If your server documentation is still alien to you, the only suggestion I have is to test this on the shared/dedicated server and let the server administrator take care of it for you. 2) Ask your server administrator! Tell them you need a mail alias entry to parse a script - provide the examples given in the contribution installation text. If your server administrator does not know or has to do research on it, I'd suggest to move to another server hosting company. Hey, this is e-commerce, it should be taken seriously - your server administrator should have the know-how for their own servers! 3) A combination of 1) and 2). ## I hope that helps somewhat - I am not a unix mail guru so I cannot provide more tips. ## The contribution will also work without a mail alias entry, but then incoming emails cannot be tracked and stored in the database. I think the Contact Us page provided needs to be updated in this case as it needs to store the submited information directly in the database instead of emailing it to the mail alias entry (which would not exist).

Remember that it is just the HTML being compressed, not the images. The images are already compressed in either GIF or JPG or whatever. I have proposed a php/gzip feature internally and will spruce it up and contribute it soon. There is some logic to enable gzip compression only if the client supports it. Here are some rough benchmarks: default.php: Uncompressed length: 27774 Compressed length: 3753 product_info.php: Uncompressed length: 25908 Compressed length: 4045 checkout_confirmation.php: Uncompressed length: 25617 Compressed length: 3428

Thanks to Mattice for helping out in testing the contribution .. in the weeee hours of the morning (4:30am->6:00am :shock:)

NOTE: The osc_mail2db.php script has been updated which fixed 2 errors. It can be downloaded in the Contribution package-set at the following link. http://www.oscommerce.com/community/contributions,859 A helpdesk add-on for osCommerce that has the capability to keep track of communication via emails. The thread of communication is stored in the database where a ticket number is assigned to a thread. It is possible to create template responses which can be used when replying to a ticket entry. Departments are setup to handle different areas of communication (help, sales, information, etc). [This is a separate work to other helpdesk feature contributions currently available]

Ok, I will fix it. There was no need to make a duplicate contribution. Please email me if there are further problems with the package.

The v0.3 contribution has been moved to its package set, which can be found here: http://www.oscommerce.com/community/contributions,585 To the authors, please avoid having multiple contributions in the one file (by the title I presume there is a shipping module involved too).

This posting is a short description on how contributions should be made. It will be added to the Contributions section when the "adding" pages have been updated to be a little more user friendly. When a new contribution is made available, a package is created that holds the description and file. This file can be seen as v1.0 of the contribution made. When an updated contribution is made available, it should be added to the original package. This allows different versions of the contribution to exist in an easy to find package. Clicking on "Contribute A New Package" will enter a new package into the contributions list. Clicking on "Add A File To This Package" will add a file to an existing package. Both methods will show the package on the Newest Contributions list as it has been the latest package to be modified. Since a package can hold multiple files, it is a good idea to enter a clear title for new packages without the version number. For example, if an updated categories box is to be contributed, the ideal package name would be Different Style Categories Box instead of My Categories Box v1.0. Additional files to this package should include the version number in their title, as the title to the files are shown when viewing the package.