Biggest Fake Conference in Computer Science

We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.

We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware

Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 

We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of

Fwd: New Version Notification for draft-bosch-sieve-duplicate-02.txt

Hi,

I made a new version of the "duplicate" draft. It should address the 
comments by Ned, Kristin and Alexey. I added the example I gave to Alexey.

This resulted in quite a bit of restructuring in the description of the 
new test command, so it is best to review at least that section entirely.

There is one thing I thought of and haven't addressed so far. My current 
implementation makes a new entry in the duplicate tracking list 
irrespective of whether one exists already, overwriting the old one and 
thereby resetting the expiry time to whatever is configured using 
":seconds". This will make example 3 in the draft yield unexpected 
results; if duplicates arrive within the expiry time, the total expiry 
time is in effect extended. The semantic difference here is that the 
expiry time is either measured relative to the initial message or 
relative to the last duplicate. This means that the 30 minutes in the 
example can stretch indefinitely if duplicates keep arriving before the 
expiry deadline. So, for the scenario of example 3, such behavior is 
quite obviously wrong. However, would there be an application for having 
the expiry time be relative to the last message received with the 
specified ID rather than the initial one? How would we accommodate for that?

Regards,

Stephan.

(Continue reading)

Fwd: New Version Notification for draft-bosch-sieve-duplicate-01.txt

Hi,

I made a new version of the "duplicate" draft. It should address the 
comments by Ned and Alexey.

Regards,

Stephan.

From: Hi, I made a new version of the "duplicate" draft. It should address the comments by Ned and Alexey. Regards, Stephan. <internet-drafts <at> ietf.org>
Subject: New Version Notification for draft-bosch-sieve-duplicate-01.txt
Date: 2013-02-10 00:04:20 GMT

A new version of I-D, draft-bosch-sieve-duplicate-01.txt
has been successfully submitted by Stephan Bosch and posted to the

Duplicate test

Hi,

A while back I built a non-standard Sieve extension for detecting 
duplicate message deliveries, e.g. as seen when people cross-post over 
multiple mailing lists. This functionality is very similar to what could 
be achieved with Procmail using formail -D. Someone requested this at 
some point and in a moment of boredom I built the initial 
implementation. Last year I extended it a bit and I made it more 
generic. I never intended for this to be standardized, but - now that I 
look at it again - I think this may yet be of some interest to other 
Sieve implementers as well.

I make a habit of documenting my custom Sieve extensions in a familiar 
RFC-like manner:

http://hg.rename-it.nl/dovecot-2.1-pigeonhole/raw-file/tip/doc/rfc/spec-bosch-sieve-duplicate.txt

What do you think? Would you be interested in having functionality like 
this standardized? Should I submit this as a draft?

Regards,

Stephan.

_______________________________________________
sieve mailing list
sieve <at> ietf.org
https://www.ietf.org/mailman/listinfo/sieve

WG Action: Conclusion of Sieve Mail Filtering Language (sieve)

The Sieve Mail Filtering Language (sieve) in the Applications Area has concluded. The IESG contact person
is Pete Resnick.

The mailing list will remain active.
_______________________________________________
sieve mailing list
sieve <at> ietf.org
https://www.ietf.org/mailman/listinfo/sieve

Closing of the WG

Hi all,

All of the documents we are going to publish have been published. Thanks 
for all of the excellent work in this group. We'll leave the list open 
for individual submissions and other work, but the WG will be closed. 
Job well done.

pr

--

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

_______________________________________________
sieve mailing list
sieve <at> ietf.org
https://www.ietf.org/mailman/listinfo/sieve

Script Runtime errors via X-Headers

Hi,

recently I stumbled upon a server, which returns run time errors of a 
sieve script as an X-Header. I did not find any documentation regarding 
this behavior, so I think it non standard. Never the less it's quite 
handy. Especially if you move, rename or misspell an imap folder.

Such an error X-Header looks like this:
X-Nemesis-Sieve: missing mailbox "\example"

Is there a chance to standardize this within the Sieve RFCs? It makes 
debugging script for inexperienced users with no access to the server 
logs way easier.

Especially since Paragraph "2.10.6. Errors" of "rfc5228" requires 
implementation to represent script errors to the user but does not offer 
any suggestions how to do that.

Thus I would suggest adding the following to paragraph 2.10.6 :

    When an error happens, implementations MUST notify the user that an
    error occurred and which actions (if any) were taken, and do an
    implicit keep.

+  This can be achieved by adding an "X-Sieve-Error" header containing
+  the runtime error message to the mail.

What are your thought on that?

Regards

I-D Action: draft-ietf-sieve-imap-sieve-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title           : Support for Internet Message Access Protocol (IMAP) Events in Sieve
	Author(s)       : Barry Leiba
	Filename        : draft-ietf-sieve-imap-sieve-09.txt
	Pages           : 23
	Date            : 2012-09-14

Abstract:
   Sieve defines an email filtering language that can, in principle,
   plug into any point in the processing of an email message.  As
   defined in the base specification, it plugs into mail delivery.  This
   document defines how Sieve can plug into points in the IMAP protocol
   where messages are created or changed, adding the option of user-
   defined or installation-defined filtering (or, with Sieve extensions,
   features such as notifications).  Because this requires future Sieve
   extensions to specify their interactions with this one, this document
   updates the base Sieve specification, RFC 5228.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sieve-imap-sieve-09

I-D Action: draft-ietf-sieve-imap-sieve-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title           : Support for Internet Message Access Protocol (IMAP) Events in Sieve
	Author(s)       : Barry Leiba
	Filename        : draft-ietf-sieve-imap-sieve-08.txt
	Pages           : 23
	Date            : 2012-09-10

Abstract:
   Sieve defines an email filtering language that can, in principle,
   plug into any point in the processing of an email message.  As
   defined in the base specification, it plugs into mail delivery.  This
   document defines how Sieve can plug into points in the IMAP protocol
   where messages are created or changed, adding the option of user-
   defined or installation-defined filtering (or, with Sieve extensions,
   features such as notifications).  Because this requires future Sieve
   extensions to specify their interactions with this one, this document
   updates the base Sieve specification, RFC 5228.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sieve-imap-sieve-08

Unicode regular expressions

http://www.unicode.org/reports/tr18/tr18-15.html

Unicode Technical Standard #18, Unicode Regular Expressions, just got
a new draft in July 2012; the previous draft was done in 2008. Who's
ready to update our own Regex draft?

*ducks*

Aaron
_______________________________________________
sieve mailing list
sieve <at> ietf.org
https://www.ietf.org/mailman/listinfo/sieve

I-D Action: draft-ietf-sieve-imap-sieve-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.

	Title           : Support for Internet Message Access Protocol (IMAP) Events in Sieve
	Author(s)       : Barry Leiba
	Filename        : draft-ietf-sieve-imap-sieve-05.txt
	Pages           : 23
	Date            : 2012-06-15

Abstract:
   Sieve defines an email filtering language that can, in principle,
   plug into any point in the processing of an email message.  As
   defined in the base specification, it plugs into mail delivery.  This
   document defines how Sieve can plug into points in the IMAP protocol
   where messages are created or changed, adding the option of user-
   defined or installation-defined filtering (or, with Sieve extensions,
   features such as notifications).

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-05

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-sieve-imap-sieve-05

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/