Re: [courier-users] rpm weirdness
On 07 Oct 2003 17:03:01 -0700 Stephen Arnold wrote: My rpm command line is: rpm -ba --define 'xflags --enable-https --enable-workarounds-for-imap-client-bugs' courier.spec Now, I read the INSTALL doc and other stuff, and it did say that make check would fail with the above options, and to do the check part first without the options, then configure again and build with these options. How does this help when building rpms? It seems to me it's impossible to build an rpm (with the above options) if make check always fails. What is the work-around I'm missing? I don't remember what I did last time (on the other machine) but I didn't run into this issue. Can somebody please enlighten me? If you want to build RPMs with --enable-workarounds-for-imap-client-bugs then you have to edit the spec file and remove the make check line. There's nothing else to do. -- Anand Buddhdev --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] rpm weirdness
On Wednesday 08 October 2003 00:03, Stephen Arnold wrote: I've been having trouble building courier rpms on RedHat 7.3 (which worked fine on another machine a few months ago). On this machine, I started with the latest source package (0.43.2) which had rpm build errors. Sam put out a patch so that 0.43.2 would compile under RH 7.3. I'll forward it to you off the list. rpm -ba --define 'xflags --enable-https --enable-workarounds-for-imap-client-bugs' courier.spec I thought that the imap-client-bugs option was for some old Netscape bugs. I haven't enabled it in over a year (I think) and we don't have any trouble with any of the clients we use (Outlook, OE, Kmail, Mozilla). I'm curious to know if it's still needed in some situations. Jeff Jansen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Virtual Domains problem (I think)
Thanks to Matthew Wilsson and Jeff something that helped me with my previous question. It solved the problem, but a new one came up. When starting the program (outlook express) I think my accounts gets their server setting changed. My settings is IMAP-server=mail.mydomain.com, Username=username%mydomain.com. I have virtual domain thats why I need the domain-name with the username. I'm not sure about this but I think the antivirus program is doing this. When I'm restarting the program my accounts gets server=127.0.0.1, [EMAIL PROTECTED] It worked properly before I restarted the program, and if I change the settings again it works but again the settings are changed when restarting. What do you think? /J Lindroos _ Hotmail snakker ditt språk! http://www.hotmail.msn.com/cgi-bin/sbox?rru=dasp/lang.asp - Få Hotmail på norsk i dag --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] HELP: Authentication Failure
Hello, I am trying to setup a simple system with Redhat 8.0. I have installed Qmail successfully. Now I am trying to install Courier-Imap (courier-imap-2.1.2.20031005) in usr/lib. I did everything as they say on the site http://www.inter7.com/courierimap/courierimap.html But 2 problems, 1. Authentication Failure (I need to use authpwd for authentication, but some how it does not appear when I try authlib/authinfo) (Is it something to do with imap_plain? ) 2. How to tell courier_imap that the mail folder is $HOME/Maildir/ ? Any help will be greatly appreciated. This is an emergency. I need to get this running ASAP. Thanks in advance, Suhas SOME MORE DETAILS: 1. Redhat 8.0 2. QMAIL 3. Trying to connect Mozilla Mail Client and MS Outlook Express
[courier-users] Re: HELP: Authentication Failure
Suhas Pharkute writes: But 2 problems, 1. Authentication Failure (I need to use authpwd for authentication, but Are you sure that your passwords are in /etc/passwd, and not /etc/shadow? some how it does not appear when I try authlib/authinfo) authdaemon is now installed by default, so look in authdaemonrc. (Is it something to do with imap_plain? ) 2. How to tell courier_imap that the mail folder is $HOME/Maildir/ ? That's the default setting. pgp0.pgp Description: PGP signature
[courier-users] Full courier Howto
On Thu, 02 Oct 2003 21:17:37 +1000, you wrote: Would anyone be interested in co-writting a full courier-only Howto similar in scope to this article ? If you do something like that please focus on things that are not written [clearly enough] in the documentation. This could include detailed explanations on setting up mailing lists with virtual mysql-user accounts and mailman and detailed instructions for amavisd-new, clamav and spamassassin or similar (free, of course) antispam-/antivir combos. Especially the last point should be made somehow easier for new mailadmins (or people that DO have a fulltime job and must do all that server stuff in the evenings... ;() Also I vote for Debian as a base system with a hint on backports.org to state clearly, where people can get new, working packages... I am certainly not skilled enough to act as a co-author but could give comments from a dumbo-user point of view like following this article does not work for me because blabla... Have a nice thread, Peter --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Full courier Howto
On Wed, 2003-10-08 at 22:40, Peter Holm wrote: On Thu, 02 Oct 2003 21:17:37 +1000, you wrote: Would anyone be interested in co-writting a full courier-only Howto similar in scope to this article ? If you do something like that please focus on things that are not written [clearly enough] in the documentation. This could include detailed explanations on setting up mailing lists with virtual mysql-user accounts and mailman and detailed instructions for amavisd-new, clamav and spamassassin or similar (free, of course) antispam-/antivir combos. I only have a minimal subset of experience with mysql, and virtual hosting in general, so a lot of the really interesting anti-virus material I'd have to leave to someone else anyway. Especially the last point should be made somehow easier for new mailadmins (or people that DO have a fulltime job and must do all that server stuff in the evenings... ;() Some docs for the rest of us would be great. Also I vote for Debian as a base system with a hint on backports.org to state clearly, where people can get new, working packages... I agree with that but RH packages and from-source are also popular. I am certainly not skilled enough to act as a co-author but could give comments from a dumbo-user point of view like following this article does not work for me because blabla... Hey, you might surprise yourself :) I think the best way forward all around is to have a Wiki and let's see what happens... http://courier.opensrc.org Nothing there yet... everyone/anyone, please just paste notes or comments any which way and the RecentChanges junkies will take care of the rest and refactor it into something half sensible. --markc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Virtual Domains problem (I think)
On Wednesday 08 October 2003 11:50, Jörgen Lindroos wrote: I'm not sure about this but I think the antivirus program is doing this. When I'm restarting the program my accounts gets server=127.0.0.1, [EMAIL PROTECTED] Norton Anti-virus and maybe others do this. They redirect the login to their scanning daemon and it in turns downloads the mail from the server and scans it before passing it to your mail client. But as far I know it only works for POP accounts, not IMAP. Go into your anti-virus software and turn off Incoming Email Checking. Of course, then you really need to have anti-virus email scanning on the server if you're not going to be running it on your workstation. Jeff Jansen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] How can I test Maildrop?
Hi,
I have to set local mail fitering rules for several users and I have
thought it to be a simple job with maildrop. What I did is:
1. in /etc/courier/courierd I have set
DEFAULTDELIVERY=| /usr/local/courier/bin/maildrop
where
MAILDROPDEFAULT=./Maildir
/etc/courier/maildrop consists of:
/usr/local/courier/bin/maildrop
2. in test user's home I have created .mailfilter file with 0600
permission consisting of:
VERBOSE=9
logfile filter.log
log mailfilter started
if (/^From: [EMAIL PROTECTED]/)
{
cc !root
}
All mail users are virtual users stored in mysql database.
Now if I understand it correctly, this test mailfilter should write to
$HOME/filter.log message mailfilter started and if the sender is
[EMAIL PROTECTED], then also send a copy of this mail to root.
However, it looks as if courier ignores this file - nothing is logged,
no mail comes to root and no error is logged. Actually /var/log/mail.log
states successfull delivery.
How can I check if the mail is really delivered via maildrop and what
files it tries to parse? I have even tried to install global filter (in
/etc/courier/maildroprc) - without success as well.:(
Could anyone help me, plz?
David.
System: Debian Woody
Courier: 0.40.1 (complete suite)
ps -A | grep courier
13039 ?00:00:00 courierfilter
13041 ?00:00:00 courierlogger
13058 ?00:00:00 courierd
13065 ?00:00:00 couriertcpd
13067 ?00:00:00 courierd
13068 ?00:00:00 courierlocal
13070 ?00:00:00 courierlogger
13076 ?00:00:00 courieresmtp
13077 ?00:00:00 couriertcpd
13078 ?00:00:00 courierdsn
13085 ?00:00:00 courierlogger
13087 ?00:00:00 couriertcpd
13090 ?00:00:00 courierlogger
13373 ?00:00:00 courieresmtpd
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How can I test Maildrop?
David Bruha wrote:
Hi,
I have to set local mail fitering rules for several users and I have
thought it to be a simple job with maildrop. What I did is:
1. in /etc/courier/courierd I have set
DEFAULTDELIVERY=| /usr/local/courier/bin/maildrop
where
MAILDROPDEFAULT=./Maildir
/etc/courier/maildrop consists of:
/usr/local/courier/bin/maildrop
2. in test user's home I have created .mailfilter file with 0600
permission consisting of:
VERBOSE=9
logfile filter.log
log mailfilter started
if (/^From: [EMAIL PROTECTED]/)
{
cc !root
}
All mail users are virtual users stored in mysql database.
fyi if you have maildir set in mysql it will ignore DEFAULTDELIVERY
Now if I understand it correctly, this test mailfilter should write to
$HOME/filter.log message mailfilter started and if the sender is
[EMAIL PROTECTED], then also send a copy of this mail to root.
However, it looks as if courier ignores this file - nothing is logged,
no mail comes to root and no error is logged. Actually
/var/log/mail.log states successfull delivery.
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Full courier Howto
On Wed, 08 Oct 2003 23:31:41 +1000, you wrote: http://courier.opensrc.org GREAT! Finally a courier-wiki! I was waiting for this a long time and hope all the readers here will paste their courier-notes... ;) Is there a syntax-howto for that wiki? Have a nice thread, Peter --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How can I test Maildrop?
David Bruha wrote: All mail users are virtual users stored in mysql database. Now if I understand it correctly, this test mailfilter should write to $HOME/filter.log message mailfilter started and if the sender is [EMAIL PROTECTED], then also send a copy of this mail to root. However, it looks as if courier ignores this file If your user database specifies a mailbox, then DEFAULTDELIVERY is not used. You should specify only a home directory in the user database, and make sure there is a Maildir inside each user's home directory. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] courier and smtp-auth
I've courier installed with: /etc/courier/locals localhost localhost.localdomain mydomain.com /etc/courier/me mydomain.com /etc/courier/esmtpd AUTHMODULES=authdaemon ESMTPAUTH=LOGIN /etc/courier/smtpaccess/default 127.0.0.1 allow,RELAYCLIENT makesmtpaccess I've tested the installation and I can't send mail from my server to another domain without auth login (that's right). But anyone can telnet to my 25 port, say that's a user of my domain and, without auth login, send mail to another user of my domain. Is this a normal behaviour?? ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Full courier Howto
I contributed a basic install with virtual users using mysql to the BLFS project. Here are the links. http://lfs.oregonstate.edu/blfs/view/cvs/server/courier.html This is before it was incorporated into BLFS http://lfs.oregonstate.edu/hints/downloads/files/OLD/courier.txt - Original Message - From: Mark Constable [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 6:31 AM Subject: Re: [courier-users] Full courier Howto On Wed, 2003-10-08 at 22:40, Peter Holm wrote: On Thu, 02 Oct 2003 21:17:37 +1000, you wrote: Would anyone be interested in co-writting a full courier-only Howto similar in scope to this article ? If you do something like that please focus on things that are not written [clearly enough] in the documentation. This could include detailed explanations on setting up mailing lists with virtual mysql-user accounts and mailman and detailed instructions for amavisd-new, clamav and spamassassin or similar (free, of course) antispam-/antivir combos. I only have a minimal subset of experience with mysql, and virtual hosting in general, so a lot of the really interesting anti-virus material I'd have to leave to someone else anyway. Especially the last point should be made somehow easier for new mailadmins (or people that DO have a fulltime job and must do all that server stuff in the evenings... ;() Some docs for the rest of us would be great. Also I vote for Debian as a base system with a hint on backports.org to state clearly, where people can get new, working packages... I agree with that but RH packages and from-source are also popular. I am certainly not skilled enough to act as a co-author but could give comments from a dumbo-user point of view like following this article does not work for me because blabla... Hey, you might surprise yourself :) I think the best way forward all around is to have a Wiki and let's see what happens... http://courier.opensrc.org Nothing there yet... everyone/anyone, please just paste notes or comments any which way and the RecentChanges junkies will take care of the rest and refactor it into something half sensible. --markc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Full courier Howto
On Wed, 8 Oct 2003, Peter Holm wrote: On Wed, 08 Oct 2003 23:31:41 +1000, you wrote: http://courier.opensrc.org GREAT! Finally a courier-wiki! I was waiting for this a long time and hope all the readers here will paste their courier-notes... ;) Is there a syntax-howto for that wiki? Yay! I have the feeling that this has the potential for making the docs and HOWTOs of courier more complete and accurate. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson [EMAIL PROTECTED] C and Python Code Gardener --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Full courier Howto
Everyone who has a particular favorite OS (or the only one they have ever used) keeps wanting detailed notes on how to use a particular package as a working example 1) Although people who build from packages MAY need more help than others, it doesn't seem to be in couriers best interest to start documenting a preferred platform. 2) From what I've seen over the years (started with RH, Mandrake moved to OpenBSD, FreeBSD and have tried debian, Solaris, AIX, etc. etc.) MANY problems are caused by people not knowing what they are doing trying to follow a process which by it's nature is dependant on lots of other packages which may themselves be broken, incompatible or themselves dependant on other broken packages. If documentation has to reference a single method, going from source is the only way that makes sense ot the entire community... Sam has a lot of good material - if there are holes, or things that are unclear, the time might be better spent improving what we have to start with and ensuring it survives as a living document instead of sidestepping it and allowing it to slide. My 2 cents. m/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Constable Sent: Wednesday, October 08, 2003 6:32 AM To: [EMAIL PROTECTED] Subject: Re: [courier-users] Full courier Howto On Wed, 2003-10-08 at 22:40, Peter Holm wrote: On Thu, 02 Oct 2003 21:17:37 +1000, you wrote: Would anyone be interested in co-writting a full courier-only Howto similar in scope to this article ? If you do something like that please focus on things that are not written [clearly enough] in the documentation. This could include detailed explanations on setting up mailing lists with virtual mysql-user accounts and mailman and detailed instructions for amavisd-new, clamav and spamassassin or similar (free, of course) antispam-/antivir combos. I only have a minimal subset of experience with mysql, and virtual hosting in general, so a lot of the really interesting anti-virus material I'd have to leave to someone else anyway. Especially the last point should be made somehow easier for new mailadmins (or people that DO have a fulltime job and must do all that server stuff in the evenings... ;() Some docs for the rest of us would be great. Also I vote for Debian as a base system with a hint on backports.org to state clearly, where people can get new, working packages... I agree with that but RH packages and from-source are also popular. I am certainly not skilled enough to act as a co-author but could give comments from a dumbo-user point of view like following this article does not work for me because blabla... Hey, you might surprise yourself :) I think the best way forward all around is to have a Wiki and let's see what happens... http://courier.opensrc.org Nothing there yet... everyone/anyone, please just paste notes or comments any which way and the RecentChanges junkies will take care of the rest and refactor it into something half sensible. --markc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: courier and smtp-auth
Dario Alonso writes: I've courier installed with: /etc/courier/locals localhost localhost.localdomain mydomain.com /etc/courier/me mydomain.com /etc/courier/esmtpd AUTHMODULES=authdaemon ESMTPAUTH=LOGIN /etc/courier/smtpaccess/default 127.0.0.1 allow,RELAYCLIENT makesmtpaccess I've tested the installation and I can't send mail from my server to another domain without auth login (that's right). But anyone can telnet to my 25 port, say that's a user of my domain and, without auth login, send mail to another user of my domain. Is this a normal behaviour?? If you connect to your server's external IP address, then courier will see your connection from some IP other than 127.0.0.1, and not allow relay. Make sure that you connect to 127.0.0.1 and then try to relay, and it will work. -- Anand --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How can I test Maildrop?
V St, 08. 10. 2003 v 17:30, Gordon Messmer pe: David Bruha wrote: All mail users are virtual users stored in mysql database. Now if I understand it correctly, this test mailfilter should write to $HOME/filter.log message mailfilter started and if the sender is [EMAIL PROTECTED], then also send a copy of this mail to root. However, it looks as if courier ignores this file If your user database specifies a mailbox, then DEFAULTDELIVERY is not used. You should specify only a home directory in the user database, and make sure there is a Maildir inside each user's home directory. Ah, I see. Isn't there a way how to put a piece of code into the maildir field in the database so the maildrop will be initiated? Because I have: - maildirs in /var/mail/domain/.users_maildir - homes in /home/domain and would like to keep them separated. FYI /var/mail is on it's own partition. David --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] rpm weirdness
On Wed, 2003-10-08 at 01:23, Jeff Jansen wrote: On Wednesday 08 October 2003 00:03, Stephen Arnold wrote: I've been having trouble building courier rpms on RedHat 7.3 (which worked fine on another machine a few months ago). On this machine, I started with the latest source package (0.43.2) which had rpm build errors. Sam put out a patch so that 0.43.2 would compile under RH 7.3. I'll forward it to you off the list. rpm -ba --define 'xflags --enable-https --enable-workarounds-for-imap-client-bugs' courier.spec I applied the patch, which fixed the maildrop error, and now there's a more informative error in imapd: Making check in imap make[1]: Entering directory `/home/sarnold/rpm/BUILD/courier-0.43.2/imap' Error: --with-trashquota or the --enable-workarounds-for-imap-client-bugs option was specified to the configure script. As INSTALL told you, make check fails if these options are used, and I wasn't kidding when I wrote it. Reconfigure and rebuild without these options, then rerun make and make check. If make check passes, reconfigure again with your original options, and proceed with installing this server. Have fun! make[1]: *** [check] Error 1 make[1]: Leaving directory `/home/sarnold/rpm/BUILD/courier-0.43.2/imap' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.58244 (%build) Looks like the rpms need at least one more patch, and no, I don't think it's appropriate to have to comment out the make check in the spec file just to build rpms correctly. Rpm should be able to handle it, ie, run the make check without the additional configure options, then build the rpms with the options enabled (and no, I don't have the time to fix it myself right now). The part I don't get is why 0.42.2 built fine on another RH 7.3 machine just a few months ago... Thanks, Steve -- Stephen Arnold [EMAIL PROTECTED] ENSCO, Inc. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How can I test Maildrop?
David Bruha wrote: V St, 08. 10. 2003 v 17:30, Gordon Messmer pe: David Bruha wrote: All mail users are virtual users stored in mysql database. Now if I understand it correctly, this test mailfilter should write to $HOME/filter.log message mailfilter started and if the sender is [EMAIL PROTECTED], then also send a copy of this mail to root. However, it looks as if courier ignores this file If your user database specifies a mailbox, then DEFAULTDELIVERY is not used. You should specify only a home directory in the user database, and make sure there is a Maildir inside each user's home directory. Ah, I see. Isn't there a way how to put a piece of code into the maildir field in the database so the maildrop will be initiated? Because I have: - maildirs in /var/mail/domain/.users_maildir - homes in /home/domain and would like to keep them separated. FYI /var/mail is on it's own partition. You can create a symlink from Maildir in the users' home directory to the maildir that's in /var/mail. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Mail Queue Time
Hello, I was wondering if anyone knows which file it is that sents the time that messages are held in the queue. I would like it messages kept in the queue for 1 day and anything past that delete it or send a message back giving an error. I currently have messages in the queue for about 5 days. Any help will be greatly appreciated. Thanks Jason B --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] bofhbadmime=accept pre/contra
On 07 Oct Ben Kennedy wrote: I can't see any issue of safety, unless you don't trust your mail client. (Bet you're an Outlook user, eh?) =-=-=-part of orig msg-=-=-= Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.3.28i From: dick hoogendijk [EMAIL PROTECTED] X-Spam-Score: -2.5 (--) Subject: [courier-users] bofhbadmime=accept pre/contra =-=-=- Can't see the outlook sign in this, can you? The reason I asked the Q is that lots of people on the courier list disencourage the bofhbadmime=accept Reason seems to be security _plus_ a standard that needs to be met ;) -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Re: bofhbadmime=accept pre/contra
On 07 Oct Sam Varshavchik wrote: The invalid MIME coding may cause a problem with the IMAP mail client. Or, it may not. You'll have to experiment to find out for yourself. OK, we use the courier imap too, so I guess it'll be wiser to leave things as they are? -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Mail Queue Time
On Wednesday 08 October 2003 16:55, [EMAIL PROTECTED] wrote: Hello, I was wondering if anyone knows which file it is that sents the time that messages are held in the queue. I would like it messages kept in the queue for 1 day and anything past that delete it or send a message back giving an error. I currently have messages in the queue for about 5 days. Any help will be greatly appreciated. The short answer is to put 1d into /etc/courier/queuetime (or /usr/lib/courier/etc/queuetime) to have messages returned as undeliverable after 1 day. Search for queuetime in the courier man page. The queuetime file in the courier etc directory controls how long messages stay in the queue. You might also want to look at warntime as well which is how long before the user gets a warning message that a message hasn't yet been sent. Jeff Jansen --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Re: bofhbadmime=accept pre/contra
Dick I think there is a standard... and a bit of FUD too... Most other mail systems I've seen ignore the problem... courier follows the standard and alters the mail which a sendmail or postfix system would accept by default (some people believe in a tollerant acceptance policy and a rigid sending policy)... I run a lot of accounts and have been pressured by users to make the switch. I have had no complaints as a result. I think old mail clients (like outlook 97 / netscape communicator 4, etc.) were crashing as a result of some badly formatted messages... they have seemingly fixed this though. good luck. m/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of dick hoogendijk Sent: Wednesday, October 08, 2003 10:15 AM To: courier-users Cc: courier-users Subject: Re: [courier-users] Re: bofhbadmime=accept pre/contra On 07 Oct Sam Varshavchik wrote: The invalid MIME coding may cause a problem with the IMAP mail client. Or, it may not. You'll have to experiment to find out for yourself. OK, we use the courier imap too, so I guess it'll be wiser to leave things as they are? -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IMAP Folder Structure
Thomas Smith wrote: I'm in the process of converting from Sendmail/Linuxconf/UW-IMAP to qmail/vpopmail/Courier-IMAP. In the process, I've noticed that Courier-IMAP handles the INBOX and subfolders a bit differently than UW-IMAP. In particular, all the folder I'm able to create and modify are stored under the INBOX. Some mail clients try like such things as Sent, Trash, Drafts, and so on, to be in the root of the IMAP connection--that is, at the same level as the INBOX rather than a subdirectory of it. I have the same problem if I try to create a folder manually, too. The error is: The current command did not succeed. The mail server responded: Invalid mailbox name. Otherwise, I'm able to do everything I need to as long as I do it within the INBOX directory structure. Can Courier-IMAP be configured to allow folders to be created at the same level as the INBOX? I think this is what you are looking for http://www.inter7.com/courierimap/FAQ.html#namespace This is a function of the IMAP client, look in the courier-imap docs on how to configure most clients. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] courier spamassassin
Hi, I've found that quite a few people are using this combination but couldn't find anything with spamassassin rules on a per user bases with virtual users. I'am using courier-mta with an ldap backend, is there anyone who has a similar setup working with spamassassin and rules per user without the need of .courier or .mailfilter files ? Thnx ! With kind regards, Tjeerd van der Zee
Re: [courier-users] Re: Proposing new functions for maildropfilter
what happens when you have 5 addresses going to ONE box? now you do it five filters when you only need to do one. it's a trade off, and the current way of doing it is the proper one, it gives you more control (if you have 5 destinations you have 5 users, which might very have different preferences) On Wed, 2003-10-08 at 13:03, Theo Cabrerizo Diem wrote: Hi all , Maybe a nice feature is to apply a filter to a message *before* alias expansion... for example .. : with spamassassin/clamav/amavis .. if I got an alias that delivers to 5 different addresses .. maybe it's better to filter just one time .. not 5 using maildrop when it reads the maildroprc file ... Sorry if this is already implemented .. but I didn't found any docs about this (and sorry .. didn't searched too much) []'s On Wed, 2003-10-01 at 23:32, Sam Varshavchik wrote: Eduardo Roldan writes: I think that the conditional functions (the ones you only use in the IF statement) proposed by [EMAIL PROTECTED] shold be in maildrop because in a tyipical filter these are evaluated each time a message is delivered. Define typical filter. To me a typical filter means: depending on the message's contents, deliver to this folder, or that folder. Or, perhaps, discard the message; or maybe forward it. These things can be accomplished entirely by the existing facilities in maildrop. When you start doing things like checking if an external file exists, creating or removing directories, I think you're getting beyond what a typical mail filter does. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier and smtp-auth
Dario Alonso wrote: /etc/courier/smtpaccess/default 127.0.0.1 allow,RELAYCLIENT ... I've tested the installation and I can't send mail from my server to another domain without auth login Is that a space or a tab in your smtpaccess file? --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Re: Proposing new functions for maildropfilter
Theo Cabrerizo Diem wrote: Maybe a nice feature is to apply a filter to a message *before* alias expansion... for example .. : with spamassassin/clamav/amavis .. if I got an alias that delivers to 5 different addresses .. maybe it's better to filter just one time .. not 5 using maildrop when it reads the maildroprc file ... You can do that using a courierfilter(8). --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier spamassassin
Tjeerd van der Zee wrote: Hi, I've found that quite a few people are using this combination but couldn't find anything with spamassassin rules on a per user bases with virtual users. I'am using courier-mta with an ldap backend, is there anyone who has a similar setup working with spamassassin and rules per user without the need of .courier or .mailfilter files ? Have a look at Bug 2205 in SpamAssassins Bugzilla. You'l find a patch adding LDAP-support to SpamAssassin so preferences can be retrieved on a per-user-base directly from LDAP. -- CU, Patrick. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IMAP Folder Structure
On Wed, 2003-10-08 at 10:20, Thomas Smith wrote: I'm in the process of converting from Sendmail/Linuxconf/UW-IMAP to qmail/vpopmail/Courier-IMAP. In the process, I've noticed that Courier-IMAP handles the INBOX and subfolders a bit differently than UW-IMAP. In particular, all the folder I'm able to create and modify are stored under the INBOX. Some mail clients try like such things as Sent, Trash, Drafts, and so on, to be in the root of the IMAP connection--that is, at the same level as the INBOX rather than a subdirectory of it. I have the same problem if I try to create a folder manually, too. The error is: The current command did not succeed. The mail server responded: Invalid mailbox name. Otherwise, I'm able to do everything I need to as long as I do it within the INBOX directory structure. Can Courier-IMAP be configured to allow folders to be created at the same level as the INBOX? IIRC, this is really a client issue. Courier follows the IMAP RFC, but client-land is a whole 'nother story. The way the namespaces are implemented on the client side is really what affects how you see the folders (ie, if the client is up to snuff, then you will see the folders correctly). HTH, Steve -- Stephen Arnold [EMAIL PROTECTED] ENSCO, Inc. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: courier and smtp-auth
If you connect to your server's external IP address, then courier will see your connection from some IP other than 127.0.0.1, and not allow relay. Make sure that you connect to 127.0.0.1 and then try to relay, and it will work. That's the problem. I connect to my server's external IP address, and courier leaves me relay from one account of my server to another account of my server. The steps I follow are these (hope this helps) # /etc/courier/esmtpd -- ESMTPDSTART=YES -- AUTHMODULES=authdaemon -- ESMTPAUTH=LOGIN /etc/courier/esmtpd-ssl -- ESMTPDSSLSTART=YES /etc/courier/aliases/system -- postmaster: user /etc/courier/locals -- localhost -- localhost.localdomain -- mydomain /etc/courier/me -- mydomain /etc/courier/smtpaccess/default -- 127.0.0.1 allow,RELAYCLIENT (this is a tab) /etc/courier/defaultdomain -- mydomain makesmtpaccess newaliases /etc/init.d/courier restart # I'm confused, because I think these are the steps I follow in another installations, and I haven't found never this problem. AFAIK. ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier and smtp-auth
Is that a space or a tab in your smtpaccess file? It's a tab ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] courier and smtp-auth
From: Dario Alonso [mailto:[EMAIL PROTECTED] I've courier installed with: /etc/courier/locals localhost localhost.localdomain mydomain.com /etc/courier/me mydomain.com /etc/courier/esmtpd AUTHMODULES=authdaemon ESMTPAUTH=LOGIN /etc/courier/smtpaccess/default 127.0.0.1 allow,RELAYCLIENT makesmtpaccess I've tested the installation and I can't send mail from my server to another domain without auth login (that's right). But anyone can telnet to my 25 port, say that's a user of my domain and, without auth login, send mail to another user of my domain. Is this a normal behaviour?? Unless I'm missing something in your description... Yes, that's normal behavior for an MTA. Anyone has to be able to send mail to your users, otherwise they can't receive email from the Internet. This is the way it should work: Anyone (authorized or otherwise) should be able to send mail to users of your domain. Authorized users, or users from an allowed IP block (RELAYCLIENT in smtpaccess) should be able to send mail anywhere. Bowie --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] courier and smtp-auth
Yes, anyone should be able to send mail to users in my domain, that's right... but the problem is with the jokers. i.e. one valid user, user1, want's to send a fake mail to user2. He could create one fake account (user3) from my domain in his MUA (evolution, kmail, etc...), and not use authentication for smtp. He could send without problems a mail from [EMAIL PROTECTED] to [EMAIL PROTECTED] That is what it seems to me. Can be avoided that? And he can still do that. Authentication doesn't set his From: header. All you've gained is a logged authentication to check it against. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] documentation bug in authpgsqlrc
Sam, authpgsqlrc says: ##NAME: PGSQL_SELECT_CLAUSE:0 # # (EXPERIMENTAL) # This is optional, PGSQL_SELECT_CLAUSE can be set when you have a # database, which is structuraly different from proposed. The fixed # string will be used to do a SELECT operation on database, which should # return fields in order specified bellow: # # username, cryptpw, uid, gid, clearpw, home, maildir, quota, fullname However, looking at the code, I see that clearpw should come before uid, like this: username, cryptpw, clearpw, uid, gid, home, maildir, quota, fullname Would you be so kind as to correct this in the next releases of courier, sqwebmail and courier-imap ? -- Anand Buddhdev --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: courier and smtp-auth
Dario Alonso writes: Yes, anyone should be able to send mail to users in my domain, that's right... but the problem is with the jokers. i.e. one valid user, user1, want's to send a fake mail to user2. He could create one fake account (user3) from my domain in his MUA (evolution, kmail, etc...), and not use authentication for smtp. He could send without problems a mail from [EMAIL PROTECTED] to [EMAIL PROTECTED] That is what it seems to me. Can be avoided that? Yes. Make sure that you're running identd on the server. Then: A) If the user sends mail using the sendmail command, the userid will be shown in the headers. B) If the user sends mail by connecting to port 25, using either 127.0.0.1, or your external IP address, the sender's userid will be provided by identd, and stamped in the headers of the mail. C) If the user connects from an external IP address that you've granted relaying privileges, you must then have logs that record who was using the IP address at the time. D) If the user connects from a foreign IP address, then this is no different than anyone else sending a message with randomly-generated From: header. As such, your recipient should simply be educated that anyone on the Internet can send E-mail, while pretending to be Santa Claus. pgp0.pgp Description: PGP signature
Re: [courier-users] Full courier Howto
Mark Constable wrote: [...] Hey, you might surprise yourself :) I think the best way forward all around is to have a Wiki and let's see what happens... http://courier.opensrc.org Nothing there yet... everyone/anyone, please just paste notes or comments any which way and the RecentChanges junkies will take care of the rest and refactor it into something half sensible. Hi all, since I've been quite unhappy with some aspects of courier-imap-documentation, especially if realted to LDAP, I already planned to setup a wiki about courier-imap, openldap, exim-ldap and spamassassin-ldap to document my own setup. I suppose at least part of my documentation could be included in your wiki, too. Which topics do you plan to cover? Strictly focused on courier-mta or open, so that using courier-imap standalone could be documented there? However, at least my documentation about exim-ldap and spamassassin-ldap would still be kept in my own wiki. -- CU, Patrick. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Complete List of [error] messages
Hi, I would like to have a list of all possible log-entries of courier and their meanings. is it possible to get a complete list of [error] messages that courier logs? I could read the sourcecode, I know, I am just asking if there might be someone who has a list... THANKS! Have a nice thread, Peter --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Re: Courier-IMAP 2.1.2 uses tons of bandwidth
--On Tuesday, October 07, 2003 8:37 AM -0400 Sam Varshavchik [EMAIL PROTECTED] wrote: Jeff Tucker writes: I haven't studied the code in great detail, but I don't see how the system will ever end up with the filename as a modern UIDL. Sam, what am I missing? Or what were you expecting that isn't here? My old 1.6 pop3dserver.c simply prints the filename for the UIDL. What do I need to do to make 2.1.2 do the same? Try the following patch. The upgrade logic may not be working correctly. Sam, Unfortunately, this still doesn't work. The patch seems to be entirely concerned with opening an older version of the courierpop3dsizelist file. It appears that if you opened one of these old files (was it just a filename and a size), then every message entry in the msglist gets 0 in the uid.n and uid.uidv. With my old version of Courier IMAP, this file doesn't exist. So, the readpop3dlist() returns with just a single, blank or null entry in the msglist as far as I can tell. When this happens, the system notices that there are files in the cur directory which don't appear in the msglist. This causes savepop3dlist() to be called, which writes out a new courierpop3dsizelist file with version 2 entries in it. From then on, if UIDL is called the version 2 entries cause the new-style UIDL to be printed. The only way an old-style UIDL (filename) will be printed is if the uid.n field in the msglist is zero. So, what I need is a msglist with all these current existing messages to have a uid.n of 0. The only way I can see that happening is if the system noticed that it was started with no courierpop3dsizelist file and created one using the special rule that uid.n was set to zero for all existing files. All new files can have an incrementing uid.n field. This might break other logic, though. I have a feeling that intermediate versions of Courier IMAP created earlier versions of the courierpop3dsizelist file, ones in which the uid.n wasn't printed out. Those versions printed the filename as the UIDL. When this version reads one of those old files, it gets 0 for the uid.n for every filename and saves that when writing out the new-style file. But this version of the software doesn't seem to be able to handle a missing courierpop3dsizelist file. What if I patched this version of the code to store 0 for the uid.n for every file. I could run that for a month or so, then undo the patch. That would work, wouldn't it? Jeff --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Courier-IMAP 2.1.2 uses tons of bandwidth
Jeff Tucker writes:
The only way an old-style UIDL (filename) will be printed is if the uid.n
field in the msglist is zero. So, what I need is a msglist with all these
current existing messages to have a uid.n of 0. The only way I can see that
happening is if the system noticed that it was started with no
courierpop3dsizelist file and created one using the special rule that uid.n
was set to zero for all existing files. All new files can have an
incrementing uid.n field. This might break other logic, though.
I don't think anything will break. Roll back the first patch, and try this
one, instead.
I have a feeling that intermediate versions of Courier IMAP created earlier
versions of the courierpop3dsizelist file, ones in which the uid.n wasn't
printed out. Those versions printed the filename as the UIDL. When this
version reads one of those old files, it gets 0 for the uid.n for every
filename and saves that when writing out the new-style file. But this
version of the software doesn't seem to be able to handle a missing
courierpop3dsizelist file.
Yup, I think this is the correct analysis.
pgp0.pgp
Description: PGP signature
diff -U3 -r1.25 pop3dserver.c
--- imap/pop3dserver.c 5 Oct 2003 04:47:50 - 1.25
+++ imap/pop3dserver.c 9 Oct 2003 02:04:57 -
@@ -105,6 +105,7 @@
static unsigned long retr_count=0;
static unsigned long uidv=0;
+static int convert_v0=0;
/*
** The RFC is pretty strict in stating that octet size must count the CR
@@ -161,12 +162,17 @@
uidv=time(NULL);
+ convert_v0=0;
+
if (fp == NULL ||
fgets(linebuf, sizeof(linebuf)-1, fp) == NULL ||
linebuf[0] != '/' || sscanf(linebuf+1, %d %lu %lu, vernum,
uid, uidv)
2 || (vernum != 1 vernum != 2))
{
+ if (fp == NULL)
+ convert_v0=1;
+
if (vernum == 0 fp fseek(fp, 0L, SEEK_SET) = 0)
{
/* Old version 0 format courierpop3dsizelist file */
@@ -453,6 +459,9 @@
msglist_a[i]-uid.n=nextuid++;
msglist_a[i]-uid.uidv=uidv;
msglist_a[i]-isnew=1;
+ if (convert_v0)
+ msglist_a[i]-uid.n=0;
+
calcsize(msglist_a[i]);
savesizes=1;
}
pgp1.pgp
Description: PGP signature
[courier-users] Rejection message format in log files: rejection due to DNS blacklist vs. due to custom courierfilter
Hi Sam, I'm currently experimenting with writing a custom courierfilter. It works fine, except for one thing. When mails get rejected due to the sending host being listed in a DNS blacklist (via the BLACKLISTS option in /etc/courier/esmtpd), I get log entries of this format: Oct 9 03:37:30 io courieresmtpd: error,relay=:::68.35.83.35,from=[EMAIL PROTECTED],to=[EMAIL PROTECTED] .net: 511 Blocked - see http://www.spamcop.net/bl.shtml?68.35.83.35 But when a mail gets rejected due to my custom filter, I get log entries of this format: Oct 9 03:59:00 io courieresmtpd: error,relay=:::217.88.243.27,from=[EMAIL PROTECTED]: 511 Just testing... The to=... part is missing. I need this because I parse the log files for rejection messages and create records in a PostgreSQL database, so my users can use a web front-end to look up whether mails directed to them have been rejected by the mail server. Without the to=... part, I'm unable to assign the rejection records to users. Why is the to=... part missing in rejection log messages caused by a courierfilter? --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Rejection message format in log files: rejection due to DNS blacklist vs. due to custom courierfilter
Julian Mehnle wrote: Why is the to=... part missing in rejection log messages caused by a courierfilter? Probably because the courierfilter runs after the message has been received, and there may have been several 'RCPT TO' commands. BLOCK causes failures for reach 'RCPT TO' command, when the 'RCPT TO' command is sent. Perhaps your courierfilter could insert the information into the SQL database itself. The cron job could search for the BLOCK-style failures and insert those into the database later. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Rejection message format in log files: rejection due to DNS blacklist vs. due to custom courierfilter
Julian Mehnle writes: /etc/courier/esmtpd), I get log entries of this format: Oct 9 03:37:30 io courieresmtpd: error,relay=:::68.35.83.35,from=[EMAIL PROTECTED],to=[EMAIL PROTECTED] .net: 511 Blocked - see http://www.spamcop.net/bl.shtml?68.35.83.35 But when a mail gets rejected due to my custom filter, I get log entries of this format: Oct 9 03:59:00 io courieresmtpd: error,relay=:::217.88.243.27,from=[EMAIL PROTECTED]: 511 Just testing... The to=... part is missing. This is because courierfilter runs after the message was received via DATA, and not in response to a RCPT TO. I need this because I parse the log files for rejection messages and create records in a PostgreSQL database, so my users can use a web front-end to look up whether mails directed to them have been rejected by the mail server. Without the to=... part, I'm unable to assign the rejection records to users. The only thing you could do is read the control file to obtain the recipient list of the original message (there may be more than one, and courierfilter is invoked once, no matter how many recipients the message has, and some of those recipients may be remote recipients) and include the recipients' addresses in your error message. pgp0.pgp Description: PGP signature
Re: [courier-users] Re: Courier-IMAP 2.1.2 uses tons of bandwidth
--On Wednesday, October 08, 2003 10:06 PM -0400 Sam Varshavchik [EMAIL PROTECTED] wrote: I don't think anything will break. Roll back the first patch, and try this one, instead. Thanks, Sam. The patch makes perfect sense, and it works. Jeff --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
