On Fri, Feb 12, 1999 at 10:16:23PM -0800, Russ Allbery wrote:
> Harald Hanche-Olsen <[EMAIL PROTECTED]> writes:
>
> > Sounds like you need the serialmail from DJB's collection.
[...]
> That's what I was thinking too, but that doesn't take care of this part:
>
> > - Donna Phillips <[EMAIL PROTECTED]>:
> > | [...] Basically what people are wanting is this: When they are
> > | dialed up mail gets delivered straight to thier machine (Not to the
> > | mail server then to thier machine) [...]
>
> Assuming the "not to the mail server then to their machine" should be
> taken literally, that's going to require playing games with DNS MX records
> based on whether the customer is dialed in.
Someday I thougt about about the following:
domain: client.isp.net.
primary MX is mailhub.isp.net.
the client has his own mailserver, with ip address 192.168.42.1.
state 1 (client offline):
catch-all maildirdelivery on mailhub.isp.net.
control/virtualdomains:
client.isp.net:alias-ppp-clientid
~alias/.qmail-ppp-clientid:
./spool/clientid/
state 2 (client dials up):
- add the customers ip to control/smtproutes:
client.isp.net:[192.168.42.1]
- remove the client domain from control/virtualdomains.
- kill -HUP qmail-send
- flush the catch-all maildir via serialmail:
# maildir2smtp ~alias/spool/clientid/ alias-ppp-clientid- 192.168.42.1 helo
state 3 (client online):
mail goes directly to the clients mailserver, via smtproutes.
state 4 (clients disconnects):
- add the client domain to virtualdomains again.
- kill -HUP qmail-send
- remove the smtproutes entry.
The whole thing though would require reliable communications
between the ISPs mailhub and their terminal server.
regards, lars
