Internal sendmail problems

O'Connor, Kevin KevinO'Connor at merseyfire.gov.uk
Wed Jan 2 18:08:46 GMT 2008


This is a multi-part message in MIME format.

------_=_NextPart_001_01C84D6A.84A1E11D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>The correct solution is to fix the broken DNS server that is=0D=0A>returni=
ng ServFail instead of NXDOMAIN on AAAA lookups.  IPv6 RFCs=0D=0A>have been=
 published for about 15 years so it's a sign of very=0D=0A>shoddy resolver =
software if it can't DTRT as of this late date.=0D=0A=0D=0AMatthew,=0D=0A=0D=
=0AThat just sounds like a polite way of saying "Throw the MS DNS in the bi=
n" which is sadly not an option.=0D=0AI'll stick with my kludge of using an=
 alias as a relay for all mail so that sendmail does not need to query DNS.=0D=
=0A=0D=0ABIND has a nightmare time synchronising zones from MS DNS due to t=
he non-standard record types they stick in the file so I'm not sure running=
 a local DNS server would not cause me more problems than I have now.=0D=0A=0D=
=0AServer 2008 is RTM in March and it has IPv6 built into the GUI so I'll w=
ait and see if their new improved DNS sorts it.=0D=0A=0D=0AThanks to all fo=
r the suggestions and pointers=0D=0A=0D=0AKevin=0D=0A_ _ _ _ _ _ _ _ _ _ _ =
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _=0D=0A=0D=0AThis e-mai=
l and any files transmitted with it are confidential and intended=0D=0Asole=
ly for the use of the individual or entity to whom they are addressed.=0D=0A=
If you have received this e-mail in error please notify the originator of t=
he message.=20=0D=0A=0D=0AAny views expressed in this message are those of =
the individual sender,=0D=0Aexcept where the sender specifies and with auth=
ority, states them to be=0D=0Athe views of Merseyside Fire & Rescue Service=
, (MFRS).=0D=0A=0D=0AIncoming and outgoing emails may be monitored in line =
with current legislation.=0D=0A=0D=0ASteps have been taken to ensure that t=
his email and attachments are=20=0D=0Afree from any virus.  In keeping with=
 good computing practice the=20=0D=0Arecipient should ensure they are actua=
lly virus free.=0D=0A=0D=0Ahttp://www.merseyfire.gov.uk/=0D=0A=0D=0A
------_=_NextPart_001_01C84D6A.84A1E11D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0D=0A<HTML>=0D=0A<HEAD>=0D=
=0A<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-88=
59-1">=0D=0A<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">=0D=0A<TITLE>RE: Internal sendmail problems</TITLE>=0D=0A</HEAD=
>=0D=0A<BODY>=0D=0A<!-- Converted from text/plain format -->=0D=0A=0D=0A<P>=
<FONT SIZE=3D2>&gt;The correct solution is to fix the broken DNS server tha=
t is<BR>=0D=0A&gt;returning ServFail instead of NXDOMAIN on AAAA lookups.&n=
bsp; IPv6 RFCs<BR>=0D=0A&gt;have been published for about 15 years so it's =
a sign of very<BR>=0D=0A&gt;shoddy resolver software if it can't DTRT as of=
 this late date.<BR>=0D=0A<BR>=0D=0AMatthew,<BR>=0D=0A<BR>=0D=0AThat just s=
ounds like a polite way of saying &quot;Throw the MS DNS in the bin&quot; w=
hich is sadly not an option.<BR>=0D=0AI'll stick with my kludge of using an=
 alias as a relay for all mail so that sendmail does not need to query DNS.=
<BR>=0D=0A<BR>=0D=0ABIND has a nightmare time synchronising zones from MS D=
NS due to the non-standard record types they stick in the file so I'm not s=
ure running a local DNS server would not cause me more problems than I have=
 now.<BR>=0D=0A<BR>=0D=0AServer 2008 is RTM in March and it has IPv6 built =
into the GUI so I'll wait and see if their new improved DNS sorts it.<BR>=0D=
=0A<BR>=0D=0AThanks to all for the suggestions and pointers<BR>=0D=0A<BR>=0D=
=0AKevin<BR>=0D=0A</FONT>=0D=0A</P>=0D=0A=0D=0A<br><br><table bgcolor=3Dwhi=
te style=3D"color:black"><tr><td><br>_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&n=
bsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_=
&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp=
;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_&nbsp;_<br=
>=0D=0A<br>=0D=0AThis&nbsp;e-mail&nbsp;and&nbsp;any&nbsp;files&nbsp;transmi=
tted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended<br=
>=0D=0Asolely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&n=
bsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.<br>=0D=
=0AIf&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;e-mail&nbsp;in&nbsp;e=
rror&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp=
;message.&nbsp;<br>=0D=0A<br>=0D=0AAny&nbsp;views&nbsp;expressed&nbsp;in&nb=
sp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&n=
bsp;sender,<br>=0D=0Aexcept&nbsp;where&nbsp;the&nbsp;sender&nbsp;specifies&=
nbsp;and&nbsp;with&nbsp;authority,&nbsp;states&nbsp;them&nbsp;to&nbsp;be<br=
>=0D=0Athe&nbsp;views&nbsp;of&nbsp;Merseyside&nbsp;Fire&nbsp;&amp;&nbsp;Res=
cue&nbsp;Service,&nbsp;(MFRS).<br>=0D=0A<br>=0D=0AIncoming&nbsp;and&nbsp;ou=
tgoing&nbsp;emails&nbsp;may&nbsp;be&nbsp;monitored&nbsp;in&nbsp;line&nbsp;w=
ith&nbsp;current&nbsp;legislation.<br>=0D=0A<br>=0D=0ASteps&nbsp;have&nbsp;=
been&nbsp;taken&nbsp;to&nbsp;ensure&nbsp;that&nbsp;this&nbsp;email&nbsp;and=
&nbsp;attachments&nbsp;are&nbsp;<br>=0D=0Afree&nbsp;from&nbsp;any&nbsp;viru=
s.&nbsp;&nbsp;In&nbsp;keeping&nbsp;with&nbsp;good&nbsp;computing&nbsp;pract=
ice&nbsp;the&nbsp;<br>=0D=0Arecipient&nbsp;should&nbsp;ensure&nbsp;they&nbs=
p;are&nbsp;actually&nbsp;virus&nbsp;free.<br>=0D=0A<br>=0D=0Ahttp://www.mer=
seyfire.gov.uk/<br>=0D=0A<br>=0D=0A</td></tr></table></BODY>=0D=0A</HTML>
------_=_NextPart_001_01C84D6A.84A1E11D--





More information about the Ukfreebsd mailing list