Re: [vps-mail] Installing SCBL for sendmail - need help, please

["Bennett Lanford" <ben@xxxxxxxxxxxxx>]

Marjolein Katsma <tfyj8lv02@xxxxxxxxxxxxxx> said:


> Although I didn't spell it out, I did look at the provided .mc samples and 
the .cf files generated from them. If I could have found a simple "superset" I 
would have used that - but none of them actually is.
>

If you need additional functionality, the standard way is generally to add 
them with FEATURES, or you can modify the standard rule sets (check_mail, 
check_rcpt, etc.) by adding special "local" versions of them (following strict 
conventions, of course) to the mc file. Then the local versions are called 
before the "standard" (i.e. shipped by sendmail.org) versions.

> Additional point:
> I originally reasoned that default-procmail-lda.mc was the most likely 
"best" equivalent to use; I see it supports procmail (which I'd like to use at 
a later point). Problem is, from the descriptions I'm not quite sure whether 
it merely "supports" procmail or _requires_ procmail to be installed (which I 
haven't done yet - one change at a time is enough!).

It *requires* procmail to be installed. If you use a procmail_lda version of 
an mc file, you must first vinstall procmail. (Actually, when you vinstall 
procmail, it checks to see if your sendmail.cf file uses procmail as the LDA. 
If it doesn't, then it vinstalls sendmail [if necessary] and copies one of the 
cf files that support procmail from ~/usr/local/sendmail/cf/cf ... at least it 
did last time I checked. It might interact with you a bit and ask if you want 
to change cf files, etc., etc.)

> Still, since functionally it looked closest to what I had (and want to have)
, that's what I used to generate a .cf file from that I hoped I could copy 
portions from to my original sendmail.cf. Which obviously didn't quite work...

What sorts of things do you want to copy from the original sendmail.cf?

>
> So... Starting from the other end, as it were, I'll now have to learn how to 
actually create an .mc file (and maybe supporting file(s)) that will generate 
something equivalent (or a superset that will work). Starting from the 
"superset" idea, three points come up:
>
> 1. When I found out that spammers could verify email addresses on the 
server, I wrote support and they added a 'Opnovrfy' option to sendmail.cf for 
me (although they downplayed the importance of that - but I _had_ seen 
spammers actually using VRFY against the server). Later, studying the subject 
(and sendmail) a bit more, I changed that myself to 'Opgoaway'.
>         => None of the (four) provided sample .mc files suggest any way for 
me to specify such an option. Can I do that in .mc, or would I still need to 
edit the generated .cf file to get the same option? If in .mc (preferred), 
what's the syntax for specifying this?

Something like:

define(`confPRIVACY_FLAGS',`goaway')

You can add multiple flags by separating them with commas. For example:

define(`confPRIVACY_FLAGS',`goaway,noetrn')

> 2. Provider added support for one extra domain for me (and were kind enough 
to tell me what they did); later I added another domain myself. This takes the 
form of 'Cwlocalhost firstdomain.com second.tld'
>         => It seems .mc files do not directly support this, but I have to 
create an external file with the domains to be supported?
> (If so, there's an equivalent, but I'll need to create an extra file, merely 
generating a .cf from .mc would not be sufficient.)

The mc-generated cf files in the sendmail vinstallall contain a line that 
begins:

Fw

and references a file named /etc/local-host-names

(Fw is similar to Cw: both lines populate the class w ($=w). The Fw line 
populates it from a file.)

The "modern" way to populate $=w is to list the domains in 
~/etc/local-host-names. (The local-host-names file has become a standard 
sendmail.org idiom. It is used only by sendmail, AFAIK.)

I generally list my domains one per line in that file.

You can verify that they work by entering a command something like:

echo '$=w' | virtual sendmail -bt

> 3. A third customization I did myself, after seeing another (access) 
provider's host headers specify a 'for' part in the headers. I managed to 
figure out how to define that in sendmail.cf.
>         => Looking at the generated .cf files, it looks as though header 
writing _is_ actually a superset of what I have now, so that's fine.
>
> If you (or someone) could answer or confirm these three issues for me, I can 
probably get to the point where I have an .mc file (plus whatever else is 
needed) to use to generate a replacement for my tired old sendmail.cf - and 
then continue from there.

The LOCAL_CONFIG section of the mc file is for defining headers. In my mc file 
(for example) my LOCAL_CONFIG section begins like this:

LOCAL_CONFIG
H?l?X-Rcpt-To: $u

The result is that my sendmail includes an X-Rcpt-To: header in every message 
.. (If you don't like the default way that the mc compiler defines a header, 
you can redefine it in the LOCAL_CONFIG section of the mc file ...)

Ben

(P.S. In one of your notes you mentioned the spammers.db file. As long as you 
are upgrading your sendmail.cf file, you might want to investigate the access.
db file. It has all the functionality of spammers, plus lots more.)

--
Bennett Lanford
ben@xxxxxxxxxxxxx


======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
======================================================================