Hi Tod,
I found it with some semi-random googling.
I couldn't find your patch though.
Thanks for the patch I'm running it now. I'll use it for the time being
and perhaps I'll start using lookup tables in the future, which all
depends on whether or not the boss give me time to work on that.
Does anybody else see value in having dspam get an adresse and then
looking up the owner of that adresse? Interest and pointers would
motivate me to do this on my own time.
respects,
David Salib
On Wed, 2007-28-02 at 18:25 -0600, Tod A. Sandman wrote:
> On Wed, Feb 28, 2007 at 05:18:48PM -0500, David S. Salib wrote:
> > Hello,
> >
> > I've got dspam working there's just one thing I can't get done. I would
> > like for dspam to strip the domain from the username. I've tried all
> > combinations of StripRcptDomain and ParseHeaders. Here are the
> > variations I have tried.
> >
>
> Where are you getting information regarding 'StripRcptDomain'?
>
> We use this option, but it required a patch:
>
> --- daemon.c.P1 2006-07-11 08:39:45.000000000 -0500
> +++ daemon.c 2006-07-11 08:46:22.854520000 -0500
> @@ -571,6 +571,15 @@
> goto GETCMD;
> }
>
> + /* Chop of @.* from the recipient */
> + if (_ds_match_attribute(agent_config, "StripRcptDomain", "on")) {
> + strtok(username, "@");
> + if (username[0] == 0 || username[0] == '-')
> + { daemon_reply(TTX, LMTP_BAD_CMD, "5.1.2", ERR_LMTP_BAD_RCPT);
> + goto GETCMD;
> + }
> + }
> +
> if (_ds_match_attribute(agent_config, "Broken", "case"))
> lc(username, username);
>
>
> I don't think the parse headers option is involved.
>
>
> Tod Sandman
> Sr. Systems Administrator
> Middleware Development & Integration
> Rice University
>
