Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Jake Vickers
Eric Shubert wrote: I'd like to know if this works, but I don't expect it will. I believe that chkuser is not finding an MX record for the backup.mydomain.com domain, and this cannot be specified in the hosts file. An MX record for backup.mydomain.dom would need to be added to the

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Jake Vickers
Maxwell Smart wrote: Like this? ip.of.server.dotted:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 ip.of.server.dotted:allow If you want to apply a line to multiple consecutive hosts, you can do this: 192.168.1.:allow,[whatever-else] This

[qmailtoaster] Re: Server Mail

2009-10-30 Thread Eric Shubert
Jake Vickers wrote: Eric Shubert wrote: I'd like to know if this works, but I don't expect it will. I believe that chkuser is not finding an MX record for the backup.mydomain.com domain, and this cannot be specified in the hosts file. An MX record for backup.mydomain.dom would need to be

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Aleksander Podsiadly
W dniu 30.10.2009 18:32, Eric Shubert pisze: While I agree with your position and hypothetical scenario, I don't believe that adding an MX record for each host is the correct nor best solution. I don't see any purpose in adding an MX record for each host that sends email. [...] That's

[qmailtoaster] Re: Server Mail

2009-10-30 Thread Eric Shubert
Aleksander Podsiadly wrote: W dniu 30.10.2009 18:32, Eric Shubert pisze: While I agree with your position and hypothetical scenario, I don't believe that adding an MX record for each host is the correct nor best solution. I don't see any purpose in adding an MX record for each host that

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Aleksander Podsiadly
W dniu 30.10.2009 20:43, Eric Shubert pisze: I'm not (necessarily) disputing that. I believe that the sending server should probably not have the host name included in the address after the @. IE @host.domain.com should simply be @domain.com, and this is configured on the sending server.

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Jake Vickers
Eric Shubert wrote: While I agree with your position and hypothetical scenario, I don't believe that adding an MX record for each host is the correct nor best solution. I don't see any purpose in adding an MX record for each host that sends email. An MX record is intended as an indication

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread Maxwell Smart
OK, here's my setup, slightly different, but seems to be same issue. I have a production mail server it's working perfectly fine. I have a test server on the LAN 192.168.0.195 I want it to be able to send the logwatch e mails to my address on my production server, but I get this error.

[qmailtoaster] Re: Server Mail

2009-10-30 Thread Eric Shubert
Jake Vickers wrote: Eric Shubert wrote: While I agree with your position and hypothetical scenario, I don't believe that adding an MX record for each host is the correct nor best solution. I don't see any purpose in adding an MX record for each host that sends email. An MX record is

[qmailtoaster] Re: Server Mail

2009-10-30 Thread Eric Shubert
I believe that the correct way is to configure the test server to use a valid domain in the sender address. It's also a good idea to configure the test server to authenticate itself as well. How you do this depends on which mail software the server uses. Maxwell Smart wrote: OK, here's my

Re: [qmailtoaster] Re: Server Mail

2009-10-30 Thread d...@acbsco.com
Don't know if this is what you are looking for, but I have a server with an private ip of 192.168.5.15 (pluto) running sendmail.  I have a qmt server with private ip address 192.168.5.2 (mercury).  I want to send all email (both local and remote) from pluto through mercury.  I do the

[qmailtoaster] Re: Server Mail

2009-10-29 Thread Eric Shubert
I'd like to know if this works, but I don't expect it will. I believe that chkuser is not finding an MX record for the backup.mydomain.com domain, and this cannot be specified in the hosts file. An MX record for backup.mydomain.dom would need to be added to the authoritative DNS for the

Re: [qmailtoaster] Re: Server Mail

2009-10-29 Thread Maxwell Smart
Here I thought I was finally starting to understand this. :( At least the DNS part was right. Eric Shubert wrote: I'd like to know if this works, but I don't expect it will. I believe that chkuser is not finding an MX record for the backup.mydomain.com domain, and this cannot be specified

[qmailtoaster] Re: Server Mail

2009-10-29 Thread Eric Shubert
No. Use a separate line for that. Maxwell Smart wrote: Can multiple addresses be used in this setting? ip.of.server.dotted:allow,ip.of.server.dotted:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 Andreas Galatis wrote: Hi Mike, for my

Re: [qmailtoaster] Re: Server Mail

2009-10-29 Thread Maxwell Smart
Like this? ip.of.server.dotted:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 ip.of.server.dotted:allow Eric Shubert wrote: No. Use a separate line for that. Maxwell Smart wrote: Can multiple addresses be used in this setting?

[qmailtoaster] Re: Server Mail

2009-10-29 Thread Eric Shubert
While this solution should work, it does carry a potential security risk. If the web servers are on a private subnet with the mail servers, the risk is pretty much negligible though. The most secure solution is to have your web servers authenticate themselves. I don't bother with sendmail, as

[qmailtoaster] Re: Server Mail

2009-10-29 Thread Eric Shubert
Yes, but you need to include all of the appropriate variable declarations on each line. They don't carry forward. Maxwell Smart wrote: Like this? ip.of.server.dotted:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 ip.of.server.dotted:allow Eric

RE: [qmailtoaster] Re: Server Mail

2009-10-29 Thread Mike Canty
] Re: Server Mail I'd like to know if this works, but I don't expect it will. I believe that chkuser is not finding an MX record for the backup.mydomain.com domain, and this cannot be specified in the hosts file. An MX record for backup.mydomain.dom would need to be added to the authoritative