-----BEGIN PGP SIGNED MESSAGE-----
Well, I've been reading this topic for a while, so now my curiosity
tell me to test this msn behaviour. I send a message to
[EMAIL PROTECTED] to test my connectivity with MSN.com
relay. Surprise, it worked!
2001-09-03 09:32:10.775721500 new msg 241676
2001-09-03 09:32:10.775767500 info msg 241676: bytes 1653 from
<[EMAIL PROTECTED]> qp 7120 uid 501
2001-09-03 09:32:10.943514500 starting delivery 716: msg 241676 to
remote [EMAIL PROTECTED]
2001-09-03 09:32:10.943619500 status: local 0/1 remote 1/30
2001-09-03 09:32:12.150171500 delivery 716: failure:
207.46.181.26_does_not_like_recipient./Remote_host_said:_550_5.1.1_twe
[EMAIL PROTECTED]/Giving_up_on_207.46.181.26
./
2001-09-03 09:32:12.244793500 status: local 0/1 remote 0/30
2001-09-03 09:32:12.490563500 bounce msg 241676 qp 7122
2001-09-03 09:32:12.523314500 end msg 241676
My qmail box is querying a Solaris box acting as a DNS server (just
cache), running BIND, to resolve MSN.com MXs. The only patch I've
installed on qmail it's the dns one.
So my question is: why the dns patch isn't the right solution?
- ---
Cordiali saluti / Best regards
Andrea Cerrito
^^^^^^^^^^^^^^
Net.Admin @ Centro MultiMediale di Terni S.p.A.
P.zzale Bosco 3A
05100 Terni IT
Tel. +39 0744 5441330
Fax. +39 0744 5441372
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQEVAwUBO5Mx9fo9HK4+yTI3AQFIcgf/TAUuJszZWY+5hGKSC3MT5sUIh73KUEP3
+FvBnvTCEegSouY1VQXOSgez/pNoBogqS0/zBlMzTUfKRt1L+L3dTpe3RMohTVU9
QMEBad/vsompGJScvwBcGmjvU62k4NV7M+bSfWZNHPMmijMiU0P5ijHtXwWKS9Q+
EDimt+ZyWxxfpsyD9vrMGzlVY9v5fkpETcXcYZD3yHl0UO09shiNuLu/t1eOCEFT
EaWOyjr1yBbUEgw2imYSprtW6G9v5a+A/TWfrJ4sfm0WAq3EJLAkBqV/YhKFcLX1
j4KSvzlxK5xr28ZkVJsi9sSRuRR/AqzRa1WTHzWyacG6ykLRJ3aNVA==
=8fai
-----END PGP SIGNATURE-----
