Date: Tue, 5 Jan 2016 11:12:38 -0500 From: Jon Radel <jon@radel.com> To: freebsd-questions@freebsd.org Subject: Re: sendmail config help Message-ID: <568BEB76.9040403@radel.com> In-Reply-To: <568BD595.6070500@FreeBSD.org> References: <201601051413.u05EDiRX065867@mech-as222.men.bris.ac.uk> <568BD595.6070500@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On 1/5/16 9:39 AM, Matthew Seaman wrote:
> In fact, even if your mail host uses just the domain as its hostname,
> I'd still have
>
> z.com. IN MX 0 z.com.
>
> Which looks entirely redundant, but the reason to have it is more social
> and reputational rather than technical.
Though if your DNS caching and negative caching times are "normal" I
believe that's also liable to save time if anyone ever sends you more
than one e-mail. In other words, a sending SMTP daemon will [or is
supposed to-YMMV for various spam generating engines] check for an MX
record before it falls back to using the A record directly, and an MX
record is liable to be cached near the sender for longer than the
information that there is no MX record.
Actually, under many circumstances, time will also be saved on the first
e-mail, as the initial query for MX records will frequently trigger a
reply with the appropriate A records included in the additional records
of the response, so the sending daemon won't have to make further
queries for the appropriate A record(s).
Eventually those milliseconds add up. :-)
In other words, unless there is good reason to not have an MX record,
I'd suggest always having an MX record for any name at which you wish to
regularly receive e-mail.
--Jon Radel
jon@radel.com
[-- Attachment #2 --]
0 *H
010
`He 0 *H
00 #SanzTgk!0
*H
0o10 USE10U
AddTrust AB1&0$UAddTrust External TTP Network1"0 UAddTrust External CA Root0
141222000000Z
200530104838Z010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CA0"0
*H
0
zSNpRV&IQZI`zQBy"aNv#
J n=ٺ.CRC|2PȦOZϓ%{0dV*$3DiFK3@@:*S= a<UNv%!)|qvO_T{5R"=,0-1YR73i-C֥wgQ'뼥8v8ߌIs:2:=F:WtaP@?⟢! 00U#0z4&&T$T0UakᢠOg£ 0U0U0 0U%0++0U
00U 0DU=0;09753http://crl.usertrust.com/AddTrustExternalCARoot.crl05+)0'0%+0http://ocsp.usertrust.com0
*H
*nU:Uka+ #fjow^a } [jr
AX&MX"cR6}Xޫ;cs{B#ʶM>K-ػBKiۦ74{:ǟO4ne6d)5ֱqC>2Svʆ4,Jؙ
␒ZBj#!eջ~ꌅ b:,Yř38zyJ&|00sT<}k
`i
0
*H
010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CA0
150330000000Z
180329235959Z010 UUS10U2215010 UVA10USpringfield10U 6917 Ridgeway Dr.10U
Jon T. Radel1200U)Issued through Jon T. Radel E-PKI Manager10UCorporate Secure Email10U Jon Radel10 *H
jon@radel.com0"0
*H
0
aЩ@@g3eGރ͛; d#>q7&Hf
:3vL"jV#Xݷ>U-H[$SUڻ{Ϝ,z¶IchO=rcyrn v.Vh7k;%ueYuӬnz6!| !Aȡ+,u+
CAպF-un#vjUJWnk%j]
2JPkl 00U#0akᢠOg£ 0UE|GDp/ʚB0U0U0 0U%0++0FU ?0=0;+10+0)+https://secure.comodo.net/CPS0]UV0T0RPNLhttp://crl.comodoca.com/COMODOSHA256ClientAuthenticationandSecureEmailCA.crl0+00X+0Lhttp://crt.comodoca.com/COMODOSHA256ClientAuthenticationandSecureEmailCA.crt0$+0http://ocsp.comodoca.com0U0
jon@radel.com0
*H
KS `?H_D`8G߿VbĘ<tB-Ӈї|{'Ũݹg0Gp$%F(;*MO*gt$@ t6,?0|#ăz,&! {j2i[%b7ߪP+9G㲍["y<?8rZ'[UR6%L̤
w"=:L~Ƨ^jf36 OP1.}(e1A0=0010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0
`He a0 *H
1 *H
0 *H
1
160105161238Z0/ *H
1" X%XDzyMGHq-λ;
H$VD[b}0l *H
1_0]0 `He*0 `He0
*H
0*H
0
*H
@0+0
*H
(0 +710010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0*H
1010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0
*H
C2@ty:Rݝ!p?L\f.R俴|U7o0l8'B;PU'm'BfK"А1m٧̸-xrxGnq{ߐTogʯt$'ފ}` V@FXR,.f䏰ql d&pWs"8(T{[H^w:d/;Hp?ﺠ-~l
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?568BEB76.9040403>
