On Wed, 29 Apr 1998, era eriksson wrote:
regex looks too wild, fine, but at least you should be using
^TO(_dot_)*(_at_)(_dot_)*falcon(_dot_)org (or even \.org) if that's what you
mean to say.
(I.e. the fact that it seems to work is kind of a coincidence.)
what i meant was: anyuser(_at_)anyzone(_dot_)falcon(_dot_)org
i.e. the following would catch with that:
bob(_dot_)bill(_at_)mail(_dot_)falcon(_dot_)org
jimbo(_at_)falcon(_dot_)org
falconnews(_at_)falcon(_dot_)org
things that wouldnt with that:
falcon(_dot_)org(_at_)bob(_dot_)com
bill(_at_)falcon(_dot_)com
oblert(_at_)mort(_dot_)falcon(_dot_)org(_dot_)au
basically, regex leaves the @ sign alone, right?
(im just curious at this stage, im definetly making plans to bone up on
regex now.. im really clueless when it comes to them)
> procmail: Opening "/var/mail/falcontest"
> procmail: Acquiring kernel-lock
> Subject: Returned mail: Can't create output: Error 0
> Folder: **Bounced** 2120
Okay, now we're seeing clues. Are the permissions on /var/mail and the
file you're trying to write to set up properly? Is Procmail installed
with the suid and gid bits properly set up?
heres what I have:
-rwsr-sr-x 1 root mail 68676 Apr 22 13:10 /usr/local/bin/procmail
(/var/ :)
drwxrwsrwt 3 root mail 512 Apr 29 13:49 mail
drwxrwxr-x 5 root sys 512 Apr 25 04:05 adm
drwxrwxrwx 2 root other 512 Apr 29 13:47 test
(yes, test is 777 for now.. i wanted to eliminate that as this problem..
i.e. i've already been through the perms.. though /var/mail looks a tad
interesting).
whats the "2120" code to the right of "Folder: **Bounced**" mean?
most of the time i get a 320 code. as of late, however, i've gotten a
533, a 2132, a 527, and a 2120.