Seems the best solution is to use root's crontab. Can you run 'sudo crontab -e'? If so, it eliminates the need for sudo in the script and the need to put your passwd in plain text in the script.

Did you try to use quotes when piping your password?
I sending my password to sudo command like this:

yes i tried like same in my script but it is not giving proper output when i am running through crontab

I do not know how mission critical your script needs to be ran as far as 'it has to be ran at this time then it then has to be send out right away in an email' that may or may not be read until whenever that other person gets around to it. Not to negate the importance of data that it is gathering at a certain time.

I only use one "home made" script within CRON's world. I put it inside of the /etc/cron.weekly and it runs once a week. root side - it is for trimming my sdd hdd. This is on a laptop. So however CRON actually works in what time it gets ran once a week I have not even bothered to look into. due to this laptop can miss whatever that time is. so maybe it does not get ran due to that. I do not even check its log.

But I did just now because of this issue you are having.
It trims both / (root) and /home

as you can see it did not run the very same day of the week because I do not have this thing on 24/7 for it to keep a tight schedule, perhaps that is how CRON works. If it misses that day/time it was suppose to run then run it first chance it gets when having it just sitting in one of the directories to be ran.

now saying that the script of yours does not run the same in a command issued job for CRON.

"it is not giving proper output when i am running through crontab"

which is too vague of a "hey this thing is not working still", Thinking the ones you are telling this to will know just what it is you are talking about without showing what it is doing now against what it is suppose to be doing. One is only left with having to go into dream land to try and figure out what it is actually doing that it is not suppose to be doing.

But, seeings how you have been fiddling with this script for more than a day. what is one more day or two?

if it is a weekly and you run your PC 24/7 it should / is suppose to then run every hour, day, week, month, year at whatever given time.

Even with a user input'ed CRON Job if that PC is not turned on then it still cannot run that job and CRON still has to wait for it to be turned on to do so.

so what is the harm in trying to just add your script into the root sided /etc/cron.xx directory and lets CRON take care of it like that?

your Job is just gathering info and sending an E Mail to someone else. no permissions are really needed to be worried about in setting them on an e mail or having root sending an email a non root user has to read. it is e mail not a file on a system somewhere where permissions are needed to read it depending on where it is at.

that way too it is already root so no password is needed. You'd have to just dig in and find out how exactly does these directories work on getting it to run at a certain time if one is just placed within it to be ran without assigning a job through CRON crontab

this one is mine:
these are the scripts that the system put in all by itself that I pay no attention to either.