[toaster] secondary MX

2007-03-22 Thread Maciej Sołtysiak
Hi, I just set up a secondary MX for my domains, and it works of course. But, what I wanted is that for both MXes to chkuser from mysql. When sending mail through the first MX (it has mysql and the domain maildirs) it can check if a user does not exist and say: no such user. The other MX suppose

Re: [toaster] Secondary MX Question

2003-12-21 Thread Bill Shupp
Peter Maag wrote: Bill, Thanks for the quick response. Would you happen to know the correct syntax for those lines in the tcp.smtp file? I am unsure which variables actually need to be assigned different values(I know the QMAILQUEUE) one does, but the others I am unsure of. Also, in the pa

Re: [toaster] Secondary MX Question

2003-12-20 Thread Peter Maag
Bill, Thanks for the quick response. Would you happen to know the correct syntax for those lines in the tcp.smtp file? I am unsure which variables actually need to be assigned different values(I know the QMAILQUEUE) one does, but the others I am unsure of. Also, in the past tcp.smtp did no

Re: [toaster] Secondary MX Question

2003-12-20 Thread Bill Shupp
Peter Maag wrote: Bill, Thats what I was thinking of doing, however what(in the unlikely event) would happen if the scanning server went down? Mail would be queued for 3 days on the sender's end, correct? Maybe you can tell me if this is possible using just QMail settings. I know in tcp.s

Re: [toaster] Secondary MX Question

2003-12-20 Thread Bill Shupp
Peter Maag wrote: To The List, I have been trying to find a solution to this problem for quite some time, didn't find it so I thought I would ask you fine folks. Currently, in DNS(djbdns) I use the following entries for MX records: @domain.com::scanner.domain.com:1

[toaster] Secondary MX Question

2003-12-20 Thread Peter Maag
To The List, I have been trying to find a solution to this problem for quite some time, didn't find it so I thought I would ask you fine folks. Currently, in DNS(djbdns) I use the following entries for MX records: @domain.com::scanner.domain.com:1 @domain.com: