Re: [courier-users] Problem forwarding to other user account maildroprc or .mailfilter

2007-10-05 Thread Alessandro Vesely
M Core wrote:

 I think the question is - HOW do I CC or TO an email message to a
 different mail directory? I suspect this is the problem with TO
 /home/username/Maildir.
 (Note that TO or CC does work if it is in the user's directory that the
 email is being sent to e.g. TO $HOME/Maildir, or CCMaildir, or
 TOMaildir/.trash etc. these work.)

Did you check permissions? Your .mailfilter is executed on *delivery*
of a message, thus, in general, you shoudn't be able to do whatever
you want around the system. However, if you host *virtual* users, then
they all have the same courier uid/gid.












































-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] Greylisting with Courier-MTA on Debian

2007-10-05 Thread Georg Lutz
On 2007-09-24 07:44, Gordon Messmer wrote:

 The greylist filter included with pythonfilter is actually newer than 
 the one on Georg's site.  I incorporated most of his improvements, and 
 merged his secondary scripts into the filter.
 

Gordon is right. As the most greylisting functionality is now included
in pythonfilters standard distribution it should be preferred over my
original implementation. I have updated my website accordingly.

Concerning the statistics on effectiveness of greylisting: I think it
would be good to also have some measuring points in the greylist filter.

The interesting data would be 
 * how much messages/sender hit the greylisting filter
 * how much of them where discarded because of TTL 
 * how much of them get through

The data could be collected over periods of let say 24 hours and be
stored in another gdbm file. But I suppose that for this to work TtlDb
has to be tweaked. 

What do you think?

-- 
Georg

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] problem with esmtp(DNS lookup failure)

2007-10-05 Thread sergio
Hello courier-users,

  I know that my problem is very general problem.And I find many
  similar messages in list,but nslookup and dig work correct on my
  server,BUT in maillog I received

Oct  5 17:50:22 voyage courieresmtpd:
started,ip=[:::123.456.678.910(its just instead real IP)]
Oct  5 17:50:22 voyage courieresmtpd: EHLO neonet.ua
Oct  5 17:50:22 voyage courieresmtpd: MAIL FROM:[EMAIL PROTECTED] BODY=7BIT 
SIZE=949
Oct  5 17:50:22 voyage courieresmtpd:
error,relay=:::123.456.678.910,from=[EMAIL PROTECTED]: 417 DNS lookup 
failure: neonet.ua.  Try again later.

Can you help me?
-- 
Best regards,
Sergio Bortsov(Global Ukraine Lan ISP),  mailto:[EMAIL 
PROTECTED]
phones:+38(032)2987593;
   +38(098)4491155.



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] Problem with compiling courier-authlib-userdb

2007-10-05 Thread Aldisa Admin
Hello All,

I am trying to make courier-authlib on FreeBSD 6.2, using the FreeBSD ports 
system.

The courier-authlib-base package has compiled and installed successfully.  When 
I proceed with making the userdb code I get the following output:

===  Building for courier-authlib-userdb-0.60.0
gmake  all-recursive
gmake[1]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0'
Making all in libltdl
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libltdl'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libltdl'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libltdl'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libltdl'
Making all in bdbobj
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/bdbobj'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/bdbobj'
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/bdbobj'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/bdbobj'
Making all in md5
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/md5'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/md5'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/md5'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/md5'
Making all in sha1
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/sha1'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/sha1'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/sha1'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/sha1'
Making all in libhmac
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libhmac'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libhmac'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libhmac'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/libhmac'
Making all in numlib
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/numlib'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/numlib'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/numlib'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/numlib'
Making all in rfc822
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/rfc822'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/rfc822'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/rfc822'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/rfc822'
Making all in random128
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/random128'
gmake  all-am
gmake[3]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/random128'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/random128'
gmake[2]: Leaving directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0/random128'
gmake[2]: Entering directory 
`/usr/ports/databases/courier-authlib-userdb/work/courier-authlib-0.60.0'
/bin/sh ./libtool --tag=CC   --mode=link cc  -O2 -fno-strict-aliasing -pipe  
-Wall -I.. -I./.. -module -rpath /usr/local/lib/courier-authlib 
-export-symbols-regex 'courier_auth.*_init' -L/usr/local/lib -o 
libauthuserdb.la  authuserdb.lo preauthuserdb.lo preauthuserdbcommon.lo 
authuserdbpwd.lo libcourierauthcommon.la userdb/libuserdb.la 

Re: [courier-users] Problem with compiling courier-authlib-userdb

2007-10-05 Thread Milan Obuch
On Friday 05 October 2007, Aldisa Admin wrote:
 Hello All,

 I am trying to make courier-authlib on FreeBSD 6.2, using the FreeBSD ports
 system.

 The courier-authlib-base package has compiled and installed successfully. 
 When I proceed with making the userdb code I get the following output:


This is a bug in port. Actually I am just trying to understand it, hopefully 
someone (port maintainer is notified) will help to find the real issue.
There is a problem with subdirectories - subdirectory userdb is neither 
configured nor built.

If you do make configure followed with cd into userdb subdirectory, 
then ./configure and make, from main port's directory make - you are almost 
done. You could make install, but it is an awkward hack, even when it works.
Hopefully, this bug will soon be resolved.

Regards,
Milan

-- 
This address is used only for mailing list response.
Do not send any personal messages to it, use milan in
address instead.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] Setting up maildrop

2007-10-05 Thread M Core

--Forwarded Message Attachment--
From: [EMAIL PROTECTED]
To: courier-users@lists.sourceforge.net
Date: Fri, 5 Oct 2007 11:37:27 +0200
Subject: Re: [courier-users] Problem forwarding to other user account   
maildroprc or .mailfilter

M Core wrote:
 
 I think the question is - HOW do I CC or TO an email message to a
 different mail directory? I suspect this is the problem with TO
 /home/username/Maildir.
 (Note that TO or CC does work if it is in the user's directory that the
 email is being sent to e.g. TO $HOME/Maildir, or CCMaildir, or
 TOMaildir/.trash etc. these work.)
 
Did you check permissions? Your .mailfilter is executed on *delivery*
of a message, thus, in general, you shoudn't be able to do whatever
you want around the system. However, if you host *virtual* users, then
they all have the same courier uid/gid.

---

Well if I try to do the TO or CC that is sent to some other users directory so 
I guess that is what I'm getting at. How to get around those permissions?
I've seen examples on the web where people did that but never explained that 
they needed to do anything extra. 

My goal is to avoid the user having to redirect spam to me to file for 
learning. 
It would be nice to use maildroprc or .mailfilter to do a check for 'high 
scoring spam'
and send it to the spam-forsure user account. 


_
Show your pals how you really feel! Learn more today!
http://www.freemessengeremoticons.ca/-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users