courier-imap and open-smtp
I'm using vpopmail-4.9.8 and courier-imap-1.3.2. The open-smtp relay feature works for pop connections but don't works for imap connections. When a user connect via imap /home/vpopmail/etc/open-smtp isn't updated with the user ip. What have I mistaken? Thanks Dario -- Delivered by qmail Powered by RH Linux 6.2 on HP LH6000
Re: courier-imap and open-smtp
I'm using vpopmail-4.9.8 and courier-imap-1.3.2. The open-smtp relay feature works for pop connections but don't works for imap connections. When a user connect via imap /home/vpopmail/etc/open-smtp isn't updated with the user ip. Are you sure you have authvchkpw in your /usr/local/libexec/courier-imap/authlib/ or equivalent directory? If you are using vpasswd.cdb database, you should remove everything from the AUTHMODULES line of your /usr/local/etc/courier-imap/imapd and leave just AUTHMODULES="authvchkpw" in it. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Upgrading
At 02:17 PM 2/7/2001 -0800, you wrote: In the real world, there is NO SUCH THING as upgrading. It basically removes/replaces your old files with the new ones. I'm afraid I must disagree. If there were no such thing as upgrading, then when I install a new version of a package (after removing the old, of course -- unless it is designed so that the two versions do not conflict with each other) all of the data created/managed/whatever by the old version would be lost (due to removal) and/or obsolete (due to different software installed). Any time the manufacturer of a product (software or hardware) alters the product to raise its quality (or extend its life) that is an upgrade by definition (check Webster's if you disagree). And in fact, it turns out that what I asked for *almost* exists already (in config.status). And now I'm going to suggest a minor improvement to configure that will hopefully make its way to people who might implement it: It would be great if (a) configure recorded the options used to build a package in a format it [configure] could reuse and (b) there were a command line option to tell configure to read those options from a specific file and/or directory. For example, instead of manually entering all of the options (and hoping they match what was used for the previous version) we could enter a command something like this: ./configure --use=../vpopmail-4.9/config.opt Then, any additional options could add (or replace) options from the old file. I doubt that this would be difficult to implement, especially for the kind of script guru that created configure in the first place. However, it could be of great benefit quite often. OK, 'nuf said.
Re: [Re: Upgrading]
I have to say that I think that would be a very nice feature. I would love to be able to upgrade vpopmail, or any of the other associated packages by using ./configure --enable-options=/vpopmail-4.9/config.opt or something to that effect. Just my 2 cents. Aaron Steve Valliere [EMAIL PROTECTED] wrote: At 02:17 PM 2/7/2001 -0800, you wrote: In the real world, there is NO SUCH THING as upgrading. It basically removes/replaces your old files with the new ones. I'm afraid I must disagree. If there were no such thing as upgrading, then when I install a new version of a package (after removing the old, of course -- unless it is designed so that the two versions do not conflict with each other) all of the data created/managed/whatever by the old version would be lost (due to removal) and/or obsolete (due to different software installed). Any time the manufacturer of a product (software or hardware) alters the product to raise its quality (or extend its life) that is an upgrade by definition (check Webster's if you disagree). And in fact, it turns out that what I asked for *almost* exists already (in config.status). And now I'm going to suggest a minor improvement to configure that will hopefully make its way to people who might implement it: It would be great if (a) configure recorded the options used to build a package in a format it [configure] could reuse and (b) there were a command line option to tell configure to read those options from a specific file and/or directory. For example, instead of manually entering all of the options (and hoping they match what was used for the previous version) we could enter a command something like this: ./configure --use=../vpopmail-4.9/config.opt Then, any additional options could add (or replace) options from the old file. I doubt that this would be difficult to implement, especially for the kind of script guru that created configure in the first place. However, it could be of great benefit quite often. OK, 'nuf said.
RE: Upgrading
PHP's configure script has something similiar. At the end of the configure it creates a config.nice script. So when you are upgrading you just have to run ../php-4.0.whatever/config.nice and it configures your new sources exactly like the old. Maybe this is a feature that is dependant on the version of config that the developers use. I haven't had the need to play with these packages for any of my projects yet. Joe -Original Message- From: Steve Valliere [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 08, 2001 7:28 AM To: [EMAIL PROTECTED] Subject: Re: Upgrading At 02:17 PM 2/7/2001 -0800, you wrote: In the real world, there is NO SUCH THING as upgrading. It basically removes/replaces your old files with the new ones. I'm afraid I must disagree. If there were no such thing as upgrading, then when I install a new version of a package (after removing the old, of course -- unless it is designed so that the two versions do not conflict with each other) all of the data created/managed/whatever by the old version would be lost (due to removal) and/or obsolete (due to different software installed). Any time the manufacturer of a product (software or hardware) alters the product to raise its quality (or extend its life) that is an upgrade by definition (check Webster's if you disagree). And in fact, it turns out that what I asked for *almost* exists already (in config.status). And now I'm going to suggest a minor improvement to configure that will hopefully make its way to people who might implement it: It would be great if (a) configure recorded the options used to build a package in a format it [configure] could reuse and (b) there were a command line option to tell configure to read those options from a specific file and/or directory. For example, instead of manually entering all of the options (and hoping they match what was used for the previous version) we could enter a command something like this: ./configure --use=../vpopmail-4.9/config.opt Then, any additional options could add (or replace) options from the old file. I doubt that this would be difficult to implement, especially for the kind of script guru that created configure in the first place. However, it could be of great benefit quite often. OK, 'nuf said.
qmailloganalyzer
Hi all, I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good logparsing I thought that I might be best of writing my own perl script which utilizes qmailanalog to its full extent. The Script takes a logfile with tai format converts it to tailocal to determine the correct date. Afterwards pipes it back through localtai to get it back back to the taiformat that qmailanalog needs. Then passes it through matchup and gzips all the files to a directory of your liking for archiving. Then it uses all these archived logfiles and pipes them through the various qmailanalog scripts zoverall, senders, etc. and outputs the result to a webdir of your liking. It saves the result in static html pages in a hierarchichal structure, so you get can view your results over the periods of time. command line options to the script are: b - basename this is the prefix of the lognames if you don't like qmail set it different (qmail-mmdd.gz is default) d - archive directory (defaults to ".") s - do you want to save the source logs (default is "no") t - pipe the logs through tailocal before parsing (default is "no") z - compression (look at the source code (sorry) defaults to standard .gz) m - path to qmailanalog binary files (defaults to /usr/local/qmailanalog/bin) o - outputdirectory (defaults to /var/www/maillog) You can see an example of the output at http://www.web-4-all.de/maillog AGAIN This is only for multilog. Please let me know if this software is useful to you and don't hesitate to contact me if you have any questions. I will post the script to the qmail mailing list later on, or maybe one of you guys can do it for me, since I am really busy at the moment. I will setup a website also which will be available via http://qmaillog.byteaction.de by the end of the month. Planned features include graphs, Column Totals where column totals ought to be. Any other feature requests? Ken feel free to distribute this with vpopmail if you want to. kind regards Juergen Hoffmann P.S. the qmailloganalyzer.css has to be copied to the root directory of your webserver for it to work. If you do not use it the results will look crabby. qmailloganalyzer.tar.gz
Re: qmailloganalyzer
Hi, thanx. multilog is a program that comes with the daemontools package. You can download it from http://www.qmail.org The best way on how to install it iat documented in my life with qmail. If you use daemontools already (supervise, svc, etc.) then you most likely just have to edit your logging options. kind regards Juergen Hoffmann - Original Message - From: [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Sent: Thursday, February 08, 2001 9:10 PM Subject: Re: qmailloganalyzer Hi! Looked at this. What is multilog? The page looks AWESOME and I think I wanna try it. =) Cheers, Tren. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - Tren Blackburn - Ownermailto:[EMAIL PROTECTED] = = End of Time Networks http://www.theendoftime.net - - (403) 269-2122 = =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- On Thu, 8 Feb 2001, [iso-8859-1] Jrgen Hoffmann wrote: Hi all, I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good logparsing I thought that I might be best of writing my own perl script which utilizes qmailanalog to its full extent. The Script takes a logfile with tai format converts it to tailocal to determine the correct date. Afterwards pipes it back through localtai to get it back back to the taiformat that qmailanalog needs. Then passes it through matchup and gzips all the files to a directory of your liking for archiving. Then it uses all these archived logfiles and pipes them through the various qmailanalog scripts zoverall, senders, etc. and outputs the result to a webdir of your liking. It saves the result in static html pages in a hierarchichal structure, so you get can view your results over the periods of time. command line options to the script are: b - basename this is the prefix of the lognames if you don't like qmail set it different (qmail-mmdd.gz is default) d - archive directory (defaults to ".") s - do you want to save the source logs (default is "no") t - pipe the logs through tailocal before parsing (default is "no") z - compression (look at the source code (sorry) defaults to standard .gz) m - path to qmailanalog binary files (defaults to /usr/local/qmailanalog/bin) o - outputdirectory (defaults to /var/www/maillog) You can see an example of the output at http://www.web-4-all.de/maillog AGAIN This is only for multilog. Please let me know if this software is useful to you and don't hesitate to contact me if you have any questions. I will post the script to the qmail mailing list later on, or maybe one of you guys can do it for me, since I am really busy at the moment. I will setup a website also which will be available via http://qmaillog.byteaction.de by the end of the month. Planned features include graphs, Column Totals where column totals ought to be. Any other feature requests? Ken feel free to distribute this with vpopmail if you want to. kind regards Juergen Hoffmann P.S. the qmailloganalyzer.css has to be copied to the root directory of your webserver for it to work. If you do not use it the results will look crabby.
qmailloganalyzer
Thursday February 08 2001 19:51, =?iso-8859-1?Q?J=FCrgen_Hoffmann?= wrote to All: iH This is a multi-part message in MIME format. iH Hi all, iH I know this might not be the right list, but since I am using iH multilog So why post this crap!? KS
RE: qmailloganalyzer
Because we all use qmail and most of us like a pretty useful way to view stats and logs. Don't flame the guy, I applaud him. I don't know how many times I have heard complaints about not having a good log analyzer that works with vpopmail, or even qmail at all for that matter. -Original Message- From: Kari Suomela [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 08, 2001 4:33 PM To: [EMAIL PROTECTED] Subject: qmailloganalyzer Thursday February 08 2001 19:51, =?iso-8859-1?Q?J=FCrgen_Hoffmann?= wrote to All: iH This is a multi-part message in MIME format. iH Hi all, iH I know this might not be the right list, but since I am using iH multilog So why post this crap!? KS
transfer of domain
I just had the DNS transferred over from a third party that was handling the mail. All that goes to our addresses doesn't get rejected but when we login there is no messages either. This is for both mail that is relayed remotely and locally. When I do qmail-qstat I get this: messages in queue: 110 messages in queue but not yet preprocessed: 0 I'm at a loss as to where the mail is going and how to get it to the right users.. Miles
Re: qmailloganalyzer
Hi, I will write a detailed README tomorrow. Plus I will add a -h flag to print out the usage of the script. kind regards Juergen Hoffmann - Original Message - From: "Shao Ming" [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Sent: Thursday, February 08, 2001 11:47 PM Subject: Re: qmailloganalyzer Hi! I want to give your package a try but can you attach some 'README' to help me get started? cheers! - Original Message - From: "Jrgen Hoffmann" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 09, 2001 4:46 AM Subject: Re: qmailloganalyzer Hi, thanx. multilog is a program that comes with the daemontools package. You can download it from http://www.qmail.org The best way on how to install it iat documented in my life with qmail. If you use daemontools already (supervise, svc, etc.) then you most likely just have to edit your logging options. kind regards Juergen Hoffmann - Original Message - From: [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Sent: Thursday, February 08, 2001 9:10 PM Subject: Re: qmailloganalyzer Hi! Looked at this. What is multilog? The page looks AWESOME and I think I wanna try it. =) Cheers, Tren. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - Tren Blackburn - Ownermailto:[EMAIL PROTECTED] = = End of Time Networks http://www.theendoftime.net - - (403) 269-2122 = =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- On Thu, 8 Feb 2001, [iso-8859-1] Jrgen Hoffmann wrote: Hi all, I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good logparsing I thought that I might be best of writing my own perl script which utilizes qmailanalog to its full extent. The Script takes a logfile with tai format converts it to tailocal to determine the correct date. Afterwards pipes it back through localtai to get it back back to the taiformat that qmailanalog needs. Then passes it through matchup and gzips all the files to a directory of your liking for archiving. Then it uses all these archived logfiles and pipes them through the various qmailanalog scripts zoverall, senders, etc. and outputs the result to a webdir of your liking. It saves the result in static html pages in a hierarchichal structure, so you get can view your results over the periods of time. command line options to the script are: b - basename this is the prefix of the lognames if you don't like qmail set it different (qmail-mmdd.gz is default) d - archive directory (defaults to ".") s - do you want to save the source logs (default is "no") t - pipe the logs through tailocal before parsing (default is "no") z - compression (look at the source code (sorry) defaults to standard .gz) m - path to qmailanalog binary files (defaults to /usr/local/qmailanalog/bin) o - outputdirectory (defaults to /var/www/maillog) You can see an example of the output at http://www.web-4-all.de/maillog AGAIN This is only for multilog. Please let me know if this software is useful to you and don't hesitate to contact me if you have any questions. I will post the script to the qmail mailing list later on, or maybe one of you guys can do it for me, since I am really busy at the moment. I will setup a website also which will be available via http://qmaillog.byteaction.de by the end of the month. Planned features include graphs, Column Totals where column totals ought to be. Any other feature requests? Ken feel free to distribute this with vpopmail if you want to. kind regards Juergen Hoffmann P.S. the qmailloganalyzer.css has to be copied to the root directory of your webserver for it to work. If you do not use it the results will look crabby.
Re: qmailloganalyzer
I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good logparsing I thought that I might be best of writing my own perl script which utilizes qmailanalog to its full extent. Interesting that this has come up as its something ive been trying to do for ages now, and given up. I have qmailanalog installed, multilog doing the logging, and vpopmail. Imtrying to get a good log analysis program working, but all my logfiles are in the form @timestamp.s like @40003a6b6eac32a52fe4.s and no log analyser seems to be able to decode them or make any sense, but then again its possible im just not using them properly, any advice on this would be great!
Re: qmailloganalyzer
Hi, make sure that if you are using multilog that you pass the argument -t This is needed, because the logs timestamps are in tai format (e.g. @4003829some odd number) -t makes sure that these numbers are first converted to localtime Format So the Script can determine the day. The Script uses the command tailocal. If this is named tai64nlocal on your machine make a symlink or edit the code. after the script has determined the date of the logentry it pipes it through localtai, and converts it to a timestring that is suitable for qmailanalogs matchup. Besides by after converting it gets passed through matchup right away and is then packed into a gzipped archive. And by the way make sure that you submit the -s switch. There is a bug in the code close to unlink, which won't delete the old logfiles, but wil in future releases. The -s switch will make sure that the logs stay in place. After that you should be set. Hope that helps. Let me know. kind regards Juergen Hoffmann - Original Message - From: "Shao Ming" [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Sent: Friday, February 09, 2001 12:24 AM Subject: Re: qmailloganalyzer Hi! first of all, I did make another change to your script. The script cough out the following error sh: localtai: command not found so I make a change to line 74 $localtai = "./localtai"; I ran the script without any arguments. The system is Redhat Linux 6.2 and the perl version is as below ... # perl -v This is perl, version 5.005_03 built for i386-linux Copyright 1987-1999, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5.0 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. The scripts did create lots of qmail-xxx.gz logs around in the same directory. cheers! - Original Message - From: "Jrgen Hoffmann" [EMAIL PROTECTED] To: "Shao Ming" [EMAIL PROTECTED] Sent: Friday, February 09, 2001 7:07 AM Subject: Re: qmailloganalyzer Hi, what arguments did you give to the script? match writes out pending message on Dsecriptor five. I have not found a way to solve this. What Perl Version are you using? kind regards Juergen Hoffmann - Original Message - From: "Shao Ming" [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Sent: Friday, February 09, 2001 12:05 AM Subject: Re: qmailloganalyzer Here some error I have encountered in my initial run. Not enough arguments for mkdir at ./qmailloganalyzer.pl line 78, near "$outputdir }" Not enough arguments for mkdir at ./qmailloganalyzer.pl line 182, near ""$outputdir/$year" }" Not enough arguments for mkdir at ./qmailloganalyzer.pl line 183, near ""$outputdir/$year/$month" }" Not enough arguments for mkdir at ./qmailloganalyzer.pl line 184, near ""$outputdir/$year/$month/$day" }" Not enough arguments for mkdir at ./qmailloganalyzer.pl line 222, near ""$outputdir/$year" }" Not enough arguments for mkdir at ./qmailloganalyzer.pl line 223, near ""$output} so I append the MODE 0777 behind the parameter. Now it run but give me the following error ... matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open matchup: fatal: unable to write fd 5: file descriptor not open had to CTRL-C to get out of the endless loop Hope the above help ... cheers! - Original Message - From: "Jrgen Hoffmann" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, February 09, 2001 2:51 AM Subject: qmailloganalyzer Hi all, I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good
Re: qmailloganalyzer
Hi, you could of course use my loganalyzer which is still alpha but gives out good results. If u pipe your logfiles through tai64nlocal you wil get the standard date and fractional seconds behind that. Or is that the process id? I dont really remember. Anyways the usage for tai64local would be: tai64nlocal @214382hfdjhkl.s Your_parsed_log_with_dates.txt kind regards Juergen Hoffmann - Original Message - From: "Daniel Hardaker" [EMAIL PROTECTED] To: "Jrgen Hoffmann" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 09, 2001 12:22 AM Subject: Re: qmailloganalyzer I know this might not be the right list, but since I am using multilog with qmail + vpopmail and I could not find anything that would do good logparsing I thought that I might be best of writing my own perl script which utilizes qmailanalog to its full extent. Interesting that this has come up as its something ive been trying to do for ages now, and given up. I have qmailanalog installed, multilog doing the logging, and vpopmail. Imtrying to get a good log analysis program working, but all my logfiles are in the form @timestamp.s like @40003a6b6eac32a52fe4.s and no log analyser seems to be able to decode them or make any sense, but then again its possible im just not using them properly, any advice on this would be great!
user unknown....
Hi i've already installed qmail and vpopmail without problems. Also i'm using all domains as virtualdomains. My host is webmail.sicomnet.edu.mx and i added this host as a virtual domain using vadddomain webmail.sicomnet.edu.mx, and i can receive messages for all users under webmail.sicomnet.edu.mx (not for users in /etc/passwd, only for users in ~vpopmail/domains/webmail.sicomnet.edu.mx/passwd). Ialso created a virtualdomain vadddomain lozano2000.org.mx, i can send messanges usin g sqwebmail, but when i send a mail from another host it responde user unknown I don't know what is happening. Also i can config this virtual domain using qmailadmin. why my server can't receive mails for virtualdomains from other hosts? thanks in advance
RE: user unknown....
The reason you cannot receive mail for users on webmail.sicomnet.edu.mx is because there is no DNS record associated with this host of any kind. No A record and no MX record. The reason you cannot receive mail for lozano2000.org.mx is like that there is no MX record listed for that host. Fix your DNS and you should be able to receive mail. Aaron
Torture test Vpopmail + Qmail
Hello, I have set up Qmail + tcpserver + vpopmail on our RH 6.2 p3 box. We'd like to torture test it. Is there anything more than sending bulk email from a group mail software that we can do. Please give me suggestions as to how can we we continously hit the server with a lot of mails. Regards Sumith __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Re: virtual user quota
Correction, .current_size is generated the user's home directory by the "deliverquota" program that is also bundled with sam varschak's sqwebmail. It is not associated with vdelivermail (vpopmail's vdelivermail) as I earlier said. But an example of current user qutota usage is already incorporated in vpopmail's vdelivermail.c. It calculates the mail size before delivering a message to the user's Maildir. The part where it calculates the mail could be used as an example in the new program that would parse that information to STDOUT -- CGI -- custom html template code --- user's custom webmail. :D
