From: j debert (jdebertgarlic.com)
Date: Fri May 02 2008 - 09:48:35 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Baker �ん�書����:
| Hi
|
| I have only used headers checks to hold for spam scanning.
|
| But today after a phising scam came in purporting to be from our
| helpdesk I put one like this in to block users from replying:
|
| /^To: fromthehelpdesk2007gmail.com/ REJECT
|

This is a regular expression form: (regexp or pcre)

However, you probably should escape the "." thus: "\.", since "."
means 'match any character' in regexps. Fortunately, it already
matches what you want to match. Using "\." will match it literally.

(It might be helpful to add text to your REJECT to explain why your
users' replies your "helpdesk" are being rejected or they might think
you don't like them anymore.)

| And then I get this warning when I run postmap
/etc/postfix/header_checks
|
| postmap: warning: /etc/postfix/header_checks, line 1: record is in
"key:
| value" format; is this an alias file?
|

Postmap can make a map from a regexp or pcre file but the results are
useless, afaik. The postmap manpage doesn't seem to indicate this.
Postmapping regexp files is a common mistake even among experienced
postfixers. (I wonder whether gurus ever make this mistake...)

| It appeared from all the information I could find that I was going
about
| this the right way and the check actually does seem to work.
|

You're apparently not using the resulting hash file header_checks.db,
so it will work just fine.

| But I'm not clear on exactly what is going on. Why do I get this
warning
| and is there a proper way to do this that will make the warning stop
| when I add a header_check?

Remember not to postmap regexp files like header_checks. perhaps
appending ".regex" or ".pcre" to these files will be a helpful reminder.

(Is there a regexp/pcre howto or tutorial somewhere? I bought a little
Bell manual 20+ years ago that covers regexps exhaustively so /I/
don't need it but surely such a howto would be useful for those who
don't have such a book. [sorry, don't mean to call anyone 'Shirley'!])

==
jd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFIGynBhpL3F+HeDrIRAkyVAKCLG76W7q8Q1yDBqM6HCy87T2YWjACgpW2c
/W58YEti1HoMjFGTxdt77GI=
=+NQC
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]