procmail program

Red Squirrel · 05-22-2005, 04:43 PM

I want to design a parser that will parse news articles that come to my news inbox, so I'm learning as I go, for now, all I want is a basic program that will output mail back to the inbox, and write it to file, this is just to get started so I know what works, what does not, etc.

Here's my code so far:

Code:

int main()
{
char a;

fstream fout("/data/samba/shared/ryan/applications/news_parser/procmailtest.log",ios::out);
for(int i=1000;i>0;i--)
{
a = getchar();

cout<<a;

fout.put(a);
}
fout.close(); 

return 0;
}

I can't figure out how to programaticly know when to stop, (I think it has to do with the content-lenght header, but I'm not there yet) so that's why I just read 1000 chars.

My problem is that the email is NOT being outputted to the procmailtest.log file, the file does not even get created. But the email does successfully make it to the inbox. (a little corrupted though, because it ads/removes chars depending on the size of the email but that I know why).

So how do I get it to write the email to file? If I run this program directly and type stuff, it will write the file properly.

I'm also sending emails bigger then 1000 chars to ensure the program does end so the fout.close does get called. I even tried opening and closing a file right at the start and it does not even work either, so really not sure what's going on.

deiussum · 05-23-2005, 09:52 AM

The first obvious question that comes to mind is, does the user you are executing the program as have write access to that directory?

Red Squirrel · 05-23-2005, 11:17 AM

Yeah, it's running as root (unless it's actually under a different user when procmail runs), and the directory is chmoded 777. Hmm, could it be that it runs under the user to which the mail belongs to? given procmail usually has to write to the home directory, this would make sense.

Red Squirrel · 05-24-2005, 06:21 PM

That was my problem, had to chmod the folder to 777. Figured it already was since samba is set to chmod everything to 777 but perhaps that folder was created with the shell, I can't remember.