Hi Eric/Maxwell, Thanks local DNS solved the problem. Another issue with that client is the below error:
'ami...@rediffmail.com [1]' on 25/06/2010 05:27 PM 451 DNS temporary failure (#4.5.1 - chkuser) When there internet is down and if any user send mail to external domain they immediately get above bounced message. I explained them it is because DNS is not resolvable when internet is down. But they want mail should be in queue atleast for 24 hrs even if internet is down. I increased queue life to 24 hrs but no success. How can I stop such bounce message to user for 24 hrs? Else how can stop this bounce message completely from my QMT server. Regards, Amit At Wednesday, 23-06-2010 on 22:07 Eric Shubert wrote: Amit Dalia wrote: > > There ERP software needs only few things like incoming server, > outgoing server, sender id and receiver id. Now here sender id and > receiver id are from local domain of QMT. But getting error "421 > Refused. Your reverse DNS entry does not resolve" in their ERP > software. I'm not getting a clear picture of what the ERP software is doing. I don't know why it cares whether or not there's an rDNS entry, unless it's receiving mail itself. None the less, this appears to be a problem with name resolution. Once again, I think you'll need to configure AD's name resolution to satisfy this. I presume AD handles rDNS as well. > >> 3) I want to disable RDNS check for local ips. How to do this > and any > >> harm in doing this? > > Do you use spamdyke? If not, install it. That will solve this problem. > Alternatively, you can configure local clients to use port 587. > > Yes, I'm using Spamdyke. There is no option for port else I planning > to change smtp port to 587. Changing to port 587 won't help this. Apparently you have some local clients that aren't authenticating, otherwise spamdyke would allow them to send. You can allow unauthenticated senders by whitelisting the local IPs that do not authenticate, although this is generally a bad practice. You should make every effort possible to configure all clients to authenticate before resorting to whitelisting IPs. Also, whitelisting IPs in spamdyke will only allow unauthenticated senders to send to local domains. If you need to allow unauthenticated senders to send to external domains (a very bad practice), you'll need to add an entry in your tcp.smtp file as well. -- -Eric 'shubes' --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com Links: ------ [1] mailto:b_thomb...@rediffmail.com
