Re: Lost the Battle

2001-03-01 Thread Jason Radford


I must say being someone who's installed NOTES (R5) that it's all up
to who installed/configured it and their level of understanding of
the product.  Trouble with groupware products like Notes and Exchange
is companies figure they dont need moderate/highly priced people who
actually understand what they are doing (it's GUI, so it's easy, right?)

This is the downfall of today's reality in alot of companies, they
trade experienced employees for 'turn key' and 'easily maintainable'
products which seemly dont need an experienced staff to administer.  Or
at least that's the crap managers are being sold on.

I must say if I hear another Lotus rep extoll the virtues of 
"knowledgeware" one more time I'll shoot them! :)

Sorry, my rant for the month.

-Jason

On Thu, 01 Mar 2001 09:41:56 +0100 (MET)
Stefaan A Eeckels [EMAIL PROTECTED] wrote:

 
 On 28-Feb-2001 dennis wrote:
   My qmail project, only 1 week away from implementation, was canned, we are
   now moving to Lotus Notes.
 
 Condolences. A company I used to work with also replaced the qmail
 I installed (and which had worked flawlessly for 18 months) with
 Notes (they wanted shared calendars :-). Two months later, they
 had to be rescued by their ISP because they were being used as
 a SPAM relay. 
 
 Stefaan
 -- 
 How's it supposed to get the respect of management if you've got just
 one guy working on the project?  It's much more impressive to have a
 battery of programmers slaving away. -- Jeffrey Hobbs (comp.lang.tcl)
 



Re: Need Arguments for qmail

2001-02-20 Thread Jason Radford


 Recently switching from sendmail to qmail I have observed the difference in
 architecture between the two.  The modularization of qmail appeals to me
 in both simplicity and elegance, and it's superiority was evident in my
 smtp benchmarking between the two MTAs.  The only thing I miss from an admin
 standpoint is the readability of sendmail's logs vs. qmail/multilog.
 
 While I fully understand the justification of qmail's logging structure
 because of it's modularization, I am still left somewhat longing for a 
 more readable logfile.  Possibly over time I will develop a
 better skill for reading these logs, but for now that's my only concern
 since switching.  There may be tools to aid in this, however out of
 the box this doesnt seem to be the cause.
 
 Just my thoughts since running qmail for about a week.
 
 -Jason
 
  to that job.  Along the same lines is the fact that qmail IS broken up into
  separate services for each function, rather than a single process handling a
  wide variety of tasks.
  
  Kyle



Re: error in qmail logs

2001-02-14 Thread Jason Radford

On 14 Feb 2001 14:01:04 +
[EMAIL PROTECTED] (James R Grinter) wrote:

 qmHandle will attempt to shutdown qmail before removing the file from
 the queue, but it would seem that even if it fails to do so it will
 remove the file.

I wonder if supervise is starting qmail backup before qmHandle can perform
it's deletes?
 
  Messages in local queue: 0
  Messages in remote queue: 2
 
 don't know about the descrepancy in numbers, sorry.

After wandering around the /mess queue I found a number of old 0K files
hanging around without /info /local /remote counterparts.  

I guess I'll watch when I delete messages again to see if this occurs.

Thanks

-Jason
 
 James.
 



error in qmail logs

2001-02-13 Thread Jason Radford


hi all,

I'm getting a reoccuring error in my qmail logs,
I'm not sure I understand what it's trying to
tell me.

@40003a8a0e53036600b4 warning: trouble opening remote/4/2226680; will try again 
later
@40003a8a0e530367aa7c warning: trouble opening remote/10/2226663; will try again 
later

Thanks

-Jason



Re: error in qmail logs

2001-02-13 Thread Jason Radford


Actually I use a tool called qmHandle -d# to delete a few messages out of
qmail's message queue.  Funny thing is doing a qmHandle -l produces:

Messages in local queue: 0
Messages in remote queue: 2

But a qmail-qstat produces

messages in queue: 17
messages in queue but not yet preprocessed: 0

Is this because of qmHandle?

-Jason

On 14 Feb 2001 16:16:00 +1100
Brett Randall [EMAIL PROTECTED] wrote:

 On Tue, 13 Feb 2001, [EMAIL PROTECTED] wrote:
 
  hi all,
  
  I'm getting a reoccuring error in my qmail logs,
  I'm not sure I understand what it's trying to
  tell me.
  
  @40003a8a0e53036600b4 warning: trouble opening remote/4/2226680;
  will try again later @40003a8a0e530367aa7c warning: trouble
  opening remote/10/2226663; will try again later
  
  Thanks
  
  -Jason
 
 Means that you may have deleted files from the queue (eg
 /var/qmail/queue/mess/4/2226680) without deleting the information
 files (in /var/qmail/queue/remote). Either that or there's been some
 kind of corruption/permission change.
 -- 
 "The C Programming Language: A new language which combines the flexibility
 of assembly language with the power of assembly language."
 
 - Murphy's Introduction to C 
 



Re: Selective relaying with xinetd

2001-02-11 Thread Jason Radford


As a very new qmail guy (1 day) I would recommend the url:

http://www.palomine.net/qmail/selectiverelay.html

Had me in and out in 10 minutes, switching from inetd to tcpserver
(thanks chris Johnson if your on this list!).

Only caveat I ran into was 127.0.0.1 (localhost) has to go in there
too along with valid IP's if you need it, that goofed me up for 4-5 minutes
doing tests with telnet localhost 25.

-Jason

 
 Switch to tcpserver.  Chances are you can get it set up correctly in
 thirty minutes or less if you follow Life with qmail, and there are more
 eyes here familiar with tcpserver configuration than with xinetd.
 
 Charles
 -- 
 ---
 Charles Cazabon[EMAIL PROTECTED]
 GPL'ed software available at:  http://www.qcc.sk.ca/~charlesc/software/
 Any opinions expressed are just that -- my opinions.
 ---
 



sendmail migration

2001-02-10 Thread Jason Radford

Hi all,

I've spent some time looking over the qmail documenation and want to migrate
from sendmail because of it's lackluster virtual domain support.

The things I would like to do are:

1. Have email/pop accounts without adding system users (/etc/passwd)
2. Have clear seperation of the virual domains, with domain1 having a seperate
directory with it's /var/spool/mail equivelent.  So that mail would be delivered
to /domain1-com/jradford and another would be /domain2-com/jradford
3. Users getting their pop mail could use a username of [EMAIL PROTECTED] and 
other use [EMAIL PROTECTED] to login for their pop3 services and the qmail
pop3 daemon would know to go to the right /domain directory to retrieve their
email based on the username/domain combination.

This is the easiest method I can think of doing large numbers of virtual domains
without using something clunky like sendmail's virtual user map files, ie. joe@domain1 
maps
to joe-domain1 on the local box.

Or if anyone has any better suggestions I'm all ears.

Thanks!

-Jason