Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: AOL scomp

  • From: Suresh Ramasubramanian
  • Date: Tue Mar 01 23:57:01 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=AQzl9BLrmkR/b7OF2QFoxVsHRdZk3iVeA+DWKehXhGwK7YHGa/UwkDujyKDIdvHPcCoqbLVPOqa4LV2dNYQhqpMB7LioybvG1VhjUopvx4nmAIhLBmEKOu8HBkyIf9685ugAMjCCDdIfIjLkWyLbnJDTxWG38foB5w/1+gS7L74=

On Tue, 01 Mar 2005 09:28:31 -0500, Vinny Abello <vinny@tellurian.com> wrote:
> I can attest that we do not see the same here as you are seeing (1 in 100).
> I'd agree more with the 1/3 being stupid AOL users reporting regular
> messages that were either forwarded from their own account that we host to

Well - there's a way out, sort of.

1. Route .forwarded email out a separate IP (besides cutting down on
accepting and forwarding spam)

or

2. Find some way - like an X-Forwarded-For header, that AOL can tag on.

--srs

-- 
Suresh Ramasubramanian (ops.lists@gmail.com)




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.