Forum Moderators: coopster & phranque

Message Too Old, No Replies

Sendmail error?

         

rocknbil

5:15 am on Apr 12, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I have a customer using Dirt-Cheap-Web-Hosting, there is a small scriptlet on their server that processes paypal IPN. When attempting to connect to sendmail,

can not chdir(/var/spool/mqueue/): Permission denied

Of course I don't do any chdir anywhere in the script, it's a simple open sendmail by the methods you're all familiar with. Being Dirt-Cheap-Hosting I only have access via FTP. Everything was working fine until a few days ago, no new changes.

So am I correct in assuming this is an issue with the host? Any ideas to work around it? Sendmail is the only command-line mail they offer.

Dabrowski

11:28 am on Apr 12, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If you're using the hosts sendmail, and you're not referencing that directory in your code, then absolutely this is a hosting issue.

Are you using sendmail as a command line or doing a 'use' on it?

perl_diver

8:03 pm on Apr 12, 2007 (gmt 0)

10+ Year Member



yea, server problem, hopefully just temporary.

rocknbil

12:39 am on Apr 14, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Sorry wife had an anniversary business party yesterday, I was the "road crew." :-)

Yeah it's your typical perl sendmail usage, with -t to reduce abuse on the pipe

open (MAIL,"¦ $mailprog -t") or &error("Cannot start $mailprog $!");

With a content-type header at the top it stops with the mailqueue error and never gets to my error sub. The folks I'm doing this for have zero technical knowledge, and when I presented the question to the host they replied "have the primary account holder call us to discuss the issue." They won't have a clue what to tell them!

Ya get what ya pay for I guess.

EDIT: in my absence, Lo and behold, it has gone away, apparently they have fixed it.

perl_diver

6:10 am on Apr 14, 2007 (gmt 0)

10+ Year Member



cool, either the site was hacked and some jerk changed permission on the mqueue folder or more likely the site administrators were messing around with something and changed the permissions unintentionally, maybe during an upgrade.