trestlemail-cvs Mailing List for Trestlemail
Status: Alpha
Brought to you by:
bronson
Menu
▾
▴
trestlemail-cvs — CVS commits
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(25) |
Nov
|
Dec
(12) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(27) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Scott B. <br...@us...> - 2001-01-06 04:15:45
|
Update of /cvsroot/trestlemail/trestlemail
In directory usw-pr-cvs1:/tmp/cvs-serv27981
Modified Files:
TODO
Log Message:
Update todo
Index: TODO
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/TODO,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -r1.28 -r1.29
*** TODO 2001/01/06 04:14:32 1.28
--- TODO 2001/01/06 04:15:50 1.29
***************
*** 38,43 ****
message to screw up the argument list.
- - 0.9 Serious organization
-
- 0.9 idcache? Remove duplicates using message ID?
If so, then I can get rid of formail in the FAQ
--- 38,41 ----
***************
*** 68,71 ****
--- 66,78 ----
- 0.9 stream EVERY message, including lists and errors.
+
+ - 0.9 Serious organization
+ parse_rc_file()
+ check_rc_parse()
+ read_command_line_args()
+ check_command_line_args()
+ read_message_headers()
+
+ ----
- 1.0+: re-write in C
|
|
From: Scott B. <br...@us...> - 2001-01-06 04:14:26
|
Update of /cvsroot/trestlemail/trestlemail/doc
In directory usw-pr-cvs1:/tmp/cvs-serv27809/doc
Modified Files:
trestlemail-command.html
Log Message:
Removed Craig Steadman's realname changes. :(
They're a great idea, and a good feature, but the way mail works,
I just can't make it reliable.
Index: trestlemail-command.html
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/doc/trestlemail-command.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** trestlemail-command.html 2000/12/19 02:31:41 1.6
--- trestlemail-command.html 2001/01/06 04:14:32 1.7
***************
*** 104,117 ****
look like this: "[soda] Re: [soda] re: [soda] RE [soda] how's it
going?"</dd>
- <dt><strong>@-r</strong><em><strong></strong></em></dt>
- <dd>This enables real-name delivery, where the message is delivered based
- on the real name portion of the address (<code>"Real Name" re...@do...
- </code>or<code> </code><code>Real Name <re...@ad...></code>). Note
- that this is a <em>terrible</em> thing to do! You will never have
- reliable mail delivery if you use this option.
- <p>If your ISP charges you a huge amount of money for POP mailboxes and
- you don't mind the constant maintenance that this option requires, then
- go ahead. But don't say I didn't warn you.</p>
- </dd>
</dl>
--- 104,107 ----
|
|
From: Scott B. <br...@us...> - 2001-01-06 04:14:26
|
Update of /cvsroot/trestlemail/trestlemail/bin
In directory usw-pr-cvs1:/tmp/cvs-serv27809/bin
Modified Files:
trestlemail
Log Message:
Removed Craig Steadman's realname changes. :(
They're a great idea, and a good feature, but the way mail works,
I just can't make it reliable.
Index: trestlemail
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/bin/trestlemail,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -r1.24 -r1.25
*** trestlemail 2001/01/04 23:19:07 1.24
--- trestlemail 2001/01/06 04:14:32 1.25
***************
*** 5,12 ****
# 26 Oct 1998
- # "Realname" message delivery feature
- # by Craig Steadman (spi...@ho...)
- # 14 May 2000
-
# This entire file, and every file in the Trestlemail distribution,
# is covered by the GNU GPL. See the file COPYING for more information.
--- 5,8 ----
***************
*** 45,51 ****
# if "nn" don't run executables either.
- my $opt_d = ""; # debug and diagnostic messages -- the more ds, the
- # more messages you get.
-
my $opt_c = ""; # if "c", print shallow processed rc file and exit
# if "cc", print deep processesd rc file and exit
--- 41,44 ----
***************
*** 54,78 ****
# (i.e. addrs are coming from a plugin, not fetchmail)
- my $opt_r = ""; # if "r?" enable real-name message routing, ? is defined below
- # ? selects which part of the email you want to parse for a real-name
- # which is used as the local username for message delivery
- #
- # v - parse To: & Cc: headers
- # s - parse Subject: header
- # x - parse email suffix eg us...@yu...main(realname)
- # f - parse >From: headers in message body, includes suffix scan as well
- # h - scan all headers for a valid realname ... last resort !!
- # b - scan message body for a valid realname ... last resort !!
- # z - send a copy of all messages to the postmaster
- #
- # any combinations of these can be made to fine tune your setup
- # eg "vvf" works ok for hotmail
- # eg "vvfhb" if your subscribed to mailing lists
- #
- # Cc-ing to mutliple realname recipients is only supported on
- # To & Cc headers, otherwise only the first realname found
- # receives the message.
-
-
my $sendmailcmd = ""; # Tells how to invoke sendmail. It will be filled
# in later with one of $sendmail or $dontsendmail.
--- 47,50 ----
***************
*** 85,98 ****
# try to ensure no lost mail). However, it is not a good idea
# to dump a 1 Mb message into the Fetchmail log. Therefore, we don't dump
! # more than $max_error_lines of message body into the log. The entire
! # message still gets sent to the administrator's address, and we try to
! # ensure the message remains in the mail spool, so there should never be
! # any need to retrieve the message out of the error log.
! my $max_error_lines = 25;
!
! # realname stuff
! my $recipient = "";
! my $seperator = "";
! my $lastheader = "";
# OK let's go...
--- 57,67 ----
# try to ensure no lost mail). However, it is not a good idea
# to dump a 1 Mb message into the Fetchmail log. Therefore, we don't dump
! # more than $max_error_lines of message body into the log (we always dump
! # all the header).
! # The entire message still gets sent to the administrator's address, and we
! # try to ensure the message remains in the mail spool, so there should never
! # be any need to retrieve the message out of the error log.
! my $max_error_lines = 40;
!
# OK let's go...
***************
*** 107,111 ****
my @to = (); # list of addrs to send this message to
- my @rto = (); # list of "realname" addrs to send message to
my @fr = (); # who this message is from
my @rc = (); # list of rc files to parse
--- 76,79 ----
***************
*** 151,158 ****
/^\@-(n.*)$/ && do { $opt_n .= $1; next; };
- /^\@-(d.*)$/ && do { $opt_d .= $1; next; };
/^\@-(c.*)$/ && do { $opt_c .= $1; next; };
/^\@-(e.*)$/ && do { $opt_e .= $1; next; };
- /^\@-(r.*)$/ && do { $opt_r .= $1; next; };
/^\@-v$/ && do { print "Trestlemail version $version\n"; exit 0; };
--- 119,124 ----
***************
*** 185,189 ****
#
! # Pre-flight: make sure that everything appears to be in order
#
--- 151,155 ----
#
! # Pre-flight: make sure that command-line appears to be in order
#
***************
*** 229,233 ****
# Collect backslash line continuations into a single line
! # Mash all whitespace around the continuation into a single space
while( s/\s*\\\s*\n// ) {
my $str = <RC>;
--- 195,199 ----
# Collect backslash line continuations into a single line
! # Mash all whitespace after the continuation into a single space
while( s/\s*\\\s*\n// ) {
my $str = <RC>;
***************
*** 301,308 ****
exit 1;
}
$domain || matrice( "You forgot to set the domain parameter in the rc file!" );
! # Slurp headers into @msgheader. Try to leave msgbody on stdin
# so we can stream it, but we'll call slurp_message() to read it
# entirely into core if we have to...
--- 267,275 ----
exit 1;
}
+
$domain || matrice( "You forgot to set the domain parameter in the rc file!" );
! # Slurp headers into @msgheaders. Try to leave msgbody on stdin
# so we can stream it, but we'll call slurp_message() to read it
# entirely into core if we have to...
***************
*** 315,499 ****
unless( $opt_c ) {
while( <STDIN> ) {
! if( $_ eq "\n" ) {
! # Plain newline marks the separation between header and body
! $seperator = "ok";
! if ( $opt_d ) { print "<< Found new-line seperator>>\n" }
! last;
! }
-
- # Display header info for debugging purposes
- if ( $opt_d ) { print "Header----------> $_" }
-
- # If RealName message routing is enabled then extract names
- #####################################################################
- unless ( !$opt_r ) {
-
- # Extract Realname from suffix (comment) of addr in To: & Cc: header
- # <should grab all recipients not juz first>
- #
- if ( $opt_r =~ m/x/ && !scalar(@rto)) {
- if( /^to:.*\((\w+)/i ) {
- lookup_user_name ( $1 ) && push @rto, $1;
- $lastheader = "to";
- if ( $opt_d ) { print "RealName---> $1\n" }
- }
- if( /^cc:.*\((\w+)/i ) {
- lookup_user_name ( $1 ) && push @rto, $1;
- $lastheader = "cc";
- if ( $opt_d ) { print "RealName---> $1\n" }
- }
- }
-
- # Extract Realname from To: & Cc: headers to @rto array
- # Realname must have one whitespace character around it and follow immediately after To: or Cc:
- # <should grab all recipients not juz first>
- #
- if ( $opt_r =~ m/v/i && !scalar(@rto)) {
- if( /^to:\s\W??(\w+)\s/i ) {
- lookup_user_name ( $1 ) && push @rto, $1;
- $lastheader = "to";
- if ( $opt_d ) { print "RealName---> $1\n" }
- }
- if( /^cc:\s\W??(\w+)\s/i ) {
- lookup_user_name ( $1 ) && push @rto, $1;
- $lastheader = "cc";
- if ( $opt_d ) { print "RealName---> $1\n" }
-
- }
-
- }
-
- # Extract Realname from Subject: header to @rto array
- #<should grab all recipients not juz first>
- #
- if ( $opt_r =~ m/s/ && !scalar(@rto)) {
- if( /^subject:\s\W??(\w+)/i ) {
- lookup_user_name ( $1 ) && push @rto, $1;
- if ( $opt_d ) { print "RealName---> $1\n" }
- }
- }
-
-
- # Scan entire length of header for a valid recipient and save the name
- #
- if ( $opt_r =~ m/h/ && !scalar(@rto) ) {
- while (/\s*(\w+)/ig ) {
- if ( lookup_user_name ( $1 )) {
- $recipient = $1;
- if ( $opt_d ) { print "RealName---> $1\n" };
- last;
- }
-
- }
- }
-
-
- } # end unless
-
if( /^\s/ ) {
# Any line in the header beginning with whitespace is a
# continuation of the previous header.
$msgheaders[$#msgheaders] .= $_;
! next;
! }
! push @msgheaders, $_;
! }
! }
!
! if ( $opt_d && !$seperator ) { print "<< No new-line seperator>>\n" }
!
! # Read from STDIN to parse headers returned in message body for realnames
! # Note ONLY scan message body if a seperator was found
! #
! unless ( (!$opt_r =~ m/f/ && !scalar(@rto)) && $seperator ) {
!
! while ( <STDIN> ) {
! push @msgbody,$_;
!
! # Display msg body text for debugging
! if ( $opt_d ) { print "Body----------> $_" }
!
!
! # Extract Realname from first replied >From: header & comment suffix
! #
! if ( $opt_r =~ m/f/ && !scalar(@rto) ) {
! if( /^.*from:\s\W??(\w+)\s/i ) {
! lookup_user_name ( $1 ) && push @rto, $1;
! if ( $opt_d ) { print "RealName---> $1\n" }
! }
!
! if( /^.*from:.*\((\w+)/i ) {
! lookup_user_name ( $1 ) && push @rto, $1;
! if ( $opt_d ) { print "RealName---> $1\n" }
! }
! }
!
! # Scan text in msg body for a valid recipient and save the name
! #
! if ( $opt_r =~ m/b/ && !scalar(@rto) ) {
! while (/(\w+)/ig ) {
! if ( lookup_user_name ( $1 ) ) {
! $recipient = $1;
! if ( $opt_d ) { print "RealName---> $1\n" };
! last;
! }
!
! }
! }
! }
!
! }
!
!
!
! # Trap all mail that we cannot determine the recipient account and send to the postmaster
!
! unless ( !$opt_r ) {
!
! # Add temporary Submitted header so sendmail knows this messages was processed by trestlemail.
! # This will be stripped off by sendmail prior to delivery.
! #
! # push @msgheaders, "Parsed: Processed by Trestlemail\n";
!
! # Last resort scan may have found a name
! # if @rto is empty and h option enabled and $recipient exists then send message to $recipient
! # Send a warning to postmaster if all else fails
! #
! if ( !scalar(@rto) ) {
! if ( ($opt_r =~ m/h/i || $opt_r =~ m/b/) && $recipient ) {
! push @rto, $recipient;
! if ( $opt_d ) { print "RealNameLast---> $recipient\n" }
! }
! else {
! push @rto, "postmaster";
! push @msgheaders, "Warning: [>>>>>>>>>>>>>>> Warning No Valid Recipient Found <<<<<<<<<<<<<<<]\n";
! if ( $opt_d ) { print "GameOver---> postmaster\n" }
}
}
}
- # Force a copy of all mail to be sent to the postmaster
- if ( $opt_r =~ m/z/ ) { push @rto, "postmaster";if ( $opt_d ) { print "RealName---> postmaster\n" } }
-
- if ( $opt_d ) { print "\n--------------------------------------- PROCESSING COMPLETED ---------------------------------------\n\n" }
-
- # Look up the addresses. You can't have a user and a list with the
- # same name (the user gets priority).
-
my @userto = ();
my @failarray = ();
- # If realname routing enabled then discard actual usernames and use "realname" list
- #
- if ( $opt_r ) { @to = @rto }
-
for( @to ) {
my( $name ) = /^([^@]+)/;
unless( $name ) {
push @failarray, $name;
- print "###!!! FAIL --> $name";
next;
}
--- 282,307 ----
unless( $opt_c ) {
while( <STDIN> ) {
! last if $_ eq "\n"; # empty line markes the end of the headers
if( /^\s/ ) {
# Any line in the header beginning with whitespace is a
# continuation of the previous header.
$msgheaders[$#msgheaders] .= $_;
! } else {
! push @msgheaders, $_;
}
}
}
+ # Look up the addresses
my @userto = ();
my @failarray = ();
for( @to ) {
my( $name ) = /^([^@]+)/;
unless( $name ) {
push @failarray, $name;
next;
}
|
|
From: Scott B. <br...@us...> - 2001-01-06 04:14:26
|
Update of /cvsroot/trestlemail/trestlemail
In directory usw-pr-cvs1:/tmp/cvs-serv27809
Modified Files:
CHANGES TODO make-dist
Log Message:
Removed Craig Steadman's realname changes. :(
They're a great idea, and a good feature, but the way mail works,
I just can't make it reliable.
Index: CHANGES
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/CHANGES,v
retrieving revision 1.25
retrieving revision 1.26
diff -C2 -r1.25 -r1.26
*** CHANGES 2000/12/19 02:31:41 1.25
--- CHANGES 2001/01/06 04:14:31 1.26
***************
*** 2,17 ****
Trestlemail 0.83
0.83:
! - Added Craig Steadman's realname changes, still some clean up needed
! - Removed trestlemailsettings file. The installer makes it obsolete
- Removed the trestlemail error log. It uses the fetchmail error log instead.
- Added the @-a administrator's address command-line switch.
- Removed any mention of the catastrophe address. It's now "administrator's address".
- They're not "externals" or "executables" -- they're plugins. Updated code and docs.
! - list-send now adds a Received header
! - Installer now knows about DEFUNCT_FILEs (for trestlemailsettings)
- Installer now knows about FILE_PERMs to explicitly set file permissions.
! 0.822:
- Fixed a bug where a message arriving for a known user and an unknown
user would result in the message body to the known user being dropped.
--- 2,23 ----
Trestlemail 0.83
+ 0.85:
+ - Removed realname -- it would never be reliable.
+
0.83:
! - Added Craig Steadman's realname changes, still some clean up needed.
! - Removed trestlemailsettings file. The installer makes it obsolete.
- Removed the trestlemail error log. It uses the fetchmail error log instead.
- Added the @-a administrator's address command-line switch.
- Removed any mention of the catastrophe address. It's now "administrator's address".
- They're not "externals" or "executables" -- they're plugins. Updated code and docs.
! - list-send now adds a Received header.
! - Installer now knows about DEFUNCT_FILEs (for trestlemailsettings).
- Installer now knows about FILE_PERMs to explicitly set file permissions.
+
+ 0.823 (merged before 0.85):
+ - Fix Perl 5.004 (and no others?) complaint about re-matching-re.
! 0.822 (merged before 0.83):
- Fixed a bug where a message arriving for a known user and an unknown
user would result in the message body to the known user being dropped.
Index: TODO
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/TODO,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -r1.27 -r1.28
*** TODO 2001/01/04 21:59:50 1.27
--- TODO 2001/01/06 04:14:32 1.28
***************
*** 10,19 ****
Need to do archiving myself -- Geocrawler stinks.
- - 0.85 Mask the version number (Trestlemail mda VERS) in the regression tests
- just like we currently mask the date.
-
- 0.85 Add headers and footers to list mail.
! - 0.85 include-addrs-in-message: when sending to a mailing list,
- 0.85 Load balancing plugin
--- 10,17 ----
Need to do archiving myself -- Geocrawler stinks.
- 0.85 Add headers and footers to list mail.
! - 0.85 display-recipients: when sending to a mailing list,
! This basically emulates a reflector
- 0.85 Load balancing plugin
***************
*** 22,25 ****
--- 20,25 ----
the catastrophe address?"
+ - 0.85 bounce plugin
+
- 0.85 local-delivery plugin
Give the local-delivery plugin a command to execute if it could
***************
*** 28,39 ****
- 0.85 Get rid of obsolete documentation.
- - 0.85 Allow showing the addresses in the To: header in a mailing list message
-
- - 0.85 Get rid of the Trestlemail log file. Make the error
- messages end up in Fetchmail's log instead.
-
- 0.85 Consolidate documentation, make it easy to jump between,
a la postfix's docs.
- 0.9 Serious organization
--- 28,41 ----
- 0.85 Get rid of obsolete documentation.
- 0.85 Consolidate documentation, make it easy to jump between,
a la postfix's docs.
+ - 0.85 The @- style arguments allow potential security holes. This
+ needs to be eliminated. HOW? Is there any other way for Fetchmail
+ to pass args to Trestlemail?
+ Nah, no need. Just do this: tm -s subj -a addr -- ALL THE TO ADDRS
+ - Now, @badarg can fail hard again, since there's no way for the
+ message to screw up the argument list.
+
- 0.9 Serious organization
***************
*** 42,50 ****
Or, maybe I can integrate formail itself?
- - 0.9 The @- style arguments allow potential security holes. This
- needs to be eliminated. HOW? Is there any other way for Fetchmail
- to pass args to Trestlemail?
- Nah, no need. Just do this: tm -s subj -a addr -- ALL THE TO ADDRS
-
- 0.9 Make it so nobody can post to a list except for the named
addresses -- this is good for an announcements list, etc
--- 44,47 ----
***************
*** 69,77 ****
- 0.9 automate mailing list subscribing and unsubscribing
Maybe never -- prolly want to look into using majordomo instead.
-
- - 1.0
! - 1.0+ stream EVERY message, even lists and errors
! - ???: re-write in C
--- 66,72 ----
- 0.9 automate mailing list subscribing and unsubscribing
Maybe never -- prolly want to look into using majordomo instead.
! - 0.9 stream EVERY message, including lists and errors.
! - 1.0+: re-write in C
Index: make-dist
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/make-dist,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** make-dist 2000/06/26 17:10:53 1.4
--- make-dist 2001/01/06 04:14:32 1.5
***************
*** 27,30 ****
--- 27,31 ----
rm make-dist
+ # Should verify no .bak, .swp, or .cvsignore files
# Should verify all version numbers
|
Update of /cvsroot/trestlemail/trestlemail/test/running/conf In directory usw-pr-cvs1:/tmp/cvs-serv12020/test/running/conf Added Files: 01-RE_Empty.test 02-RE_NoEmpty.test 03-RE_EscapedSlash.test 04-RE_EscapedSlashSlash.test 05-RE_EscapedBkslash.test 06-RE_EscapedBkslashBkslash.test 07-RE_OnlySlash.test 08-RE_OnlySlashSlash.test 09-RE_SlashSlashSlash.test 10-RE_AnySlashSlash.test 11-RE_CharClassSlash.test 12-RE_EscapedOpenBracket.test 13-RE_EscapedCloseBracket.test 14-RE_CharClassOpenBracket.test 15-RE_CharClassCloseBracket.test 16-RE_CharClassBackslash.test 17-RE_NonRE.test 18-RE_DefaultRE.test 19-RE_BackBrack.test 20-RE_qmailFAQTest.test regexps1.rc regexps2.rc regexps3.rc Log Message: dev_0-823 merge |
|
From: Scott B. <br...@us...> - 2001-01-04 23:19:05
|
Update of /cvsroot/trestlemail/trestlemail/test/delivery In directory usw-pr-cvs1:/tmp/cvs-serv12020/test/delivery Modified Files: 01-KnownAndUnknown.test Log Message: dev_0-823 merge Index: 01-KnownAndUnknown.test =================================================================== RCS file: /cvsroot/trestlemail/trestlemail/test/delivery/01-KnownAndUnknown.test,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** 01-KnownAndUnknown.test 2000/10/25 01:00:39 1.2 --- 01-KnownAndUnknown.test 2001/01/04 23:19:07 1.3 *************** *** 14,18 **** @Rc testrc @To known-user unknown-user ! @Fr sc...@tr... < ../plain.msg --- 14,18 ---- @Rc testrc @To known-user unknown-user ! @Fr te...@tr... < ../plain.msg |
|
From: Scott B. <br...@us...> - 2001-01-04 23:19:05
|
Update of /cvsroot/trestlemail/trestlemail/test
In directory usw-pr-cvs1:/tmp/cvs-serv12020/test
Modified Files:
README TODO tmtest
Log Message:
dev_0-823 merge
Index: README
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/README,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -r1.3 -r1.4
*** README 2000/10/25 01:00:39 1.3
--- README 2001/01/04 23:19:07 1.4
***************
*** 39,42 ****
--- 39,43 ----
plugins: tests the Trestlemail plugins
running: tests the Fetchmail<->Trestlemail interaction, cmd-line args, etc.
+ running/conf: Tests various trestlemailrc parsing issues
Index: TODO
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/TODO,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -r1.3 -r1.4
*** TODO 2000/12/15 20:24:12 1.3
--- TODO 2001/01/04 23:19:07 1.4
***************
*** 4,10 ****
Print the number of successes/failures.
- Make it so it doesn't care what dir it was launched from.
- (right now, ../tmtest fails)
-
Install test harness so you can immediately test to make sure most everything's ok.
--- 4,7 ----
Index: tmtest
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/tmtest,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** tmtest 2000/10/25 01:00:39 1.2
--- tmtest 2001/01/04 23:19:07 1.3
***************
*** 24,28 ****
! my $binpath = "../bin"; # location of tm executables
my $absbinpath = abs_path($binpath); # we'll be doing a lot of chdiring...
--- 24,29 ----
! my $tmtestpath = dirname $0; # directory containing this script
! my $binpath = "$tmtestpath/../bin"; # location of tm executables
my $absbinpath = abs_path($binpath); # we'll be doing a lot of chdiring...
***************
*** 47,52 ****
if( @ARGV ) {
for(@ARGV) {
! -f && file_process_test_file( $_ );
! -d && find( \&find_process_test_file, $_ );
}
} else {
--- 48,58 ----
if( @ARGV ) {
for(@ARGV) {
! if( -f ) {
! file_process_test_file( $_ );
! } elsif( -d ) {
! find( \&find_process_test_file, $_ );
! } else {
! print STDERR "File $_ not found.\n";
! }
}
} else {
|
|
From: Scott B. <br...@us...> - 2001-01-04 23:19:05
|
Update of /cvsroot/trestlemail/trestlemail/bin
In directory usw-pr-cvs1:/tmp/cvs-serv12020/bin
Modified Files:
trestlemail
Log Message:
dev_0-823 merge
Index: trestlemail
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/bin/trestlemail,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -r1.23 -r1.24
*** trestlemail 2000/12/19 02:31:41 1.23
--- trestlemail 2001/01/04 23:19:07 1.24
***************
*** 21,25 ****
my $version = "0.83";
-
use strict;
use Time::Local;
--- 21,24 ----
***************
*** 245,249 ****
matrice( "Unknown parameter $1 on line $. of $rcfile\n" );
}
! } elsif( /^\s*\/((?:[^\\\/]*(?:\\.)?(?:\[(?:[^\]\\]*(?:\\.))\])?)+)\/\s*\:\s*(.*)\s*$/ ) {
# That monstrosity above is supposed to match a regular expression.
# I tried to get as close as I could, but I haven't ensured its perfection.
--- 244,248 ----
matrice( "Unknown parameter $1 on line $. of $rcfile\n" );
}
! } elsif( /^\s*\/((?:[^\\\[\/]|(?:\\.)|(?:\[(?:[^\]\\]|(?:\\.))*\]))*)\/\s*\:\s*(.*)\s*$/ ) {
# That monstrosity above is supposed to match a regular expression.
# I tried to get as close as I could, but I haven't ensured its perfection.
|
|
From: Scott B. <br...@us...> - 2001-01-04 23:19:05
|
Update of /cvsroot/trestlemail/trestlemail In directory usw-pr-cvs1:/tmp/cvs-serv12020 Modified Files: CVSTAGS Log Message: dev_0-823 merge Index: CVSTAGS =================================================================== RCS file: /cvsroot/trestlemail/trestlemail/CVSTAGS,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -r1.12 -r1.13 *** CVSTAGS 2000/12/19 02:31:41 1.12 --- CVSTAGS 2001/01/04 23:19:07 1.13 *************** *** 16,19 **** --- 16,20 ---- rel_0-82: Trestlemail Release 0.82 rel_0-822: Trestlemail Release 0.822 + dev_0-823: version sent to Aristide to try to sort 5.004 issues dev_0-83: Trestlemail + Realname. Not for long... |
|
From: Scott B. <br...@us...> - 2001-01-04 22:35:25
|
Update of /cvsroot/trestlemail/trestlemail/test/running/conf
In directory usw-pr-cvs1:/tmp/cvs-serv6332
Modified Files:
Tag: rel_0-82-bugfixes
regexps3.rc
Added Files:
Tag: rel_0-82-bugfixes
20-RE_qmailFAQTest.test
Log Message:
Added Test 20 to test the RE in the FAQ qmail question
--- NEW FILE ---
# qmail FAQ Test
# Scott Bronson
# 02 Jan 2001
#
# There's an example RE in the FAQ (trestlemail-faq.html#qmail).
# Let's just make sure that works.
#
trestlemail @-n
@Rc regexps3.rc
@To jo-ann
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi an...@an...
Index: regexps3.rc
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/running/conf/Attic/regexps3.rc,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -r1.1.2.1 -r1.1.2.2
*** regexps3.rc 2001/01/04 20:10:48 1.1.2.1
--- regexps3.rc 2001/01/04 22:35:26 1.1.2.2
***************
*** 9,12 ****
--- 9,14 ----
/[\\\]]-[\\\]]/: back-brack@localhost
+ /.*-ann$/: an...@an...
+
/[/]/: slash@localhost
/[/][/]/: slashslash@localhost
|
|
From: Scott B. <br...@us...> - 2001-01-04 21:59:48
|
Update of /cvsroot/trestlemail/trestlemail/doc In directory usw-pr-cvs1:/tmp/cvs-serv1171/doc Modified Files: trestlemail-faq.html Log Message: Updated faq to include qmail issues and <a name=""> tags for each question. Index: trestlemail-faq.html =================================================================== RCS file: /cvsroot/trestlemail/trestlemail/doc/trestlemail-faq.html,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -r1.11 -r1.12 *** trestlemail-faq.html 2001/01/03 06:55:50 1.11 --- trestlemail-faq.html 2001/01/04 21:59:50 1.12 *************** *** 18,22 **** href="mailto:br...@tr...?subject=Trestlemail%20FAQ">br...@tr...</a></p> ! <p>Trestlemail 0.822, 24 Oct 2000<br> <a href="http://www.trestle.com/linux/trestlemail/">http://www.trestle.com/linux/trestlemail</a></p> --- 18,22 ---- href="mailto:br...@tr...?subject=Trestlemail%20FAQ">br...@tr...</a></p> ! <p>Trestlemail 0.83, 04 Jan 2000<br> <a href="http://www.trestle.com/linux/trestlemail/">http://www.trestle.com/linux/trestlemail</a></p> *************** *** 25,30 **** <p></p> ! <h3>Why use Trestlemail instead of Fetchmail's built-in multidrop ! distribution?</h3> <p>If Fetchmail alone provides all the distribution functionality that you --- 25,30 ---- <p></p> ! <h3><a name="why-tm">1. Why use Trestlemail instead of Fetchmail's built-in multidrop ! distribution?</a></h3> <p>If Fetchmail alone provides all the distribution functionality that you *************** *** 48,72 **** </ul> ! <h3>Trestlemail appears to work fine. However, if I send mail to 2 people, ! each person receives 2 copies of the same email, if I send to 3 people, each ! person receives 3 copies, ...</h3> ! ! <p>This usually happens when the MDA storing the mail in your multi-drop ! mailbox isn't adding envelope information.</p> ! ! <p>Let's say you send a message to a...@tr..., b...@tr..., and ! c...@tr.... All three messages are stored in the multi-drop mailbox. ! Without envelope information, it appears to Fetchmail (and therefore ! Trestlemail) that these are three separate messages, and each message should ! be sent to each recipient. Therefore, a...@tr..., b...@tr..., and ! C...@tr... each receive three copies of the message.</p> ! ! <p>Envelope information lets Fetchmail discover exactly who this message is ! intended for. Envelope information can be found in two places: in the ! Received headers (see the <a href="trestlemail-example.html">Trestlemail Example</a>, especially <a href="trestlemail-example.html#Received">step ! 11</a>, for more about this), or in the X-Envelope-To header.</p> ! <h3>OK, but how do I configure Sendmail to do that?</h3> <p>Here's a good answer from eSoft, Inc's web site. (I would link to it, but --- 48,109 ---- </ul> ! <h3><a name="envelope">2. Trestlemail appears to work fine. However...</a> ! <ul> ! <li>Users are receiving duplicate copies of messages.</li> ! <li>All bccs go to the Trestlemail administrator.</li> ! <li>All mailing list mail goes to the Trestlemail administrator.</li> ! </ul> ! </h3> ! ! <p>These are all symptoms of your ISP not properly inserting ! envelope information into the messages stored in your multi-drop ! mailbox. Envelope information is <i>required</i>. If your ! ISP doesn't include it then they are not properly hosting ! a multi-drop mailbox.</p> ! ! <p>Let me describe this with an example. Let's say your ISP receives a single ! message addressed to a...@tr..., b...@tr... and blind-carbon-copied to ! c...@tr.... When your ISP receives the message, they also receive envelope ! information that describes who the message is really for. This information is not ! found anywhere in the message; certainly not in the message's "To:" ! header since the To header would read: ! </p> ! ! <blockquote><pre> ! Received: from wsgc-bh.wsgc.com by meer.meer.net ! To: a...@tr..., b...@tr... ! Subject: test message ! </pre></blockquote> ! ! <p>c...@tr... is missing, of course, since it's a bcc.</p> ! ! <p>Since the envelope infomration says the message is addressed to three ! local recipients, three copies ! of the message are stored in the multi-drop mailbox. Let's ! assume now that the ISP completely throws away the envelope ! information and stores the message exactly as it received it. ! </p> ! ! <p>Fetchmail, without envelope information, does the best ! it can and uses the To: header to try to deliver the message. ! Remember that there are three identical copies of this message ! in the multi-drop mailbox, each with a To: line addressed to a...@tr... ! and b...@tr.... And that's how they're delivered: a...@tr... ! gets three copies of this message, b...@tr... gets three copies ! as well, and c...@tr... gets nothing whatsoever.</p> ! ! <p>If envelope information were stored with each message, a...@tr..., ! b...@tr..., and c...@tr... would each receive one copy of this ! message exactly as intended. ! </p> ! ! <p> ! Envelope information can be found in any of three places: ! in the Received headers (see the <a href="trestlemail-example.html">Trestlemail Example</a>, especially <a href="trestlemail-example.html#Received">step ! 11</a>, for more about this), in the X-Envelope-To header, or in the ! Delivered-To header.</p> ! <h4><a name="sendmail-envelope">2.1. How do I configure Sendmail to add the X-Envelope-To?</a></h4> <p>Here's a good answer from eSoft, Inc's web site. (I would link to it, but *************** *** 116,148 **** </pre> ! <h3>But I can't get my lame ISP to insert the X-Envelope-To header!</h3> ! Do you have shell access to your account? And procmail? If so, you can ! filter out the duplicates. Put the following line into your the .procmailrc ! file on the remote machine: ! ! <font size="-1"><i>(thanks to Tore Reimers)</i></font> <blockquote> <pre> ! # -Make sure you have the correct path to formail... :0 Wh: msgid.lock | formail -D 8192 msgid.cache </pre> </blockquote> - - <h3>Does Trestlemail work with MMDF?</h3> ! <p>Yes indeed.</p> - <h3>How about Postfix? Exim? Qmail?</h3> - <p>Postfix is sweet, isn't it? Yep, it works with all of those.</p> ! <p>They each include a wrapper program or script to emulate the behavior ! of sendmail. Trestlemail talks to the wrapper and everything should Just ! Work.</p> ! <h3>We just moved domains, and I want to use Trestlemail to re-distribute mail ! from each of my employee's old mailboxes. Why won't it?</h3> <p>This is actually a Fetchmail configuration problem. Fetchmail considers --- 153,237 ---- </pre> ! <h4><a name="lame-isp">2.2. But I can't get my lame ISP to insert the ! X-Envelope-To header, and the Received header doesn't always work!</a></h4> ! ! <p>The Received header rarely works well at carrying Envelope information. ! Too many MTAs use it too differently for it to be relied upon.</p> ! ! <p>Does your ISP insert a Delivered-To: header like qmail? If so, see ! <a href="#qmail">Trestlemail/qmail compatiblity</a>.</p> + <p>Otherwise, aside from switching to an ISP that does insert proper + envelope information, there's no good solution. However, if you have procmail, + you can at least filter out the duplicates. NOTE: this workaround is + <i>very</i> imperfect since it doesn't fix the mailing list or bcc problems! + Use this only if you're not in a production environment and you can + tolerate all mailing list mail and bccs going to the trestlemail administrator + for redirection.</p> + + <p>Despite this warning, if you still want to do this, here's how. + Put the following lines into the .procmailrc file on the remote machine: + </p> + <blockquote> + <font size="-1"><i>(thanks to Tore Reimers)</i></font> <pre> ! # Make sure you have the correct path to formail... :0 Wh: msgid.lock | formail -D 8192 msgid.cache </pre> </blockquote> ! <h3><a name="MTAs">3. Does Trestlemail work with Postfix? Exim? MMDF?</a></h3> <p>Postfix is sweet, isn't it? Yep, it works with all of those.</p> + They include wrapper programs to emulate the behavior of sendmail. + Trestlemail talks to the wrapper and everything should Just Work.</p> + + <h4><a name="qmail">3.1. What about qmail?</a></h4> ! <p>Yes, Trestlemail and qmail work well together. However, there are some ! <a href="#envelope">envelope</a> issues that you will need to sort out. ! qmail uses the Delivered-To header to carry envelope information and ! Fetchmail will probably need a bit of help recognizing the actual ! envelope address. ! </p> ! ! <p>First, read the discussion on qmail in the ! <a href="http://www.tuxedo.org/~esr/fetchmail/fetchmail-FAQ.html#T2">Fetchmail ! FAQ (question T2)</a>. ! </p> ! ! <p>However, you can ignore the last few paragraphs about how to strip ! the 'mbox-userstr-' from the address since Trestlemail can do this for ! you. Simply add one line for each user in your trestlemailrc file, ! replacing <i>mbox-userstr-</i> with whatever string your ISP inserts. ! The lines to add are in red:</p> ! ! <blockquote><pre> ! <span style="color:red">mbox-userstr-joe: joe</span> ! joe: jo...@jo... ! <span style="color:red">mbox-userstr-pam: pam</span> ! pam: pa...@pa... ! <span style="color:red">mbox-userstr-username: username</span> ! username: use...@do... ! </pre></blockquote> ! ! <p>If you don't know what string your ISP inserts, or if it changes, ! you can use regular expressions instead. The following will match ! any email address that ends with "ann":</p> ! ! <blockquote><pre> ! /.*-ann$/: an...@an... ! </pre></blockquote> ! ! <p>However, this is generally undesirable because it will match a ! user named "carol-ann" as well. You will have to be very careful ! to ensure that each regular expression is unique and in the right ! order. If at all possible, use the previous solution instead. ! And it's even faster.</p> ! <h3><a name="multi-pop">4. We just moved domains, and I want to use Trestlemail to re-distribute mail ! from each of my employee's old mailboxes. Why won't it?</a></h3> <p>This is actually a Fetchmail configuration problem. Fetchmail considers *************** *** 163,167 **** information is centralized in a single trestlemailrc file.</p> ! <h3>When I send mail to a user, Trestlemail sends an "UNKNOWN USER" message to the Trestlemail admnistrator.</h3> --- 252,256 ---- information is centralized in a single trestlemailrc file.</p> ! <h3><a name="unknown-user">5. When I send mail to a user, Trestlemail sends an "UNKNOWN USER" message to the Trestlemail admnistrator.</h3> *************** *** 174,178 **** does not work.</p> ! <h3>How does Trestlemail figure out who to send the message to?</h3> <p>For each user in the rc file, you can specify any combination of names and --- 263,267 ---- does not work.</p> ! <h3><a name="sending">6. How does Trestlemail figure out who to send the message to?</a></h3> <p>For each user in the rc file, you can specify any combination of names and *************** *** 211,216 **** "<code>u morefriends: friends, karl@localhost</code>".</p> ! <h3>I got the problem: Deep recursion on subroutine "main :: lookup_user_name" ! at /home/myacct/trestlemail/trestlemail line 424. Out of memory !</h3> <p><em><strong>note:</strong></em> Trestlemail 0.8 and up has recursion --- 300,305 ---- "<code>u morefriends: friends, karl@localhost</code>".</p> ! <h3><a name="recursion">7. I got the problem: Deep recursion on subroutine "main :: lookup_user_name" ! at /home/myacct/trestlemail/trestlemail line 424. Out of memory!</a></h3> <p><em><strong>note:</strong></em> Trestlemail 0.8 and up has recursion *************** *** 242,247 **** and the message is sent.</p> ! <h3>I still don't get it. Can you give me a full description of how ! Trestlemail works?</h3> <p>Well, Trestlemail is flexible enough that it would be very difficult to --- 331,336 ---- and the message is sent.</p> ! <h3><a name="full-desc">8. I still don't get it. Can you give me a full description of how ! Trestlemail works?</a></h3> <p>Well, Trestlemail is flexible enough that it would be very difficult to |
|
From: Scott B. <br...@us...> - 2001-01-04 21:59:48
|
Update of /cvsroot/trestlemail/trestlemail In directory usw-pr-cvs1:/tmp/cvs-serv1171 Modified Files: TODO Log Message: Updated faq to include qmail issues and <a name=""> tags for each question. Index: TODO =================================================================== RCS file: /cvsroot/trestlemail/trestlemail/TODO,v retrieving revision 1.26 retrieving revision 1.27 diff -C2 -r1.26 -r1.27 *** TODO 2000/12/19 02:31:41 1.26 --- TODO 2001/01/04 21:59:50 1.27 *************** *** 19,22 **** --- 19,25 ---- - 0.85 Load balancing plugin + - 0.85 Add "How do I send default mail to something other than + the catastrophe address?" + - 0.85 local-delivery plugin Give the local-delivery plugin a command to execute if it could |
Update of /cvsroot/trestlemail/trestlemail/test/running/conf
In directory usw-pr-cvs1:/tmp/cvs-serv20101
Added Files:
Tag: rel_0-82-bugfixes
01-RE_Empty.test 02-RE_NoEmpty.test 03-RE_EscapedSlash.test
04-RE_EscapedSlashSlash.test 05-RE_EscapedBkslash.test
06-RE_EscapedBkslashBkslash.test 07-RE_OnlySlash.test
08-RE_OnlySlashSlash.test 09-RE_SlashSlashSlash.test
10-RE_AnySlashSlash.test 11-RE_CharClassSlash.test
12-RE_EscapedOpenBracket.test 13-RE_EscapedCloseBracket.test
14-RE_CharClassOpenBracket.test
15-RE_CharClassCloseBracket.test 16-RE_CharClassBackslash.test
17-RE_NonRE.test 18-RE_DefaultRE.test 19-RE_BackBrack.test
regexps1.rc regexps2.rc regexps3.rc
Log Message:
Adding all RE tests
--- NEW FILE ---
# Empty Regular Expression
# Scott Bronson
# 02 Jan 2001
#
# This test ensures that the RE-matching-RE will match
# the empty regular expression //.
#
trestlemail @-n
@Rc regexps1.rc
@To any-user
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi empty@localhost
--- NEW FILE ---
# No Empty Regular Expression
# Scott Bronson
# 02 Jan 2001
#
# This test ensures that if there's no default RE,
# mail to an unkown user goes to the catastrophe addr.
#
trestlemail @-n
@Rc regexps2.rc
@To any-user
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Date: Date date date date date
From: tre...@tr...
To: root@localhost
Subject: UNKNOWN USER: any-user
Unknown recipient: any-user
>From: br...@do...
>Subject: Test Message
>Date: Thu, 4 Nov 1999 14:43:08 +0100
>
>This is a plain ol' message.
>
---- SENDMAIL ARGS: -oem -oi root@localhost
--- NEW FILE ---
# Escaped Slash
# Scott Bronson
# 02 Jan 2001
#
# The escaped slash regular expression should match this one.
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps1.rc
@To /
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi slash@localhost
--- NEW FILE ---
# Escaped SlashSlash
# Scott Bronson
# 02 Jan 2001
#
# The escaped slashslash regular expression should match this one.
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps1.rc
@To //
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi slash@localhost
--- NEW FILE ---
# Escaped Backslash
# Scott Bronson
# 02 Jan 2001
#
# The escaped backslash regular expression should match this one.
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
# Really, this is only 1 backslash. Remember that the following
# is passed to the shell, and the shell will interpret shell escapes...
#
trestlemail @-n
@Rc regexps1.rc
@To \\
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi bkslash@localhost
--- NEW FILE ---
# Escaped BackslashBackslash
# Scott Bronson
# 02 Jan 2001
#
# The escaped backslash regular expression should match this one.
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
# Really, this is only 2 backslashes. Remember that the following
# is passed to the shell, and the shell will interpret shell escapes...
#
trestlemail @-n
@Rc regexps1.rc
@To \\\\
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi bkslashbkslash@localhost
--- NEW FILE ---
# Only Slash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps2.rc
@To /
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi slash@localhost
--- NEW FILE ---
# Only SlashSlash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps2.rc
@To //
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi slashslash@localhost
--- NEW FILE ---
# SlashSlashSlash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps2.rc
@To ///
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi anyslashslash@localhost
--- NEW FILE ---
# Any SlashSlash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps2.rc
@To a//b
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi anyslashslash@localhost
--- NEW FILE ---
# Char Class Slash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps3.rc
@To /
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi slash@localhost
--- NEW FILE ---
# Escaped Open Bracket
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps1.rc
@To [
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi openbracket@localhost
--- NEW FILE ---
# Escaped Close Bracket
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps1.rc
@To ]
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi closebracket@localhost
--- NEW FILE ---
# Char Class Open Bracket
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps3.rc
@To [
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi openbracket@localhost
--- NEW FILE ---
# Char Class Close Bracket
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
trestlemail @-n
@Rc regexps3.rc
@To ]
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi closebracket@localhost
--- NEW FILE ---
# Char Class Backslash
# Scott Bronson
# 02 Jan 2001
#
# (this will never happen in real life -- it's just meant to test
# the RE-matching-RE).
#
# The command line below is interpreted by the shell, so "\\"
# is really only a single backslash.
#
trestlemail @-n
@Rc regexps3.rc
@To \\
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi backslash@localhost
--- NEW FILE ---
# NonRE
# Scott Bronson
# 02 Jan 2001
#
# Ensure non-RE names are interpreted before REs.
#
trestlemail @-n
@Rc regexps1.rc
@To nonre
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi actual-user@localhost
--- NEW FILE ---
# NonRE
# Scott Bronson
# 02 Jan 2001
#
# Ensure non-RE names are interpreted before REs.
#
trestlemail @-n
@Rc regexps3.rc
@To any-addr-at-all
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi default@localhost
--- NEW FILE ---
# BackBrack
# Scott Bronson
# 02 Jan 2001
#
# Make sure multiple char classes containing multiple chars
# are handled.
#
trestlemail @-n
@Rc regexps3.rc
@To \\-]
@Fr te...@tr...
< ../../plain.msg
-------------------------- Output: -----------------------------
Received: from Fetchmail by Trestlemail MDA VERSION;
Date date date date date
From: br...@do...
Subject: Test Message
Date: Thu, 4 Nov 1999 14:43:08 +0100
This is a plain ol' message.
---- SENDMAIL ARGS: -oem -oi back-brack@localhost
--- NEW FILE ---
# regexps1.rc
#
# This rc file tests matching regular expressions containing
# a lot of escaping. It also tests the empty regular expression
# (which should match any not-previously-matched address)
#
domain = trestle.com
binpath = ../../../bin
# forward slashes
# order is important: both / and // will match 1st.
# see regexps2.rc to ensure // maches 2nd as well, w/o 1st.
/\//: slash@localhost
/\/\//: slashslash@localhost
# backward slashes
# order is important: \\ will match 1st, \ will only match 2nd
/\\\\/: bkslashbkslash@localhost
/\\/: bkslash@localhost
# brackets
/\[/: openbracket@localhost
/]/: closebracket@localhost
# Fail if we select the wrong RE (slash above should be chosen)
/\//: badslash@localhost
//: empty@localhost
# ensure that this takes precedence over any RE
nonre: actual-user@localhost
--- NEW FILE ---
# regexps2.rc
#
# This rc file tests matching regular expressions containing
# a lot of escaping. These REs, however, can't be tested in
# the same RC file as the ones in regexps1.rc
#
domain = trestle.com
binpath = ../../../bin
/^\/$/: slash@localhost
/^\/\/$/: slashslash@localhost
/\/\//: anyslashslash@localhost
# Fail if we select the wrong RE (slash above should be chosen)
/\//: badslash@localhost
--- NEW FILE ---
# regexps3.rc
#
# This file tests matching regular expressions containing character classes.
#
domain = trestle.com
binpath = ../../../bin
/[\\\]]-[\\\]]/: back-brack@localhost
/[/]/: slash@localhost
/[/][/]/: slashslash@localhost
/[[]/: openbracket@localhost
/[\]]/: closebracket@localhost
/[\\]/: backslash@localhost
/.*/: default@localhost
|
|
From: Scott B. <br...@us...> - 2001-01-04 18:05:51
|
Update of /cvsroot/trestlemail/trestlemail
In directory usw-pr-cvs1:/tmp/cvs-serv5281
Modified Files:
Tag: rel_0-82-bugfixes
CVSTAGS
Log Message:
Add 0.823
Index: CVSTAGS
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/CVSTAGS,v
retrieving revision 1.7.2.1
retrieving revision 1.7.2.2
diff -C2 -r1.7.2.1 -r1.7.2.2
*** CVSTAGS 2000/10/20 01:24:55 1.7.2.1
--- CVSTAGS 2001/01/04 18:05:52 1.7.2.2
***************
*** 13,16 ****
--- 13,17 ----
rel_0-82: Trestlemail Release 0.82
rel_0-822: Trestlemail Release 0.822
+ dev_0-823: version sent to Aristide to try to sort 5.004 issues
branches:
|
|
From: Scott B. <br...@us...> - 2001-01-04 18:04:22
|
Update of /cvsroot/trestlemail/trestlemail/test/delivery
In directory usw-pr-cvs1:/tmp/cvs-serv4630/test/delivery
Modified Files:
Tag: rel_0-82-bugfixes
01-KnownAndUnknown.test
Log Message:
Update version # to 0.823
Index: 01-KnownAndUnknown.test
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/delivery/01-KnownAndUnknown.test,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -r1.1.2.1 -r1.1.2.2
*** 01-KnownAndUnknown.test 2000/10/21 01:13:43 1.1.2.1
--- 01-KnownAndUnknown.test 2001/01/04 18:04:23 1.1.2.2
***************
*** 14,18 ****
@Rc testrc
@To known-user unknown-user
! @Fr sc...@tr...
< ../plain.msg
--- 14,18 ----
@Rc testrc
@To known-user unknown-user
! @Fr te...@tr...
< ../plain.msg
|
|
From: Scott B. <br...@us...> - 2001-01-04 18:04:22
|
Update of /cvsroot/trestlemail/trestlemail/bin
In directory usw-pr-cvs1:/tmp/cvs-serv4630/bin
Modified Files:
Tag: rel_0-82-bugfixes
trestlemail
Log Message:
Update version # to 0.823
Index: trestlemail
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/bin/trestlemail,v
retrieving revision 1.18.2.4
retrieving revision 1.18.2.5
diff -C2 -r1.18.2.4 -r1.18.2.5
*** trestlemail 2001/01/03 09:55:43 1.18.2.4
--- trestlemail 2001/01/04 18:04:22 1.18.2.5
***************
*** 15,19 ****
# 19 May 2000 v0.8: Remove the ability to generate mail loops, add REs
! my $version = "0.822";
use strict;
--- 15,19 ----
# 19 May 2000 v0.8: Remove the ability to generate mail loops, add REs
! my $version = "0.823";
use strict;
|
|
From: Scott B. <br...@us...> - 2001-01-04 18:04:22
|
Update of /cvsroot/trestlemail/trestlemail/test
In directory usw-pr-cvs1:/tmp/cvs-serv4630/test
Modified Files:
Tag: rel_0-82-bugfixes
README
Log Message:
Update version # to 0.823
Index: README
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/README,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -C2 -r1.2.2.1 -r1.2.2.2
*** README 2000/10/21 01:32:28 1.2.2.1
--- README 2001/01/04 18:04:22 1.2.2.2
***************
*** 39,42 ****
--- 39,43 ----
plugins: tests the Trestlemail plugins
running: tests the Fetchmail<->Trestlemail interaction, cmd-line args, etc.
+ running/conf: Tests various trestlemailrc parsing issues
|
|
From: Scott B. <br...@us...> - 2001-01-04 18:04:22
|
Update of /cvsroot/trestlemail/trestlemail
In directory usw-pr-cvs1:/tmp/cvs-serv4630
Modified Files:
Tag: rel_0-82-bugfixes
install
Log Message:
Update version # to 0.823
Index: install
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/install,v
retrieving revision 1.13.2.1
retrieving revision 1.13.2.2
diff -C2 -r1.13.2.1 -r1.13.2.2
*** install 2000/10/24 17:24:45 1.13.2.1
--- install 2001/01/04 18:04:22 1.13.2.2
***************
*** 14,18 ****
use strict;
! my $version = "0.822";
$| = 1; # flush stdout immediately
--- 14,18 ----
use strict;
! my $version = "0.823";
$| = 1; # flush stdout immediately
|
|
From: Scott B. <br...@us...> - 2001-01-03 09:55:48
|
Update of /cvsroot/trestlemail/trestlemail/bin
In directory usw-pr-cvs1:/tmp/cvs-serv23038
Modified Files:
Tag: rel_0-82-bugfixes
trestlemail
Log Message:
transpose \ and [ to make re matching re regular
Index: trestlemail
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/bin/trestlemail,v
retrieving revision 1.18.2.3
retrieving revision 1.18.2.4
diff -C2 -r1.18.2.3 -r1.18.2.4
*** trestlemail 2001/01/03 06:18:45 1.18.2.3
--- trestlemail 2001/01/03 09:55:43 1.18.2.4
***************
*** 225,229 ****
matrice( "Unknown parameter $1 on line $. of $rcfile\n" );
}
! } elsif( /^\s*\/((?:[^\\\/\[]|(?:\\.)|(?:\[(?:[^\]\\]|(?:\\.))*\]))*)\/\s*\:\s*(.*)\s*$/ ) {
# That monstrosity above is supposed to match a regular expression.
# I tried to get as close as I could, but I haven't ensured its perfection.
--- 225,229 ----
matrice( "Unknown parameter $1 on line $. of $rcfile\n" );
}
! } elsif( /^\s*\/((?:[^\\\[\/]|(?:\\.)|(?:\[(?:[^\]\\]|(?:\\.))*\]))*)\/\s*\:\s*(.*)\s*$/ ) {
# That monstrosity above is supposed to match a regular expression.
# I tried to get as close as I could, but I haven't ensured its perfection.
|
|
From: Scott B. <br...@us...> - 2001-01-03 08:27:01
|
Update of /cvsroot/trestlemail/trestlemail/test
In directory usw-pr-cvs1:/tmp/cvs-serv10325
Modified Files:
Tag: rel_0-82-bugfixes
tmtest
Log Message:
Make tmtest print an error if a named test can't be found
Index: tmtest
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/tmtest,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -C2 -r1.1.2.2 -r1.1.2.3
*** tmtest 2001/01/03 08:21:55 1.1.2.2
--- tmtest 2001/01/03 08:26:58 1.1.2.3
***************
*** 48,53 ****
if( @ARGV ) {
for(@ARGV) {
! -f && file_process_test_file( $_ );
! -d && find( \&find_process_test_file, $_ );
}
} else {
--- 48,58 ----
if( @ARGV ) {
for(@ARGV) {
! if( -f ) {
! file_process_test_file( $_ );
! } elsif( -d ) {
! find( \&find_process_test_file, $_ );
! } else {
! print STDERR "File $_ not found.\n";
! }
}
} else {
|
|
From: Scott B. <br...@us...> - 2001-01-03 08:21:58
|
Update of /cvsroot/trestlemail/trestlemail/test
In directory usw-pr-cvs1:/tmp/cvs-serv9990
Modified Files:
Tag: rel_0-82-bugfixes
tmtest
Log Message:
Make tmtest work when with any directory as cwd (before, you had to
cd to tmtest's dir before running it).
Index: tmtest
===================================================================
RCS file: /cvsroot/trestlemail/trestlemail/test/tmtest,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -r1.1.2.1 -r1.1.2.2
*** tmtest 2000/10/21 01:32:28 1.1.2.1
--- tmtest 2001/01/03 08:21:55 1.1.2.2
***************
*** 24,28 ****
! my $binpath = "../bin"; # location of tm executables
my $absbinpath = abs_path($binpath); # we'll be doing a lot of chdiring...
--- 24,29 ----
! my $tmtestpath = dirname $0; # directory containing this script
! my $binpath = "$tmtestpath/../bin"; # location of tm executables
my $absbinpath = abs_path($binpath); # we'll be doing a lot of chdiring...
|
|
From: Scott B. <br...@us...> - 2001-01-03 07:39:33
|
Update of /cvsroot/trestlemail/trestlemail/test/running/conf In directory usw-pr-cvs1:/tmp/cvs-serv5933/conf Log Message: Directory /cvsroot/trestlemail/trestlemail/test/running/conf added to the repository --> Using per-directory sticky tag `rel_0-82-bugfixes' |
|
From: Scott B. <br...@us...> - 2001-01-03 07:37:18
|
Update of /cvsroot/trestlemail/trestlemail/test/running
In directory usw-pr-cvs1:/tmp/cvs-serv5616/running
Removed Files:
Tag: rel_0-82-bugfixes
trestlemailrc
Log Message:
Removed unused test files.
--- trestlemailrc DELETED ---
|
|
From: Scott B. <br...@us...> - 2001-01-03 07:37:18
|
Update of /cvsroot/trestlemail/trestlemail/test/results
In directory usw-pr-cvs1:/tmp/cvs-serv5616/results
Removed Files:
Tag: rel_0-82-bugfixes
arg1 subj1 subj2 subj3 subj4 subj5 subj6 subj7
Log Message:
Removed unused test files.
--- arg1 DELETED ---
--- subj1 DELETED ---
--- subj2 DELETED ---
--- subj3 DELETED ---
--- subj4 DELETED ---
--- subj5 DELETED ---
--- subj6 DELETED ---
--- subj7 DELETED ---
|
|
From: Scott B. <br...@us...> - 2001-01-03 06:55:53
|
Update of /cvsroot/trestlemail/trestlemail/doc In directory usw-pr-cvs1:/tmp/cvs-serv2473 Modified Files: trestlemail-faq.html Log Message: Add a brief explanation for MTA sendmail wrappers Index: trestlemail-faq.html =================================================================== RCS file: /cvsroot/trestlemail/trestlemail/doc/trestlemail-faq.html,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -r1.10 -r1.11 *** trestlemail-faq.html 2000/12/15 20:24:11 1.10 --- trestlemail-faq.html 2001/01/03 06:55:50 1.11 *************** *** 139,142 **** --- 139,146 ---- <p>Postfix is sweet, isn't it? Yep, it works with all of those.</p> + <p>They each include a wrapper program or script to emulate the behavior + of sendmail. Trestlemail talks to the wrapper and everything should Just + Work.</p> + <h3>We just moved domains, and I want to use Trestlemail to re-distribute mail from each of my employee's old mailboxes. Why won't it?</h3> |
