Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Jun 2010 18:36:24 +0200
From:      "Svein Skogen (Listmail Account)" <svein-listmail@stillbilde.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Midphase Hosting
Message-ID:  <4C111488.2060606@stillbilde.net>
In-Reply-To: <20100610121250.6ae70dfb@scorpio>
References:  <201006101147.40385.j.mckeown@ru.ac.za>	<201006101432.23605.j.mckeown@ru.ac.za>	<4C10E2F5.70806@infracaninophile.co.uk>	<201006101512.48246.j.mckeown@ru.ac.za> <20100610121250.6ae70dfb@scorpio>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFB042DD5A0693C2868108FA1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 10.06.2010 18:12, Jerry wrote:
> On Thu, 10 Jun 2010 15:12:48 +0200
> Jonathan McKeown <j.mckeown@ru.ac.za> articulated:
>=20
>> On Thursday 10 June 2010 15:04:53 Matthew Seaman wrote:
>>>
>>> The only other mechanism might be to tag each list e-mail with a
>>> unique value for each recipient in such a way that it is preserved
>>> in the message that mpcustomer.com's help system sends out.  That
>>> has severe problems of scale and load on the FreeBSD mail servers,
>>> but it might be possible.  There is a similar technique (whose name
>>> I have temporarily forgotten) that some mailing lists use where
>>> they tag the envelope sender address with the recipient name in
>>> order to identify addresses that are bouncing back the list e-mail.
>>
>> Isn't that called VERP (variable envelope return path)? I agree - the
>> load it would impose isn't worth it. I'm just shocked that midphase
>> care so little about their reputation or the impression this is
>> giving, on one of the more widely-archived mailing lists, of their
>> competence and diligence.
>=20
> I have employed VERP with mailing lists that I controlled. I never
> noticed any adverse effects. I know of several technical lists
> like Dovecot that employ it. Obviously, they find it useful.

Wouldn't adding an explicit route (to null) for the ip range employed by
mpcustomer.com for the poor FreeBSD server do the trick? It would build
up queue for a while, then the probe message wouldn't get there, then
the problem would simply vanish. ;)

//Svein

--=20
--------+-------------------+-------------------------------
  /"\   |Svein Skogen       | svein@d80.iso100.no
  \ /   |Solberg =D8stli 9    | PGP Key:  0xE5E76831
   X    |2020 Skedsmokorset | svein@jernhuset.no
  / \   |Norway             | PGP Key:  0xCE96CE13
        |                   | svein@stillbilde.net
 ascii  |                   | PGP Key:  0x58CD33B6
 ribbon |System Admin       | svein-listmail@stillbilde.net
Campaign|stillbilde.net     | PGP Key:  0x22D494A4
        +-------------------+-------------------------------
        |msn messenger:     | Mobile Phone: +47 907 03 575
        |svein@jernhuset.no | RIPE handle:    SS16503-RIPE
--------+-------------------+-------------------------------
         If you really are in a hurry, mail me at
               svein-mobile@stillbilde.net
 This mailbox goes directly to my cellphone and is checked
        even when I'm not in front of my computer.
------------------------------------------------------------
                     Picture Gallery:
          https://gallery.stillbilde.net/v/svein/
------------------------------------------------------------


--------------enigFB042DD5A0693C2868108FA1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)

iEYEARECAAYFAkwRFIwACgkQODUnwSLUlKT5kACfer/46UHmW+9CblFboMbXlwLs
8kAAn3iEsI6sqxiJ5K1wbzlxkLzneiaJ
=Wi6j
-----END PGP SIGNATURE-----

--------------enigFB042DD5A0693C2868108FA1--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C111488.2060606>