Ken, >The envelope recipient given to lmtpd (RCPT TO) >has to have the correct domain, otherwise lmtpd >won't find the mailbox path. If you can't
That seems logical... Just out of curiosity, why wasn't the LMTP daemon designed to support virtual domains in the same fashion the Cyrus IMAP server process does...? Meaning, if your SMTP servers are on separate machines that connect, via LMTP across the network, determine from the incoming IP address which domain the mail was intended to be delivered to... I can see setting up Postfix, or another MTA, to use a transport table to make an LMTP delivery to an IP address, regardless of the actual RCPT TO value in the message, and have Cyrus strip domain from the incoming connection... Just a thought. -John Ken Murchison wrote: > John C. Amodeo wrote: > > > I do have another question on the same topic... How can you ensure mail is > > delivered correctly (via LMTP) if the actual e-mail address is different than > > the domain Cyrus uses? > > > > For instance: > > > > email.dep1.rutgers.edu (Cyrus server IP) > > dep1.rutgers.edu (Cyrus domain) > > > > But the actual domain users send mail to is something like: > > > > department.rutgers.edu... or > > foo.rutgers.edu... > > > > Is this going to be trouble? > > The envelope recipient given to lmtpd (RCPT TO) has to have the correct > domain, otherwise lmtpd won't find the mailbox path. If you can't > change the addresses that people use externally, you can probably have > your MTA do the mapping for you. > > -- > Kenneth Murchison Oceana Matrix Ltd. > Software Engineer 21 Princeton Place > 716-662-8973 x26 Orchard Park, NY 14127 > --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp -- _____________________________________________________________ John C. Amodeo - Associate Director of Information Technology Faculty of Arts and Sciences -- Computer & Network Operations Rutgers, The State University of New Jersey 732.932.9455-voice 732.932.0013-fax
