Folks,

I've seen plenty of posts on suggestions for making this work, and I've
got sendmail blindly forwarding all mail for the domain to exchange,
but I'd like to check the recipient at the boundry. I've tried the
access map and virtuser methods, and neither of them seem to work for
this particular instance. In short, sendmail either forwards it like it
did before, or denies the relay (complaining about a failed name lookup
of the host I'm using as a test).

Here's the relevant information:

- Sendmail is the latest copy as of Jan 16, 07.
- I host the domain example.com. My mail server is mail.example.com and
it is the only MX entry in the DNS tree.
- There is a second mail server called mailbox.example.com. This is the
repository for the mailboxes. Never mind that it happens to be an
exchange server (the list of users is generated from active directory
with an LDAP query script every hour).
- The sendmail gateway is configured with the following sendmail.mc
file:

divert(0)dnl
VERSIONID(`$Id: generic-linux.mc,v 8.1 1999/09/24 22:48:05 gshapiro Exp
$')
OSTYPE(linux)dnl
define(`confBAD_RCPT_THROTTLE', `3')dnl
define(`confTO_IDEN', `0s')dnl
define(`confMILTER_LOG_LEVEL', `1')dnl
FEATURE(stickyhost)dnl
FEATURE(`mailertable', `hash /etc/mail/mailertable')dnl
define(`confDOUBLE_BOUNCE_ADDRESS', `')dnl
define(`confPRIVACY_FLAGS',`goaway,noreceipts,nobo dyreturn')dnl
define(`confDELIVERY_MODE', `q')dnl
FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access')dnl
undefine(`ALIAS_FILE')dnl
define(`confFORWARD_PATH')dnl
undefine(`UUCP_RELAY')dnl
undefine(`BITNET_RELAY')dnl
undefine(`DECNET_RELAY')dnl
INPUT_MAIL_FILTER(`mimedefang',
`S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:1m;R:1m')
FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable')dnl
MAILER(smtp)dnl

- The /etc/mail/local-host-names contains
mail.example.com

- The /etc/mail/access file contains the following:
To:user@example.com RELAY
Tother@example.com RELAY
To:example.com ERROR:5.5.1:550 User Unknown

- The /etc/mail/mailertable file contains:
example.com smtp:[mailbox.example.com]

- The /etc/mail/virtusertable is empty (currently)
- The /etc/mail/relay-domains file is empty (currently)

With this setup, I would have expected it to forward mail. This
generates a Relaying denied error due to a IP name lookup failure. If I
change RELAY to OK in the access file, nothing changes. If I add
example.com to the local-host-names nothing happens. If I add
example.com to the relay-domains file, it forwards mail blindly without
regard to the access file. Not what I want. I tried setting
'To:example.com OK' in the access file (as the only entry), and then
building a virtusertable consisting of entries like 'user@example.com
!' and such, and for a final entry '@example.com error:nouser User
Uknown'. This produced the same results. If the relay-domains file did
not contain example.com then it was deined with an IP name lookup
failure. If it did, the mail was accepted (regardless of destination
address) and forwarded along.

So, what simple tiny thing am I missing here? All I want it to do is
accept a message if it's in a list of users (either in access or
virtuser) and then forward it along to another host. If the user was
not in the list, I want it to reject the mail with a user unknown
message.

- Foxbird

Foxbird wrote:
> Folks,
>
> I've seen plenty of posts on suggestions for making this work, and I've
> got sendmail blindly forwarding all mail for the domain to exchange,
> but I'd like to check the recipient at the boundry. I've tried the
> access map and virtuser methods, and neither of them seem to work for
> this particular instance. In short, sendmail either forwards it like it
> did before, or denies the relay (complaining about a failed name lookup
> of the host I'm using as a test).
>
> Here's the relevant information:
>
> - Sendmail is the latest copy as of Jan 16, 07.
> - I host the domain example.com. My mail server is mail.example.com and
> it is the only MX entry in the DNS tree.
> - There is a second mail server called mailbox.example.com. This is the
> repository for the mailboxes. Never mind that it happens to be an
> exchange server (the list of users is generated from active directory
> with an LDAP query script every hour).

I am using LDAP routing with a real time ldap query for this purpose.
Works like a charm with

define(`confLDAP_DEFAULT_SPEC', `-h "xx.xx.xx.xx" -b "DC=XX,DC=GROUP" -d
"CN=query,OU=ressourcen,DC=XX,DC=GROUP" -MLDAP_AUTH_SIMPLE
-P/etc/mail/ldap_pass')dnl

LDAPROUTE_DOMAIN_FILE(`/etc/mail/ldap_route_domains')dnl

FEATURE(`ldap_routing', `null', `ldap -1 -T<TMPF> -v mail -k
(&(|(objectclass=user)(objectclass=group))(proxyAd dresses=smtp:%0))',
`bounce')dnl

cheers

Erich

mega wrote:
> Foxbird wrote:
> > Folks,
> >
> > I've seen plenty of posts on suggestions for making this work, and I've
> > got sendmail blindly forwarding all mail for the domain to exchange,
> > but I'd like to check the recipient at the boundry. I've tried the
> > access map and virtuser methods, and neither of them seem to work for
> > this particular instance. In short, sendmail either forwards it like it
> > did before, or denies the relay (complaining about a failed name lookup
> > of the host I'm using as a test).
>
> I am using LDAP routing with a real time ldap query for this purpose.
> Works like a charm with
>
> define(`confLDAP_DEFAULT_SPEC', `-h "xx.xx.xx.xx" -b "DC=XX,DC=GROUP" -d
> "CN=query,OU=ressourcen,DC=XX,DC=GROUP" -MLDAP_AUTH_SIMPLE
> -P/etc/mail/ldap_pass')dnl
>
> LDAPROUTE_DOMAIN_FILE(`/etc/mail/ldap_route_domains')dnl
>
> FEATURE(`ldap_routing', `null', `ldap -1 -T<TMPF> -v mail -k
> (&(|(objectclass=user)(objectclass=group))(proxyAd dresses=smtp:%0))',
> `bounce')dnl
>
> cheers
>
> Erich

Erich,

Thanks for the ful advice, but that's not quite what I want to do.
I'm trying to keep the valid users on the mailserver itself in the
offchance that the AD/Exchange server goes down (yes, it caches, and
yes I can optionally specify passthru). In addition, the list of valid
users does not come from a single AD. It's a list that's generated from
two different AD servers and then the mailertable routes the domains
appropriately. If the LDAP mapping in sendmail can handle querying one
server for domains @example.com and another server for domains in
@other.com, that'd be great, but I didn't see any documentation on how
to set that up. I don't want to query example.com and burden it with
spurious requests for other.com if it doesn't need it, particularly if
our volume of mail is quite high.

So, the question still remains: How would one setup a sendmail gateway
to forward mail to several domains if a list of valid user@domain
addresses can be generated, and the mailertable handled? Remember, no
local users. I can put the list of users in either a virtusertable, or
an access map. In either case, I need to know what to put in the
local-host-names, relay-domains, and other map files, as well as if I'm
masquerading (I suspect we're not here).

- Foxbird

Hi

Foxbird wrote:
....

>
> So, the question still remains: How would one setup a sendmail gateway
> to forward mail to several domains if a list of valid user@domain
> addresses can be generated, and the mailertable handled? Remember, no
> local users. I can put the list of users in either a virtusertable, or
> an access map. In either case, I need to know what to put in the
> local-host-names, relay-domains, and other map files, as well as if I'm
> masquerading (I suspect we're not here).

I _believe_ it would be pretty much the same set up with the exception
that a different map (not LDAP) is used. The feature ldap_routing can be
used with different map types.

Erich

Foxbird wrote:
> I've seen plenty of posts on suggestions for making this work, and I've
> got sendmail blindly forwarding all mail for the domain to exchange,
> but I'd like to check the recipient at the boundry. I've tried the
> access map and virtuser methods, and neither of them seem to work for
> this particular instance. In short, sendmail either forwards it like it
> did before, or denies the relay (complaining about a failed name lookup
> of the host I'm using as a test).

What you are wanting to do is configure Sendmail to relay messages for
specific domain(s) to your internal mail server(s).

1) Add the domain(s) that you want to relay messages for to your
relay-domains (class R) file.

2) Add entries in your Access DB for each valid recipient. I.e:
To:valid@domain.tld OK

3) Add a catch all entries for the domain(s) in question to REJECT
messages. I.e:
To:domain.tld REJECT

4) Set up a mailertable entry to tell Sendmail to relay messages for
the domain(s) to the internal mail server(s). I.e:
domain.tld relay:mailbox.domain.tld

5) Remove any stale config from any files not listed above.

This *should* get you the results that you are after.



Grant. . . .

Grant Taylor wrote:
> Foxbird wrote:
> > I've seen plenty of posts on suggestions for making this work, and I've
> > got sendmail blindly forwarding all mail for the domain to exchange,
> > but I'd like to check the recipient at the boundry. I've tried the
> > access map and virtuser methods, and neither of them seem to work for
> > this particular instance. In short, sendmail either forwards it like it
> > did before, or denies the relay (complaining about a failed name lookup
> > of the host I'm using as a test).
>
> What you are wanting to do is configure Sendmail to relay messages for
> specific domain(s) to your internal mail server(s).
>
> 1) Add the domain(s) that you want to relay messages for to your
> relay-domains (class R) file.
>
> 2) Add entries in your Access DB for each valid recipient. I.e:
> To:valid@domain.tld OK
>
> 3) Add a catch all entries for the domain(s) in question to REJECT
> messages. I.e:
> To:domain.tld REJECT
>
> 4) Set up a mailertable entry to tell Sendmail to relay messages for
> the domain(s) to the internal mail server(s). I.e:
> domain.tld relay:mailbox.domain.tld
>
> 5) Remove any stale config from any files not listed above.
>

Grant,

I'd love it if that were the case, but it doesn't seem to be so. I've
done all that you mentioned, but this particular configuration causes
sendmail to forward everything destined to domain.tld. As a recap,
here's the current content of the various files you mentioned.

1) class R (/etc/mail/relay-domains)
domain.tld

2) access map (/etc/mail/access)
To:user@domain.tld OK
To:domain.tld REJECT

3) mailertable (/etc/mail/mailertable)
domain.tld smtp[mailbox.domain.tld]

4) /etc/mail/local-host-names
[empty]

5) the sendmail.mc file
divert(0)dnl
VERSIONID(`$Id: generic-linux.mc,v 8.1 1999/09/24 22:48:05 gshapiro Exp
$')
OSTYPE(linux)dnl
define(`confBAD_RCPT_THROTTLE', `3')dnl
define(`confTO_IDEN', `0s')dnl
define(`confMILTER_LOG_LEVEL', `1')dnl
FEATURE(stickyhost)dnl
define(`confDOUBLE_BOUNCE_ADDRESS', `')dnl
define(`confPRIVACY_FLAGS',`goaway,noreceipts,nobo dyreturn')dnl
define(`confDELIVERY_MODE', `q')dnl
undefine(`ALIAS_FILE')dnl
define(`confFORWARD_PATH')dnl
undefine(`UUCP_RELAY')dnl
undefine(`BITNET_RELAY')dnl
undefine(`DECNET_RELAY')dnl
INPUT_MAIL_FILTER(`mimedefang',
`S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:1m;R:1m')
FEATURE(`mailertable', `hash /etc/mail/mailertable')dnl
FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access')dnl
FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable')dnl
FEATURE(`use_cw_file')dnl
MAILER(smtp)dnl

Now, when sending mail to baduser@domain.tld (which should be denied),
it's accepting the mail, processing it, and forwarding it on to the
host specified in the mailertable. Obviously, looking at the map this
shouldn't be happening, but it seems to be that it is. I read somewhere
that the R class causes it to ignore the information in the access map,
which seems to be the case. If I could make this problem go away, it'd
do what I want, but it doesn't seem to want to agree with this
configuration.

- Foxbird

Foxbird wrote:
> I'd love it if that were the case, but it doesn't seem to be so. I've
> done all that you mentioned, but this particular configuration causes
> sendmail to forward everything destined to domain.tld. As a recap,
> here's the current content of the various files you mentioned.

Hum. We must have some wires crossed as this is exactly what I'm doing
on my server now.

> 1) class R (/etc/mail/relay-domains)
> domain.tld

Ok.

> 2) access map (/etc/mail/access)
> To:user@domain.tld OK
> To:domain.tld REJECT

Ok

> 3) mailertable (/etc/mail/mailertable)
> domain.tld smtp[mailbox.domain.tld]

Ok.

> 4) /etc/mail/local-host-names
> [empty]

Ok.

> 5) the sendmail.mc file
> divert(0)dnl
> VERSIONID(`$Id: generic-linux.mc,v 8.1 1999/09/24 22:48:05 gshapiro Exp
> $')
> OSTYPE(linux)dnl
> define(`confBAD_RCPT_THROTTLE', `3')dnl
> define(`confTO_IDEN', `0s')dnl
> define(`confMILTER_LOG_LEVEL', `1')dnl
> FEATURE(stickyhost)dnl

I don't recall what "stickyhost" does off hand.

> define(`confDOUBLE_BOUNCE_ADDRESS', `')dnl

I'd put something in between the `' so that your double bounces would go
somewhere.

> define(`confPRIVACY_FLAGS',`goaway,noreceipts,nobo dyreturn')dnl
> define(`confDELIVERY_MODE', `q')dnl
> undefine(`ALIAS_FILE')dnl
> define(`confFORWARD_PATH')dnl
> undefine(`UUCP_RELAY')dnl
> undefine(`BITNET_RELAY')dnl
> undefine(`DECNET_RELAY')dnl
> INPUT_MAIL_FILTER(`mimedefang',
> `S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, T=S:1m;R:1m')
> FEATURE(`mailertable', `hash /etc/mail/mailertable')dnl
> FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access')dnl
> FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable')dnl
> FEATURE(`use_cw_file')dnl
> MAILER(smtp)dnl

Ok.

As I sit here and look at it, I don't see an AccessDB definition in your
mc file.

FEATURE(`access_db', `hash -T<TMPF> /etc/mail/access')

This could be why your AccessDB is not being honored.

> Now, when sending mail to baduser@domain.tld (which should be denied),
> it's accepting the mail, processing it, and forwarding it on to the
> host specified in the mailertable. Obviously, looking at the map this
> shouldn't be happening, but it seems to be that it is. I read somewhere
> that the R class causes it to ignore the information in the access map,
> which seems to be the case. If I could make this problem go away, it'd
> do what I want, but it doesn't seem to want to agree with this
> configuration.

The only thing that comes to mind is that possibly you did not rebuild
your maps? Remember to run
"makemap hash /etc/mail/access < /etc/mail/access"



Grant. . . .

Grant Taylor wrote:
> Hum. We must have some wires crossed as this is exactly what I'm doing
> on my server now.

Yes, I'd agree wholeheartedly with that statment. I figured it should
have worked from the onset as this is what I tried first step, but
something is obviously mucked up.

>
> I don't recall what "stickyhost" does off hand.
>

According to the sendmail.org website, it's used mostly with mail_hub
and local_relay options. It's used to keep the address of mail going to
a mailhub the same, instead of rewriting it (as in preventing
joe@domain.com from being written as joe@mailhub.domain.com). Just in
case there was an issue with this, I turned it off, and the same
results happened.

> > define(`confDOUBLE_BOUNCE_ADDRESS', `')dnl
>
> I'd put something in between the `' so that your double bounces would go
> somewhere.

It's a basic spam-stopping technique. This machine used to blindly
forward mail from the internet to an exchange server, and because it
wasn't looking up users, it would occasionally bounce mail to itself.
So this was undefined to eliminate all the post-master messages that
weren't important at the time.

> > FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access')dnl
>
> As I sit here and look at it, I don't see an AccessDB definition in your
> mc file.

Right there in the quotes above. Just to match your example, I removed
the -o argument, in case it has some bearing on things, and it didn't
change anything. So, that wasn't the issue.

>
> The only thing that comes to mind is that possibly you did not rebuild
> your maps? Remember to run
> "makemap hash /etc/mail/access < /etc/mail/access"
>

I made sure to rebuild them. I even deleted all the .db files, and ran
makemap over them all again, rebuilt the .cf file, and rebooted the
whole machine (hey, it works with windows!). Still, no joy on this
particular front.

Any more random thoughts? Do you have perhaps a minimal configuration
..mc file you could share that gets the job done? Perhaps I need
FEATURE(`blacklist_recipients') and/or FEATURE(`delay_checks'). Both of
them sound somewhat promising (since the To: prefix is used in the
map). An article that seems to cover some of what I'm after is here,
but the responses are varied. Any other advice would be appreciated.

Again, thanks for the !

- Foxbird

Foxbird wrote:
> Folks,
>
> I've seen plenty of posts on suggestions for making this work,

Let me repost my recap here.

----------
"How do I let my mx gateway server recognize which recipients are valid
on the final destionation/next hop server and which are not?"

Which has hit the newsgroup so frequently it really needs to be a faq
entry.

The short answers are:

*

Use ldap routing

see cf/README

+--------------+
| LDAP ROUTING |
-++--------------+

http://www.sendmail.org/m4/ldap_routing.html

*

Use virtusertable with undocumented feature and an entry for each
valid user and a catchall entry that @domain.com error:nouser

_VIRTUSER_STOP_ONE_LEVEL_RECURSION_

*

Use virtusertable with a RHS of "!" for each valid user and a
catchall entry that @domain.com error:nouser

*

Use access db with undocumented feature

define(`_RELAY_FULL_ADDR_', `1')

And put all your users in there

To:u...@example.com RELAY

*

use a milter of which there are several.

milter-ahead
j-chkmail
mimedefang
dnsbl
callahead-milter
milter-sav

A list of milters is available at
http://www.jmaimon.com/sendmail/milters

Foxbird wrote:
> Folks,
>
> With this setup, I would have expected it to forward mail. This
> generates a Relaying denied error due to a IP name lookup failure.

Try adding this to your sendmail.mc

define(`_RELAY_FULL_ADDR_', `1')

Also try the delay_checks and blacklists_to -- this way you can use the
rcpt blacklisting approach where you blacklist the entire domain and
allow each valid user.

Follow some of these instructions for easier debugging with rule test
mode

http://www.sendmail.org/~ca/email/chk-dbg.html

Why do you have this?

define(`confDELIVERY_MODE', `q')dnl

In article <1168992251.379046.30900@38g2000cwa.googlegroups.c om>
"jmaimon@ttec.com" <jmaimon@ttec.com> writes:
>
>Foxbird wrote:
>> Folks,
>>
>> I've seen plenty of posts on suggestions for making this work,
>
>Let me repost my recap here.

[snip]

> Use access db with undocumented feature
>
>define(`_RELAY_FULL_ADDR_', `1')
>
>And put all your users in there
>
>To:u...@example.com RELAY

This is exactly what is needed to match the setup the OP already has, of
course - it is also becoming an "official", documented feature as of
8.14 - from the Beta4 RELEASE_NOTES:

CONFIG: New option `relaytofulladdress' for FEATURE(`access_db')
to allow entries in the access map to be of the form
To:user@example.com RELAY

- and from its cf/feature/access_db.m4:

ifelse(lower(_ARG2_),`relaytofulladdress',`define( `_RELAY_FULL_ADDR_', `1')')

--Per Hedeland
per@hedeland.org

On 01/16/07 13:57, Foxbird wrote:
> Any more random thoughts? Do you have perhaps a minimal configuration
> .mc file you could share that gets the job done? Perhaps I need
> FEATURE(`blacklist_recipients') and/or FEATURE(`delay_checks'). Both of
> them sound somewhat promising (since the To: prefix is used in the
> map). An article that seems to cover some of what I'm after is here,
> but the responses are varied. Any other advice would be appreciated.

Here is the .mc file that I'm using in production.

VERSIONID(`$Id: generic-linux.mc,v 8.1 1999/09/24 22:48:05 gshapiro Exp $')
OSTYPE(linux)
DOMAIN(generic)
DAEMON_OPTIONS(`Address=206.152.114.68, Port=25, Name=MTA, InputMailFilters=milter-date;milter-spiff;milter-sender;milter-link;milter-spamc;clamav-milter')
DAEMON_OPTIONS(`Address=206.152.114.68, Port=587, Name=MSA, M=Ea, InputMailFilters=milter-date;milter-spiff;milter-sender;milter-link;milter-spamc')
DAEMON_OPTIONS(`Address=127.0.0.1, Port=25, Name=LMTA, InputMailFilters=milter-date;milter-spiff;milter-sender;milter-link;milter-spamc;clamav-milter')
DAEMON_OPTIONS(`Address=127.0.0.1, Port=587, Name=LMSA, M=Ea, InputMailFilters=milter-date;milter-spiff;milter-sender;milter-link;milter-spamc')
FEATURE(`access_db', `hash -T<TMPF> /etc/mail/access')
FEATURE(`no_default_msa')
FEATURE(`nouucp', `reject')
FEATURE(`mailertable', `hash /etc/mail/mailertable')
FEATURE(`domaintable', `hash /etc/mail/domaintable')
FEATURE(`genericstable', `hash /etc/mail/genericstable')
FEATURE(`generics_entire_domain')
FEATURE(`greet_pause', `3000')
FEATURE(`virtusertable', `hash /etc/mail/virtusertable')
FEATURE(`virtuser_entire_domain')
FEATURE(`smrsh')
FEATURE(`blacklist_recipients')
FEATURE(`delay_checks', `friend')
FEATURE(`local_procmail_lmtp')
FEATURE(`compat_check')
GENERICS_DOMAIN_FILE(`/etc/mail/generics-domains')
MASQUERADE_DOMAIN_FILE(`/etc/mail/masquerade-domains')
dnl Milter-Sender is doing something that needs the following M4 directive.
dnl I don't know what it is but it will not work with out it.
define(`confMILTER_MACROS_CONNECT', confMILTER_MACROS_CONNECT`, {client_addr}, {client_name}, {client_port}, {client_resolve}')
MAIL_FILTER(`milter-date', `S=unix:/var/lib/milter-date/socket, T=C:10s;S:10s;R:2m;E:2m')
MAIL_FILTER(`milter-spiff', `S=unix:/var/lib/milter-spiff/socket, T=C:10s;S:10s;R:2m;E:2m')
MAIL_FILTER(`milter-sender', `S=unix:/var/lib/milter-sender/socket, F=T, T=C:10s;S:10s;R:2m;E:2m')
MAIL_FILTER(`milter-link', `S=unix:/var/lib/milter-link/socket, T=C:10s;S:10s;R:2m;E:2m')
MAIL_FILTER(`milter-spamc', `S=unix:/var/lib/milter-spamc/socket, T=C:10s;S:10s;R:2m;E:2m')
dnl MAIL_FILTER(`milter-clamc', `S=unix:/var/lib/milter-clamc/socket, T=C:10s;S:10s;R:2m;E:2m')
MAIL_FILTER(`clamav-milter', `S=unix:/var/run/clamav/clamav-milter.sock, T=S:4m;R:4m')
dnl MAIL_FILTER(`milter-report', `S=unix:/var/lib/milter-report/socket, T=C:10s;S:10s;R:2m;E:2m')
TRUST_AUTH_MECH(`LOGIN PLAIN GSSAPI KERBEROS_V4 DIGEST-MD5 CRAM-M5')
define(`confAUTH_MECHANISMS', `LOGIN PLAIN GSSAPI KERBEROS_V4 DIGEST-MD5 CRAM-M5')
define(`confDEF_AUTH_INFO', `/etc/mail/auth/auth-info')
define(`confBAD_RCPT_THROTTLE', `2')
define(`confDOUBLE_BOUNCE_ADDRESS', `postmaster+rti02+doublebounce@riverviewtech.net')
define(`confEIGHT_BIT_HANDLING', `m')
dnl define(`confFALLBACK_MX', `tranq1.tranquility.net')
define(`confHOST_STATUS_DIRECTORY', `hoststatus')
define(`confMAX_MESSAGE_SIZE', `15000000')
define(`confPRIVACY_FLAGS', `needmailhelo,needexpnhelo,needvrfyhelo,authwarnin gs,nobodyreturn')
define(`confTO_IDENT', `0')
dnl define(`SMART_HOST', `tranq1.tranquility.net')
dnl define(`CERT_DIR', `MAIL_SETTINGS_DIR`'certs')
dnl define(`confCACERT', `CERT_DIR/cacert.pem')
dnl define(`confCACERT_PATH', `CERT_DIR/CA')
dnl define(`confSERVER_CERT', `CERT_DIR/host.cert')
dnl define(`confSERVER_KEY', `CERT_DIR/host.key')
dnl define(`confCLIENT_CERT', `CERT_DIR/host.cert')
dnl define(`confCLIENT_KEY', `CERT_DIR/host.key')
MAILER(local)
MAILER(smtp)
define(`MAILMAN_MAILER_UID', `gtaylor')
define(`MAILMAN_MAILER_GID', `mailman')
MAILER(mailman)
MAILER(nosrs)
HACK(srs)



Grant. . . .