Michelle Konzack writes:
Hi Sam,Am 2009-02-13 18:08:18, schrieb Sam Varshavchik:Post what you see in syslog.noting in syslog but: ----[ '/var/log/mail.log' ]--------------------------------------------- Feb 14 02:19:19 samba3 courieresmtpd: started,ip=[::ffff:192.168.0.91] Feb 14 02:19:49 samba3 courieresmtpd: error,relay=::ffff:192.168.0.91,from=<[email protected]>: 417 DNS lookup failure: tamay-dogan.net. Try again later. Feb 14 02:20:15 samba3 courieresmtpd: started,ip=[::ffff:192.168.0.91] Feb 14 02:20:45 samba3 courieresmtpd: error,relay=::ffff:192.168.0.91,from=<[email protected]>: 417 DNS lookup failure: tamay-dogan.net. Try again later. Right it can not resolv the senders domain but I need a solution that courier accept always mail from me... Since I do not type my E-Mail by hand it is nearly impossibel, that the Domain can be wrong and has to be checked 300 times per day. Feb 14 02:35:31 samba3 courieresmtpd: started,ip=[::ffff:192.168.0.91] Feb 14 02:35:33 samba3 courierd: newmsg,id=0002C914.49961FE4.000020FC: dns; michelle1.private.tamay-dogan.net (michelle1.private.tamay-dogan.net [::ffff:192.168.0.91]) Feb 14 02:35:33 samba3 courierd: started,id=0002C914.49961FE4.000020FC,from=<[email protected]>,module=esmtp,host=lists.sourceforge.net,addr=<[email protected]> Feb 14 02:35:33 samba3 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 Feb 14 02:35:36 samba3 courieresmtp: id=0002C914.49961FE4.000020FC,from=<[email protected]>,addr=<[email protected]>: 250 2.0.0 Ok: queued as A91CB6509DD Feb 14 02:35:36 samba3 courieresmtp: id=0002C914.49961FE4.000020FC,from=<[email protected]>,addr=<[email protected]>,size=3686,success: delivered: server4.pinguin-hosting.de [88.198.11.108] Feb 14 02:35:36 samba3 courieresmtp: id=0002C914.49961FE4.000020FC,from=<[email protected]>,addr=<[email protected]>,size=3686,status: success Feb 14 02:35:36 samba3 courierd: completed,id=0002C914.49961FE4.000020FC Feb 14 02:35:36 samba3 courierd: Waiting. shutdown time=Sat Feb 14 02:40:36 2009, wakeup time=Sat Feb 14 02:40:36 2009, queuedelivering=0, inprogress=0 ...and here it worked again. (previous answer to Gordon) The weird thing is, that my DNS on <192.168.0.74> is the Master for <private.tamay-dogan.net> and for the rest a caching DNS. This mean, the domain <tamay-dogan.net> should be in the cache and courier accept it but it does not. Where can this error be?
Well, it's not in the cache, then. Your domain: tamay-dogan.net. 3600 IN MX 10 server4.pinguin-hosting.de.Your domain, tamay-dogan.net's TTL is 3600 seconds, or one hour. Even if you have it cached, after you're offline for an hour this record will be purged from your cache, so your DNS server will look it up again, and fail because your connection is down.
Even if you adjust your domain's TTL to one day, it won't help. Courier performs full MX resolution:
server4.pinguin-hosting.de. 3600 IN A 88.198.11.108Your ISP's DNS TTL is also only one hour, so you'll need to have them adjust the TTL for their own domain in order for your full MX resolution to work through.
You'll have to turn off DNS check on return addresses. If you're always sending your mail from this internal IP, use smtpaccess to set BOFHCHECKDNS=0 for your IP address.
pgpS9Z8QHSVlE.pgp
Description: PGP signature
------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
