LDAP routing.
in [Sendmail]
|
From: David F. Skoll on 7 Jul 2010 21:58 Jim Howell wrote: > Yes, these are primarily for inbound email to be forwarded to > where the user wants it to go. Users don't have accounts on the servers > so a .forward isn't viable. You probably have to set up your aliases using LDAP also, as described at http://www.sendmail.org/m4/ldap.html Regards, David.
From: Jim Howell on 8 Jul 2010 09:54 Hi, The information is in LDAP already. Currently the lookups are done via phquery using a ph2ldap gateway and forwarding that way. This is really old and obviously we'd like to get rid of it. Using LDAP routing via Sendmail is an obvious choice. The mailRoutingAddress attribute has one or more addresses that the email is forwarded to, each address is comma delimited. If the user has one address in mailRoutingAddress it works fine, but if a user wants to forward to multiple places then we run into issues. Jim Grant Taylor wrote: > On 07/07/10 15:33, Jim Howell wrote: >> Hi, > > *wave* > >> Yes, these are primarily for inbound email to be forwarded to where >> the user wants it to go. Users don't have accounts on the servers so >> a .forward isn't viable. > > If you don't have an account / .forward file, how are you doing your > forwarding now? > > > > Grant. . . .
From: Jim Howell on 8 Jul 2010 10:00 Hi, We are using Exchange for email. The forwarding I'm talking about is for mail coming in from outside Exchange, mostly from the outside world. We use Linux machines to handle that traffic and users may use our Exchange servers or their own departmental machines, hence the forwarding need. Jim Andrzej Adam Filip wrote: > Jim Howell <jwh2(a)cornell.edu> wrote: >> Grant Taylor wrote: >>> On 07/07/10 14:38, Jim Howell wrote: >>>> We are currently switching to LDAP routing via Sendmail. We >>>> currently allow users to forward their email to multiple accounts. >>>> It appears that the mailRoutingAddress attribute is a single value >>>> attribute and can only forward to one account. How could I setup >>>> forwarding to multiple accounts? Thanks.. >>> It is my (mis)understanding (I've never used LDAP routing) that LDAP >>> routing is (primarily) used for inbound email routing. At least in >>> such as to what internal server should the message be routed to. >>> >>> With this in mind, can't you continue using .forward files on >>> individual servers? I would think that LDAP routing would get the >>> mail to the proper internal server that would then forward the >>> message on out to any number of destinations like you are currently >>> doing. >> Yes, these are primarily for inbound email to be forwarded to >> where the user wants it to go. Users don't have accounts on the >> servers so a .forward isn't viable. > > Which POP/IMAP server do you use? > > Have you considered using POP/IMAP server with sieve scripts support? > [ e.g. Cyrus or Dovecot ] > It should allow users to select multiple forwarding addresses themselves. >
From: Erich Titl on 8 Jul 2010 10:26 at 08.07.2010 03:58, David F. Skoll wrote: > Jim Howell wrote: > >> Yes, these are primarily for inbound email to be forwarded to >> where the user wants it to go. Users don't have accounts on the servers >> so a .forward isn't viable. > > You probably have to set up your aliases using LDAP also, as > described at http://www.sendmail.org/m4/ldap.html Or define a group on the M$ infrastructure cheers ET
From: Jim Howell on 8 Jul 2010 11:08 M$? Microsoft? Erich Titl wrote: > at 08.07.2010 03:58, David F. Skoll wrote: >> Jim Howell wrote: >> >>> Yes, these are primarily for inbound email to be forwarded to >>> where the user wants it to go. Users don't have accounts on the servers >>> so a .forward isn't viable. >> You probably have to set up your aliases using LDAP also, as >> described at http://www.sendmail.org/m4/ldap.html > > Or define a group on the M$ infrastructure > > cheers > > ET >
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: Using a regex to match recipient Next: DLP (was: beginers info) |