Topic: Need Explain about Email from Cron Daemon

[barame]

Dear All.
Every time SME fetchmail from my hosting the reporting email was send from Cron Deamon with the subject "Cron <root@web> /etc/startmail"
But the mail body have only the # and ***** with difference long.
What does it mean and can it show the email subject that what it fetch from host.

Sorry if this question is non-sense.
Best regards,
Barame

[barame]

No body know it right?

Barame

[Per]

Jupp, I got the same problem since yesterday.
Sender: Cron Daemon
Subject: Cron <root@server14> /etc/startmail
Content: #***********.***
or something similar (varies a bit).


Maybe it is related to the upgrade from 7.1.3 to 7.2 or maybe the fact that I installed Certificate-contrib yesterday?
I have a nagging feeling that I had this sometime in the past, but I can't remember....

[raem]

barame & per

Search the forums eg on /etc/startmail or even #***********.***

I'll let you read the results

http://forums.contribs.org/index.php?action=search2

Maybe this
http://forums.contribs.org/index.php?topic=9736.0

[Per]

Thanks Ray, but I actually did those searches before i posted, but I didn't think the answers looked like solutions.
§1 Anyway, I did the command

Code: [Select]

/etc/startmailand it turned back nothing (I'm unsure if that's good or bad).

§2 I looked over my fetchmail (contrib) account settings.

§3 I did the command

Code: [Select]

/sbin/e-smith/config show fetchmailand it turned back

Code: [Select]

fetchmail=service
    FreqOffice=every15min
    FreqOutside=every15min
    FreqWeekend=every15min
    Method=standard
    SecondaryMailAccount=popaccount
    SecondaryMailPassword=poppassword
    SecondaryMailServer=mail.myisp.xxx
    status=disabled
Note that status=disabled even though Fetchmail are enabled in server-manager (and I did a disable+enable, and then checked again with same result).
But then I realized that this is maybe only the config, not the current status?

§4 Trying Windows solution 1: Reboot.

Lets wait and see if any of these actions helped.... 

-No, another #***-mail was sent an hour later.
I'm all out, ideas anyone please?

[raem]

per, barame

Although this bug is about ezmlm, it has reference to fetchmail issues like yours.
Maybe ?
http://bugs.contribs.org/show_bug.cgi?id=2745
See comment #2

[cactus]

-No, another #***-mail was sent an hour later.
I'm all out, ideas anyone please?

Are you using the smeserver-fetchmail contrib? If so try setting the debug option for all users to disabled in the server-manager. I believe it had something to do with that. I believe this was a FAQ item once, but was unable to find it.

Please let me know if this is the solution, maybe we can add it to the FAQ again.

[Per]

Yes I do use the fetchmail contrib, and yes I did enable logging for one account a couple of days ago.
So that could very well be the problem. I have disabled that logging now.

I come back tomorrow with results (saturday night 8,30 pm here). 
PS I also searched faq and wiki previosly, with no result. DS

[micropitt]

Thanks Ray, but I actually did those searches before i posted, but I didn't think the answers looked like solutions.
§1 Anyway, I did the command

Code: [Select]

/etc/startmailand it turned back nothing (I'm unsure if that's good or bad).

If you do the command

Code: [Select]

/etc/startmailit will not give you any feedback on the command prompt. It just starts the fetchmail process and then either quits because fetchmail is done or it will time out if fetchmail doesn't work correct. Look in /var/log/messages for more......

 

[Per]

Since I disabled logging in contrib smeserver-fetchmail I haven't received any more #***-mail from Cron Daemon.
So for now it looks like solved 

I will add a note about it in the wiki page of smeserver-fetchmail.
Thanks a lot guys for your time and effort!
/Per