MX recs and backup mail reception strategies
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > WebserverTalk Community > Anonymous Servers > MX recs and backup mail reception strategies




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    MX recs and backup mail reception strategies  
TwistyCreek


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
01-25-06 07:49 AM

I'm looking to set up the MX record(s) on my domain so I can accept
incoming mail directly rather than using my registrar's redirection server
to send it to a gmail box and then pop3s'ing it down from there. The
problem is that this is probably a decrease in reliability (ie due to the
possibility power failures, ISP interuptions, etc). I've been reading a
bit on MX records and I'm wondering if it's as simple as it appears to use
a second machine at a second location to increase reliablity.

I'm considering asking a buddy that operates an FTP server 24/7 on a
different (DSL) ISP if he'd be willing to run some kind of Mercury setup
just to cover me in case my machine or my provider went down for a while.
I realize the SMTP protocol prescribes retrys etc before failing, but it
seems the MX priority idea is a pretty well defined strategy as well. Is
it just a matter of adding a second MX record with a priority value higher
than the one in the first MX rec? Why do you always see values like 10 and
100, etc. Wouldn't it make more sense to number them 1, 2, 3... I mean
it's not like the values a carved in stone.. if you ever need to add one
"in the middle" you just renumber - no?

Also... just how Eelbashian an idea would it be to suggest remops could
back each other up? I guess there's a significant potential for a rouge
remop to do traffic analysis if they had access to your (encrypted)
incoming mail over a period where you were down - right? I am having
trouble seeing how the same concern would exist relative to a trusted
buddy who has nothing to do with the remailer network (but I'm open to
re-education on that one).

Suggestions?
TIA















[ Post a follow-up to this message ]



    Re: MX recs and backup mail reception strategies  
Anonymous


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
01-25-06 01:16 PM



On 25 Jan 2006 06:19:19 -0000, TwistyCreek <anon@comments.header> wrote:

>I'm looking to set up the MX record(s) on my domain so I can accept
>incoming mail directly rather than using my registrar's redirection server
>to send it to a gmail box and then pop3s'ing it down from there. The
>problem is that this is probably a decrease in reliability (ie due to the
>possibility power failures, ISP interuptions, etc). I've been reading a
>bit on MX records and I'm wondering if it's as simple as it appears to use
>a second machine at a second location to increase reliablity.

It's not especially difficult.

>I'm considering asking a buddy that operates an FTP server 24/7 on a
>different (DSL) ISP if he'd be willing to run some kind of Mercury setup
>just to cover me in case my machine or my provider went down for a while.

Ok, but consider that your alternate will need your private keys to
decrypt incoming messages (unless they are just going to store and
forward to you at some later date).  It would be a major upgrade to
the remailer s/w and protocol to encrypt using more than one public key,
although it's technically possible.

>I realize the SMTP protocol prescribes retrys etc before failing, but it
>seems the MX priority idea is a pretty well defined strategy as well. Is
>it just a matter of adding a second MX record with a priority value higher
>than the one in the first MX rec? Why do you always see values like 10 and
>100, etc. Wouldn't it make more sense to number them 1, 2, 3... I mean
>it's not like the values a carved in stone.. if you ever need to add one
>"in the middle" you just renumber - no?

DNS records are cached. It could take quite some time for the renumbering
to propagate across the Internet.  Better to leave some gaps and retain
your flexibility.

>Also... just how Eelbashian an idea would it be to suggest remops could
>back each other up? I guess there's a significant potential for a rouge
>remop to do traffic analysis if they had access to your (encrypted)
>incoming mail over a period where you were down - right?

Pairing with another remop who will at least store and forward your
e-mail is sensible.  It would be up to you to interview the prospective
remop and determine whether or not they are trustworthy.

>I am having
>trouble seeing how the same concern would exist relative to a trusted
>buddy who has nothing to do with the remailer network (but I'm open to
>re-education on that one).

On that note, you might want to visit the following web sites:
http://rollernet.us/index.php
http://www.everydns.net

Rollernet and everydns offer free secondary MX and secondary DNS services,
respectively.  I haven't used rollernet, but I can vouch for everydns.
I've used everydns for years and it has been flawless.  David Ulevitch
is an outstanding netizen.

>Suggestions?

I believe the two areas for improvement in the remailer network are
reliability and authentication.

If remops paired up as you suggest, it would improve reliability.
There would be a small sacrifice in security, but not much.  After
a little shake-out period, the trolls would end-up pairing with other
trolls and the serious remops would cover each other.  The trolls
would be shunned as they are now, except you could kill them in pairs.

Security wise, everyone should implement TLS and get your domain cert
signed by a certificate authority.  It's no longer necessary to pay
usury to the commercial CA's. CAcert.org is available for free.




-=-
This message was sent via two or more anonymous remailing services.









[ Post a follow-up to this message ]



    Re: MX recs and backup mail reception strategies  
Zax


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
01-25-06 01:16 PM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 25 Jan 2006 06:19:19 -0000, TwistyCreek wrote in
Message-Id: <DX8VYZE538742.0550810185@twistycreek.com>:

> I'm looking to set up the MX record(s) on my domain so I can accept
> incoming mail directly rather than using my registrar's redirection server
> to send it to a gmail box and then pop3s'ing it down from there. The
> problem is that this is probably a decrease in reliability (ie due to the
> possibility power failures, ISP interuptions, etc). I've been reading a
> bit on MX records and I'm wondering if it's as simple as it appears to use
> a second machine at a second location to increase reliablity.

That's probably the best approach, although all mail servers should
retry sending for a reasonable period of time if your mta is
unreachable.  You can run your own secondary MTA, ask a friend or use a
commercial service.  I used this one for a while and they seemed pretty
good for $18/year.  http://www.sitelutions.com/info/slbackupmx

If you go down this route, I would strongly suggest you also host your
own DNS service.  There's no substitute for taking control of your
entire environment and just using service providers for connectivity.

> I realize the SMTP protocol prescribes retrys etc before failing, but it
> seems the MX priority idea is a pretty well defined strategy as well. Is
> it just a matter of adding a second MX record with a priority value higher
> than the one in the first MX rec? Why do you always see values like 10 and
> 100, etc. Wouldn't it make more sense to number them 1, 2, 3... I mean
> it's not like the values a carved in stone.. if you ever need to add one
> "in the middle" you just renumber - no?

It's just normal convention to number in steps of 10.  There is no real
reason for it other than the flexibility to insert without renumbering.

> Also... just how Eelbashian an idea would it be to suggest remops could
> back each other up? I guess there's a significant potential for a rouge
> remop to do traffic analysis if they had access to your (encrypted)
> incoming mail over a period where you were down - right? I am having
> trouble seeing how the same concern would exist relative to a trusted
> buddy who has nothing to do with the remailer network (but I'm open to
> re-education on that one).

I don't see any harm in remops hosting backup services for other remops.
DNS would be a prime example and I'm happy to host a secondary DNS
should any remop want one.  For backup MTA's, I can't think of a reason
why this would be a security problem.  All traffic in transit is
potentially being captured and stored anyway, that's why it's encrypted.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

 iQEVAwUBQ9dtfGoLu9HNUqmMAQo0FAgAoM5zUrjt
blNKmgRyoy1PbiioXPAo46gg
AGTrO6RHq1JbD+F57vZAXHbLf1diTUy1/SSeKtUJtZs4Y5f2upV08cKl7m8AO1XK
 cPpSHJwiRf4LfBSRKZUIdRGqWQHXSsWgVLEdEJqu
qT+C5SQ2uTu7HLa60qaosfR3
 63hbt88VJDgq9+h9IaCx4IdRDhwDjIZt7iS3OC0F
lhT8YKXETb8DWahKI2jdex0o
 FJgRP738AQUJkKrXQgpn5XYO8mdnLguDD7pn77LX
RleRNjRMX+N5oMxgZGt/crq6
 S9ymKIIZsS1kM00c+RbKUEgaBqCZpZTc9EkHF3gW
UiJQND4wmBU+Zg==
=VTvg
-----END PGP SIGNATURE-----

--
pub  1024D/8ED57743 2003-07-08 Bananasplit Operator
Key fingerprint = 796F 67E0 E890 A0BB BDAE  EBB4 94A6 7A09 8ED5 7743
uid                            Admin <admin.bananasplit.info>






[ Post a follow-up to this message ]



    Re: MX recs and backup mail reception strategies  
TwistyCreek Admin


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
01-28-06 02:02 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25 Jan 2006 06:19:19 -0000, TwistyCreek <anon@comments.header> wrote:

>I'm looking to set up the MX record(s) on my domain so I can accept
>incoming mail directly rather than using my registrar's redirection server
>to send it to a gmail box and then pop3s'ing it down from there. The
>problem is that this is probably a decrease in reliability (ie due to the
>possibility power failures, ISP interuptions, etc). I've been reading a
>bit on MX records and I'm wondering if it's as simple as it appears to use
>a second machine at a second location to increase reliablity.
>
>I'm considering asking a buddy that operates an FTP server 24/7 on a
>different (DSL) ISP if he'd be willing to run some kind of Mercury setup
>just to cover me in case my machine or my provider went down for a while.
>I realize the SMTP protocol prescribes retrys etc before failing, but it
>seems the MX priority idea is a pretty well defined strategy as well. Is
>it just a matter of adding a second MX record with a priority value higher
>than the one in the first MX rec? Why do you always see values like 10 and
>100, etc. Wouldn't it make more sense to number them 1, 2, 3... I mean
>it's not like the values a carved in stone.. if you ever need to add one
>"in the middle" you just renumber - no?
>
>Also... just how Eelbashian an idea would it be to suggest remops could
>back each other up? I guess there's a significant potential for a rouge
>remop to do traffic analysis if they had access to your (encrypted)
>incoming mail over a period where you were down - right? I am having
>trouble seeing how the same concern would exist relative to a trusted
>buddy who has nothing to do with the remailer network (but I'm open to
>re-education on that one).
>
>Suggestions?
>TIA
>

I am using a backup from MX1.DNSMADEEASY.com. It seems to work fine. It is
pretty cheap.

Look at:

http://www.dnsstuff.com/tools/looku...ek.com&type=ALL

Sometimes, when a lot of incoming messages hit Mercury, it is tied up and
unavailable. DNSMADEASY kicks in, picks up the excess and forwards them
back when the Mercury is ready to receive again.

I don't accept unencrypted messages so I don't see any security risk of a
temporary storage.

Warm Regards All,
TwistyCreek Admin

-----BEGIN PGP SIGNATURE-----

iQA/ AwUBQ9fN0P9qPDhkRaWyEQKN7ACgg1tqdacMwSNS
cKpNuUsEqRrBxwAAoLlb
tAassnhskHRe8M31S5bTYmr6
=cyea
-----END PGP SIGNATURE-----






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 10:01 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register