Help with dmesg

Tim Judd tajudd at gmail.com
Mon Jan 12 21:44:08 PST 2009


Rem P Roberti wrote:
> 
>> if I remember rigth I had the same problem months ago, but I'm not 
>> really sure how I solved it.
>> First try to delete the lines 44 - 49 of yourr's .cf file. then try to 
>> restart sendmail.
>> if that doesn't work try dnl after every line in the .mc file. e.x 
>> INPUT_MAIL_FILTER(`clmilter',`S=local:/var/run/clamav/clmilter.sock,F=, 
>> T=S:4m;R:4m') dnl
>> I think something like that I did and it works. But I'm not so sure.
>>
>>
> 
> I decided to start from scratch, and got rid of all the files generated 
> by the "make" command. So now my /etc/mail directory looks just as it 
> did when I started.  Instead of creating a whole new
> batch of files I decided to just start by running the "newaliases" 
> command and here's what I got:
> 
> root@ /etc/mail: newaliases
> /etc/mail/sendmail.cf: line 48: unknown configuration line "
> "
> clearly (I think) the problem has nothing to do with the files generated 
> by "make".  Something
> appears to be messed up with sendmail.cf (at least according to the 
> error message), but I don't
> see how that is possible.  Line 48 in /etc/mail/sendmail.cf is blank!
> 
> Rem
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"

The screen doesn't print all characters.  3 examples are 0x00, 0x0a, 
0x0d.  NULL, and (newline/return).

I have a feeling there's a unprintable character in there and sendmail's 
bawking at it.  I don't use sendmail, personally -- too inexperienced 
and the configuration process confuses me.

So in layman terms:
	Clear all blank and commented lines out of the .cf file
	For good measure, hexdump the saved file to see if you find any 
abnormal characters for sendmail.

	What I'm unsure of, is after clearing the .cf file up, does sendmail 
have this configuration in memory so it will CONSTANTLY complain until a 
new config is generated?  This, compared to say any other common app 
that reads it's .conf file at startup and doesn't keep any of it as part 
of the binary itself.

I feel I didn't explain this very well.  PLEASE notify me if you feel 
this is true.  I'll try to re-explain myself differently then.


More information about the freebsd-questions mailing list