Hoehrmann derhoe...@gmx.net wrote:
* Yakov Shafranovich wrote:
[...]
I am interested in this situation:
- Someone wants to publish database contents or schema
- Use DB-specific dumping tool to create .sql file
- Puts .sql file on web server
- Server associates .sql with proposed
On Tue, Feb 5, 2013 at 9:15 PM, Barry Leiba barryle...@computer.org wrote:
The question is what happens when the SQL file itself carries no
charset information, such as when using mysql-dump with the
--skip-set-charset option. According to MYSQL, UTF-8 would be used
in v5.1+ and ASCII in
Thanks for your comments. My understanding is that the SQL standards
as specified by ISO actually allow for variants and multiple vendor
implementations, all of which are not guaranteed to be compatible.
This is why the ISO standard specified conformance standards and
several levels of
were to use HTTP with this media type, then the
charset parameter would be used instead.
Yakov
On Wed, Jan 23, 2013 at 11:37 PM, Yakov Shafranovich i...@shaftek.org wrote:
Regarding the charset issue, you are correct in that when
communicating between SQL clients and SQL servers, the encoding
FYI. Some of the comments submitted are rather dangerous.
Yakov
Original Message
Subject: 0. General - UPDATE on FCC soliciting comments on mobile spam
Date: Mon, 03 May 2004 12:44:30 -0400
From: Yakov Shafranovich [EMAIL PROTECTED]
Organization: SolidMatrix Technologies, Inc
. If you
download the file in the message
(http://forum.icann.org/lists/stld-rfp-general/bin4.bin), and rename
it to .pdf (under Windows), it opens just fine.
I attached a copy of it to this message.
Yakov
--
Yakov Shafranovich / asrg at shaftek.org
SolidMatrix Technologies, Inc. / research
Vernon Schryver wrote:
If you believe that reputation or trust systems might help the
spam problem, then the only room for improvement is in the trust query
protocol. DNS is a screw driver being used as a hammer in DNS blacklists.
However, this is merely a matter of optimization or elegance.
I
Robert G. Brown wrote:
Right now enabling SPs are insulated from any kind of RFC-based
responses or complaints about spam because MUA's and MTA's have no
predefined protocol for generating such a response in a constructive
way. Most complaints/bounces that are automatically generated by
antivirus
Robert G. Brown wrote:
On Wed, 17 Mar 2004, Dean Anderson wrote:
On Wed, 17 Mar 2004, Robert G. Brown wrote:
...
b) Return the complaint as mail to postmaster of the originating
network with a special error code that would allow it to be counted and
digested easily. One doesn't want to create
william(at)elan.net wrote:
On Thu, 18 Mar 2004, Yakov Shafranovich wrote:
Paul Vixie wrote:
[EMAIL PROTECTED] (Vernon Schryver) writes:
... but I don't see any direct connection between [DNSSEC] and a
replacement for DNS blacklists.
i know. but you asked about trust query protocols
Ed Gerck wrote:
In a separate thread, under Yakov's suggestion, the solution part of
this discussion is now probably moving on to the closed ASRG list
(with open archive) as posted in
http://article.gmane.org/gmane.ietf.asrg.smtpverify/300
I'd like to now address the other part of Yakov's
Robert G. Brown wrote:
On Sun, 14 Mar 2004, Yakov Shafranovich wrote:
...
This is one of the many examples of things that the IETF can do that do
not solve the overall problem, but are very well within the IETF's
charter to make standards and can help with some aspects of the spam
problem
Dean Anderson wrote:
Given that, should the IETF pursue development of standards to make
abuse reporting easier to facilitate the work of those ISPs that
actually do handle abuse reports properly?
I'm not against a protocol to help share abuse reports. However, I haven't
seen this as much of
Vernon Schryver wrote:
From: Dr. Jeffrey Race [EMAIL PROTECTED]
...
The only solution is one which removes from connectivity those
who dump their trash on the commons. This is easy to do.
That is true in theory. In practice it has been difficult. I'm not
referring to the lies and whines of
Iljitsch van Beijnum wrote:
On 14-mrt-04, at 12:49, Dr. Jeffrey Race wrote:
...
The only solution is one which removes from connectivity those
who dump their trash on the commons. This is easy to do.
I don't think there are any easy answers here. If there were, they would
have long since be
Ed Gerck wrote:
Yakov Shafranovich wrote:
This discussion got me thinking about the need to state clearly that the
IETF's goal is not to solve the spam problem.
Inadequate design cannot be corrected?
The *possibility* of spam is due to an Internet design based on an
honor system for the end
Einar Stefferud wrote:
NSF dropped the AUP in 1994 as access was opened up to all who could afford it
and the trustworthiness of the internet has gone downhill ever since because
there is no longer any obvious incentive to inhibit bad behavior.
Reasonable trustworthiness is no longer a
Vernon Schryver wrote:
From: Yakov Shafranovich [EMAIL PROTECTED]
...
How many ISPs actually
willing to do that (although ComCast begun shutting down accounts of
hijacked machines)? What monetary incentive would the ISPs have to do
that? And even if the IETF publishes the BCP, there is no way
/). If you or anyone
else wants to join that list, let me know off-list (its a closed list
with about 30 members, separate from the main ASRG list).
I will get back to you once we digested your paper.
Yakov
Ed Gerck wrote:
Yakov Shafranovich wrote:
Go ahead - I am looking for any kind of solutions
I posted my original message to the IETF list for a reason instead of
replying to Paul and Vernon privately. My question is really directed to
all of you:
This is the IETF - an organization that sets some of the standards for
the Internet. What should the IETF be doing and NOT doing be in the
Vernon Schryver wrote:
From: Yakov Shafranovich [EMAIL PROTECTED]
Since the IETF is a standards organization, can both you and vsj tell us
in your opinion, if there is anything the IETF should or should not be
doing in the spam arena (changing existing standards, making new
standards, etc
Paul Vixie wrote:
nathaniel, john, i have a lot of respect for you but from reading this thread
it's clear that you have only been studying this issue for a couple of years.
please give it a decade, and read what's been written on the topic of digital
rights, before you go head to head with vjs
Message Verification - verification of both the message headers and
content (e.g. DK, Lumos, TEOS, etc.)
More information can be found on our webpage at:
http://asrg.sp.am. Feedback is welcome on our mailing list,
[EMAIL PROTECTED] or to the chairs directly.
Sincerely,
Yakov Shafranovich
Co-Chair
://www.infoworld.com/article/04/01/08/HNverisigncom_1.html
---
Yakov Shafranovich / asrg at shaftek.org
SolidMatrix Technologies, Inc. / research at solidmatrix.com
I ate your Web page. / Forgive me. It was juicy / And tart on my
tongue. (MIT's 404 Message)
---
.ietf.org/mailman/listinfo/asrg
Sincerely,
Yakov Shafranovich
Co-Chair, ASRG
Original Message
Subject: Wasted time?
Date: Sat, 20 Dec 2003 12:40:14 -0500
From: Hector Santos [EMAIL PROTECTED]
Organization: Santronics Software, Inc
To: Anti-Spam [EMAIL PROTECTED], Yakov
against the plan.
--
___
Asrg mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/asrg
---
Yakov Shafranovich / PGP Key: 0x10D051E6 / www.shaftek.org
SolidMatrix Technologies, Inc. / www.solidmatrix.com
Fight spam, but keep
: Yakov Shafranovich [EMAIL PROTECTED]
Organization: SolidMatrix Technologies, Inc.
To: ASRG list [EMAIL PROTECTED]
Below is the relevant list message from the NANOG mailing list:
Date: Fri, 3 Oct 2003 17:50:02 -0400
From: Matt Larson [address]
To: [EMAIL PROTECTED]
Subject: Removal of wildcard
Forwarded from the ASRG list:
Original Message
Subject: 0. General - ICANN asks Verisign to shut down SiteFinder in 48
hours
Date: Fri, 03 Oct 2003 11:31:58 -0400
From: Yakov Shafranovich [EMAIL PROTECTED]
Organization: SolidMatrix Technologies, Inc.
To: ASRG list [EMAIL
Hello,
I posted a message a while back about using or writing specialized tools
for IETF/IRTF WGs/RGs. Unfortunatly it got lost in the Verisign
discussion. I wanted to repost my original message to see if anyone has
any comments on this topic. My original message appears below.
Yakov
Mea culpa, sorry.
[EMAIL PROTECTED] wrote:
On Tue, 16 Sep 2003 01:27:09 EDT, Yakov Shafranovich said:
The SMTP server is fake, take a look at this transaction:
Actually, that was my point.
Forwarding from the ASRG list, more anti-spam tools being broken by
Verisign.
Original Message
Subject: [Asrg] 7. Best Practices - Service Providers MTA Authors
(was: Fwd: Verisign's New Change and Outdate RBL's)
Date: Tue, 16 Sep 2003 11:43:03 +0200
From: Brad Knowles [EMAIL
James M Galvin wrote:
On Tue, 16 Sep 2003, Keith Moore wrote:
verisign is masking the difference between a valid domain and
NXDOMAIN for all protocols, all users, and all software.
If you read the Verisign documentation (which is quite excellent by the
way) on what they did and what they
Just to follow up on this - I just spoke to an engineer at Verisign and
he informed me that the SMTP daemon is being replaced in a few hours
with an RFC-compliant one. As for not giving a warning - this came from
a higher policy level at Verisign and he is just an engineer.
Yakov
Yakov
Hi,
I co-chair the ASRG at the IRTF and we have been looking around for some
software to help us manage our group's website. Due to the large size of
our RG and many proposals being submitted to it, we have been looking at
a document repository primarily, with some additional tools that might
I am forwarding this message from the ASRG list. If you haven't heard it
yet, Verisign has activated their typos DNS service for .COM and .NET.
Original Message
Subject: [Asrg] Verisign: All Your Misspelling Are Belong To Us
Date: Tue, 16 Sep 2003 03:10:52 +0200
From: Brad
The SMTP server is fake, take a look at this transaction:
snip---
open 64.94.110.11 25
220 snubby1-wceast Snubby Mail Rejector Daemon v1.3 ready
blahblahbla
250 OK
blahblahbla
250 OK
blahblabhjla
550 User domain does not exist.
blahblbjhbj
250 OK
blajbjbjb
221 snubby1-wceast Snubby Mail
36 matches
Mail list logo
