6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Dead again
FromSent OnAttachments
Daniel StormAug 1, 2002 8:17 am 
Sam VarshavchikAug 1, 2002 8:45 am 
Daniel StormAug 1, 2002 9:42 am 
Sam VarshavchikAug 1, 2002 10:16 am.txt
Daniel StormAug 1, 2002 12:42 pm 
Daniel StormAug 1, 2002 4:02 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: Dead againActions...
From:Daniel Storm (dan@verbena.demon.co.uk)
Date:Aug 1, 2002 4:02:38 pm
List:net.sourceforge.lists.courier-users

Randall,

I sure sure you're aware of the vpopmail patch which does exactly that.

I don't like patching source with something that won't get included in the tree as it means every release needs to be patched, so I often work around using shell scripts if at all possible (and its often possible).

The 'rather nasty' method I'm using with courier is a cron job run once a minute that takes the output of a command, generates a file in etc/smtpaccess/ and runs makesmtpaccess. Its not related to pop access.

If you wanted a shell based pop-before-smtp I guess you could do it by tailing the log file which logs pop and (this is really nasty but simplifies removal after a certain period and duplicate ip addresses) output a seperate file to etc/smtpaccess/ for each login then run makesmtpaccess. Then in a seperate 1/2hrly cron you can run a find to remove outdated files.

so something like this to create the files (which runs constantly and would need to be restarted after logfile rotation assumes logformat used by courier popd).

perl -e 'open M, "/var/log/maillog"; for (;;) { for (grep /pop3d.*LOGIN/, <M>) { m/([0-9\.]+)\]$/; open O, ">/usr/lib/courier/etc/smtpaccess/$1"; print O "$1\tallow,RELAYCLIENT\n"; close O; } system '/usr/lib/courier/sbin/makesmtpaccess'; sleep 5; seek(M,0,1); }'

and something like this to remove them (run from cron every thirty mins).

find /usr/lib/courier/etc/smtpaccess -cmin +30 | xargs rm

Hows that for a nasty workaround :). Pretty safe but still a very, nasty method. Of course you'll need the patch for coutiertcpd posted by Sam if your using a version of courier older than todays cvs (on solaris at least).

I tend to agree that the ways of opening up smtp access on courier are a little limited and an effect of that is probably relays more open than they have to be but then most desktop clients these days are capable of smtp authentication and most servers have a fixed IP address. The thing that annoys me more is the lack of compatible methods for securely logging in but I see that as a client issue.

dan

On Thu, 1 Aug 2002, Randall Shaw wrote:

I'm assuming by your post, that you are or have a sort of makeshift "pop-before-smtp" going on? One thing I wish Sam would build into courier.. but he refuses.

Just curious, as I have been tryingto figure out a good clean 'safe' way to handle doing a hack myself, and am open to hearing how other people are attempting it.