Re: [vchkpw] .qmail file with users with dot

2003-06-13 Thread James Raftery
On Fri, Jun 13, 2003 at 10:51:37AM +0100, Bruno Morais wrote:
 The problem is that .qmail files works ok for users like
 [EMAIL PROTECTED],  [EMAIL PROTECTED],
 [EMAIL PROTECTED] but when i use
 [EMAIL PROTECTED] qmail ignores the .qmail file and uses the
 .qmail-default file.

man dot-qmail(5). See the 'EXTENSION ADDRESSES' section.


ATB,
james



Re: [vchkpw] Control/Me?

2003-04-01 Thread James Raftery
On Mon, Mar 31, 2003 at 10:32:14PM -0800, Wil Hatfield wrote:
 Received: from unknown (HELO ns1.a-zhost.com) (216.120.76.2)
   by h6.a-zhost.com with SMTP; 31 Mar 2003 21:03:59 -0800

 Where does the h6.a-zhost.com value come from shown above. I thought
 it came from control/me which I have checked and double checked. This
 email did not go through h6.a-zhost.com at all.

That's from tcpserver. Check the value of the -l flag to tcpserver, if
present. Otherwise tcpserver will look up the system's name in DNS. Check
your reverses.


ATB,
james



Re: [vchkpw] About to release new devel version 5.3.20

2003-03-25 Thread James Raftery
On Mon, Mar 24, 2003 at 01:53:58PM -0600, Ken Jones wrote:
 Does anyone have any patches they  would like to submit?
 
Hi Ken,

I've a patch at  http://romana.now.ie/#vadddomain-maildir  which
slighly modifies the -e flag to vadddomain.

I wanted a way to specify a ``catchall'' in the same way as qmailadmin
does: supply a pathname to write directly into the catchall user's
Maildir. Using -e as it is currently -- specifying an email address --
means I don't get access to the original envelope recipient in the
Delivered-To header line.

Applying the patch does not change vaddomain's behaviour when one
specifies an email address with -e. But if one specifies a value without
an @ symbol it is taken as a user into whose Maildir catchall mail
should be delivered (as qmailadmin does).

With the patch, I can say:

  vadddomain -e postmaster maildir.org

And get:

  fridge# cat maildir.org/.qmail-default 
  | /usr/local/vpopmail/bin/vdelivermail '' 
/usr/local/vpopmail/domains/maildir.org/postmaster


ATB,
james



[vchkpw] [announce] vodmr - ODMR server for vpopmail+qmail

2002-09-06 Thread James Raftery


Hi,

I have written an RFC 2645 On-Demand Mail Relay (ODMR) /
Authenticated TURN (ATRN) server for vpopmail/vchkpw mail servers
running qmail. It has a working title of ``vodmr''. It is written 
in perl and is available under the same licence as perl itself.

It's available for download from

  http://romana.now.ie/#vodmr

The current release is version 0.8, released 6th September 2002.

It should be considered as beta software. It has been tested with
fetchmail 5.9.11/5.9.13 and XATRN 1.2.2 ODMR clients and qmail-smtpd
1.03, sendmail 8.9.3/8.11.3 and MDaemon 5.0.7 SMTP servers. It hasn't
yet been subjected to widespread public testing.

This is a request for beta testers to download it, try it out and 
let me know how you get along with the program itself and its 
documentation.

For the program to work, you will need:
 1. A working vpopmail/vchkpw using qmail.
 2. Perl 5 with MIME::Base64, Mail::Header, CDB_File and
Digest::HMAC_MD5 modules
 3. Maildir mailboxes
 4. A UCSPI-TCP server (tcpserver is ideal) or inetd / xinetd


Some things to note;
 Requires vpopmail (and qmail)
 Uses your existing qmail configuration files
 No changes are needed to vpopmail or qmail
 Implements CRAM-MD5 challenge-response authentication (required by RFC)
 Uses either comment or password field of vpasswd.cdb for secrets
 Domains can be setup for ODMR with qmailadmin and/or the vpopmail
   command line tools
 Minimal implementation
 Message bouncing
 Logs to stderr (the default) or syslog 


The vodmr server is explicitly not a long running daemon.
tcpserver/inetd manage the networking elements, including starting the
vodmr daemon to service new connections. vodmr deals only with stdin,
stdout and stderr.

vodmr does not need to run as root so don't! Run it as your vpopmail
user. (It'll complain if you do run it as root)


PROBLEM REPORTING

If you want to report a problem, submit a patch, a comment or a
question please email [EMAIL PROTECTED].


Thanks,
james
-- 
James Raftery [EMAIL PROTECTED]