[plug] ProcMail help needed

[Chris Griffin]

I shall give some of this a go and see how I go. No, I know virtually 
nothing about perl too.
While I am on the toping of email, I also seem to have problems with 
sending, in so far as...
My present systems:
RedHat 6.2 with patches is my email gateway and DNS.
A number of Sun unix systems relay through this system as well as
A couple of Windows system (Eudora) use accounts on this system to send and 
receive.

New system RedHat 7.1 It receives email from the outside ok, and the 
Windows/Eudora systems can pick it up, but no-one can send email, from 
either the Sun or Windows systems. I can send out on the server itself.
I have duplicated all of the sendmail config from the 6.2 system (spam 
stuff etc) to this 7.1 system.

Eudora says: "Connection refused", but I find nothing in the logs on RedHat 
7.1 to verify this or to give me any clues.
Other than a message that says "pam_ldap:  ldap_simple_bind Can't contact 
LDAP server"
I installed openldap but have not configured anything yet (do not know 
how). Future learning project. Could this be causing the problem?
Any ideas?

Regards,
Chris






At 11:30 27/07/01 +0800, you wrote:
>Hya,
>
>At 11:07 AM 27/07/2001 +0800, you wrote:
>>No doubt you are correct on all counts Paul.
>>
>>1.      Does this mean I need spaces after the -x's ?
>
>Most commands require a space after a switch definition (eg 
>SUBJECT=`formail -xSubject:` now becomes SUBJECT=`formail -x Subject:`), 
>otherwise the command won't recognize the switch or the parameters. You 
>will need to check the format of the command.
>
>>2.      I do not really understands the syntax of the searching lines, it 
>>is what I got off the pcguru site.
>>         If I need to changes this, what do you suggest?
>
>.*.vbs.* = is looking for everthing before and after the vbs, but it has 
>an extra "." at the front, my question is, "Is this an typo, or does it 
>need to be there?" "What preceeds that "." ?", just looks wrong to me...
>
>>3.      A perl script and virus scanning sounds good to me, any suggestions?
>
>Do you know Perl? I'm just starting out with it, but Perl is a text 
>processing Interpreter, and mail is just text, unless it has been encrypted.
>You could write something that grabs incoming mail (the script called from 
>procmail) looks inside for an attachment. If there is a match then trash 
>it and replace the mail with two mails, one to the sender and one to the 
>receiver, telling them both of the possible virus.
>
><snip>
>
>
>/***** Experience is that marvelous thing that enables you to recognize a 
>mistake when you make it again.
>Franklin P. Jones *****/
>
>/*****All programmers are playwrights and all computers are lousy actors.
>             -- Unknown*****/