• NAME
• VERSION
• SYNOPSIS
• OPTIONS
• EXAMPLE
• DOWNLOAD
• INSTALLATION
• COPYRIGHT
• LICENSE
• HISTORY
• v0.10 -> v0.11
• v0.9 -> v0.10
• v0.8 -> v0.9
• v0.7 -> v0.8
• v0.6 -> v0.7
• v0.5 -> v0.6
• v0.4 -> v0.5
• v0.3 -> v0.4
• v0.2 -> v0.3
• v0.1 -> v0.2
• KNOWN PROBLEMS

NAME

mailslash.pl -- slashdot.jp checker

VERSION

v0.11 - Beta release

SYNOPSIS

mailslash.pl {--direct|--local} [--echo] [--refresh] [--proxy=SERVER] [--uri=URI] [--file=FILE] [--db=DBFILE] [--subject=SUBJ] [--from=ADDRESS] [--to=ADDRESS] [--story]

OPTIONS

• --direct
  Read slashdot.rdf or comments.pl output directly from internet. You can point the URI by --uri option. This option overrides --local option.

• --local
  Read slashdot.rdf or comments.pl output from local files, not from internet. You can point the file name by --file option.Overridden by --direct option.

• --echo
  Output to local terminal and exit. No mail will be sent. This is used for debugging purpose.

• --refresh
  Just read new slashdot.rdf or comments.pl file, build DBFILE, and exit. Do neither check story for new article, nor send email.

• --proxy
  Set proxy server name as ``servername:portnumber'' style. See EXAMPLE for sample.

• --uri
  Set URI for slashdot.rdf or comments.pl file. Default is ``http://slashdot.jp/slashdot.rdf''. Use with --direct option.

• --file
  Set file name for local slashdot.rdf or comments.pl file. Default is ``./slashdot.rdf''. Use with --local option.

• --db
  Set file name for article database, DBFILE. Default is ``./slashdot.db''.

• --subject
  Subject: header of email. Default is null. If you use slashdot.rdf file (locally or directly), the default is taken from <title> entity.

• --from
  From: header of email. Some SMTP server rejects invalid From: header, so I recommend you set this option correctly (e.g., your real email address). Default is ``hoge@example.com''.

• --to
  To: header of email. Invalid To: address leads to undeliverable error (and unexpected trouble may happen), so take care! Default is ``puni@example.com'' (Yes, THIS IS INVALID, so you MUST assign correct email address).

• --story
  Add story (without comments) for every new articles and URIs.

EXAMPLE

If you want to check updates with file 'slashdot.rdf', you can type like following:

perl mailslash.pl --uri='http://slashdot.jp/slashdot.rdf' --direct --from='your-address@somewhere.example.com' --to='somewhere@somewhere.example.com' --db=slashdot.db

You can put any file name for --db option, but if you want to check continuously, you have to put the same file name as you put before. Note that above is the most basic options. If you have to access internet via proxy, type:

perl mailslash.pl --proxy='proxy.example.com:80' --uri='http://slashdot.jp/slashdot.rdf' --direct --from='your-address@somewhere.example.com' --to='somewhere@somewhere.example.com' --db=slashdot.db

Yes, you have to change the server name, other than 'proxy.example.com'. And if you also want the story inserted, type:

perl mailslash.pl --proxy='proxy.example.com:80' --uri='http://slashdot.jp/slashdot.rdf' --direct --from='your-address@somewhere.example.com' --to='somewhere@somewhere.example.com' --db=slashdot.db --story

If you want to check more frequently than every 30 minutes, you have to download comments.pl:

perl mailslash.pl --proxy='proxy.example.com:80' --uri='http://slashdot.jp/comments.pl' --direct --from='your-address@somewhere.example.com' --to='somewhere@somewhere.example.com' --db=slashdot.db --story

If you just want output to your terminal, add --echo option:

perl mailslash.pl --proxy='proxy.example.com:80' --uri='http://slashdot.jp/comments.pl' --direct --db=slashdot.db --story --echo

DOWNLOAD

You can download tarball from SourceForge website: http://sourceforge.net/projects/mailslash/

INSTALLATION

When you decompress the tarball, you'll have files named ``mailslash.pl'' and ``mailslash.html''. Put mailslash.pl at any directory you wish. You have to install HTTP::Lite, Mail::Sendmail and Unicode::Japanese before using mailslash.pl. These are perl modules, and you can download them from CPAN mirrors.

See EXAMPLE for command line options.

COPYRIGHT

Copyright k3c(k3c@users.sourceforge.net) 2001, All Rights Reserved.

LICENSE

This program is distributed under The Artistic Licence. for details about the license, see http://www.opensource.org/licenses/artistic-license.html.

HISTORY

Version-up history.

v0.10 -> v0.11

• Coding typo
  Removed multiple $subject definition.

• --story option
  If a line was substituted and the result was an empty line, reading story was over. This is not a correct processing (imagine, for example, ^<BR>^M$), so I modified the code. For now, only when the line is by default an empty line, reading story is over.

  Ignore case sensitivity for <BR> tag.

• POD
  OPTIONS section is introduced.

  --story option problem is deleted from KNOWN PROBLEM section. Bra bra! :-)

v0.9 -> v0.10

• First Beta release
  This is the first Beta release. if no bug is found or reported, I will release this code as a ``Product'', including other in-detail PODs. Note, at any time, comments are welcome :-)

• Slashcode 2.2 compatibility
  Made some modification on --story option function, for all TAB characters in article.pl has been replaced by 8 whitespaces.

v0.8 -> v0.9

• Slashcode 2.2 compatibility
  slashdot.jp was updated to Slashcode 2.2, so I had to change the ``template ID'' number. I don't understand why they had to change this number.

• POD
  LICENSE section is shortened, The Artistic License term was deleted. now this section is only a pointer to the license.

  INSTALLATION section is introduced.

v0.7 -> v0.8

• --story option bug fix
  Attempt to get new story has been sometimes failed(see KNOWN PROBLEM for detail), so I added some modifications on the source code.

• POD
  EXAMPLE section is introduced.

v0.6 -> v0.7

• comments.pl availability
  mailslash.pl is now able to handle comments.pl in place of slashdot.rdf. Invoking mailslash.pl with --uri http://slashdot.jp/comments.pl will process comments.pl as new artcle database.

• POD
  COPYRIGHT and LICENSE sections are introduced.

v0.5 -> v0.6

• POD
  Sections named: NAME, VERSION, SYNOPSIS and DOWNLOAD are introduced.

v0.4 -> v0.5

• --story option
  Match of </p> tag was changed to case-insensitive.

  Anchor tag is removed and stored as footnote at end of each story.

  Other tags are removed from the story.

v0.3 -> v0.4

• BUG FIX
  Story encoding was changed from 'utf-8 -> jis' to 'euc -> jis'.

v0.2 -> v0.3

• --story option
  Added new function to get story from new article.

• POD
  KNOWN PROBLEMS section is introduced.

v0.1 -> v0.2

• BUG FIX
  Changed default value of $subject to NULL. (If not NULL, Subject: header string is always set to $subject.)

• POD
  HISTORY section (this stuff :-) is introduced.

KNOWN PROBLEMS

Known but not solved problems.

• Multibyte Subject
  Header string must be MIME encoded, but not yet.