Mailinglist Archive: opensuse (2217 mails)
| < Previous | Next > |
Re: [opensuse] Postfix not recognising me (WAS: Postfix does not seem to be logging)
- From: Sandy Drobic <suse-linux-e@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Sep 2007 21:49:22 +0200
- Message-id: <46F02BC2.8060407@xxxxxxxxxxxxxxxxxxxxxxx>
John wrote:
> Sandy Drobic wrote:
>> [snip]
>>
>> For further help please send the output of "saslfinger -s" of your
>> Postfix
>> box to the list. Patrick's Saslfinger is a script you can easily find.
>>
>>
> True, the script was easily found. However, running install gave the error:
>
> : bad interpreter: No such file or directory
>
> so I copied the files manually to the paths given (and chmoded them).
> 'man 1 saslfinger' works but 'saslfinger -s' gives the :bad interpreter
> error above. I hadn't bargained for debugging the debugging tool! Next
> stop - read the script and run manually.
The most probable explanation is a bad line break, the difference between
windows and unix line feeds. View the file with the viewer of mc, then you
should see the control characters.
Either find a correct encoded version or convert your script with
dos2unix, recode...
I remember that it happened to me as well some years ago.
--
Sandy
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
> Sandy Drobic wrote:
>> [snip]
>>
>> For further help please send the output of "saslfinger -s" of your
>> Postfix
>> box to the list. Patrick's Saslfinger is a script you can easily find.
>>
>>
> True, the script was easily found. However, running install gave the error:
>
> : bad interpreter: No such file or directory
>
> so I copied the files manually to the paths given (and chmoded them).
> 'man 1 saslfinger' works but 'saslfinger -s' gives the :bad interpreter
> error above. I hadn't bargained for debugging the debugging tool! Next
> stop - read the script and run manually.
The most probable explanation is a bad line break, the difference between
windows and unix line feeds. View the file with the viewer of mc, then you
should see the control characters.
Either find a correct encoded version or convert your script with
dos2unix, recode...
I remember that it happened to me as well some years ago.
--
Sandy
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |