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 not work well for me when assigning a value to the QMAILQUEUE global. Any suggestions, or wisdom on it's use?
Thanks,
Peter
Bill Shupp wrote:
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.smtp I can set the QMAILQUEUE variable based on the IP address of the originating system. Could I simply have all my coming from my scanning server use the regular qmail-queue, and have all of the other mail(coming from other hosts) scanned on the main POP3 server with QMail scanner?
Here is a brief diagram:
Mail from host disobeying MX priority -------------> pop3.mydomain.com - with qmailscanner
Mail from host obeying MX priority ------| |--- pop3d.mydomain.com without qmailscanner
| |
|-----scanner.mydomain.com-->|
I would think that this would lessen the load on the primary MX, correct?
Exactly. Either that, or have multiple scanners in front of it for redundancy. But the main idea being that any host listed as an MX record be a scanner as well to ensure that all mail is scanned.
Regards,
Bill Shupp
