9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Invalid RCPT TO r...
FromSent OnAttachments
Martin Schuster (IFKL IT OS DSM CD)Jan 16, 2008 4:30 am 
Marcus IlgnerJan 16, 2008 7:19 am 
Martin Schuster (IFKL IT OS DSM CD)Jan 16, 2008 7:29 am 
Jeff JansenJan 16, 2008 1:06 pm 
Martin Schuster (IFKL IT OS DSM CD)Jan 16, 2008 11:10 pm 
Bernd WurstJan 16, 2008 11:22 pm 
Martin Schuster (IFKL IT OS DSM CD)Jan 17, 2008 1:44 am 
Jeff JansenJan 17, 2008 7:54 pm 
Martin Schuster (IFKL IT OS DSM CD)Jan 23, 2008 3:49 am 
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] Invalid RCPT TO results in 513 Syntax errorActions...
From:Jeff Jansen (tech@sil.org)
Date:Jan 17, 2008 7:54:09 pm
List:net.sourceforge.lists.courier-users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

"Martin Schuster (IFKL IT OS DSM CD)" <Mart@infineon.com> wrote on 2008-Jan-17:

Currently my additional code looks like this

for (p=0, s=info->ptr; s; s=s->next) if (s->token == '@') p=s; if (p==0) { // no @ in address, we need to rewrite // let's find the last token for (s=info->ptr; s->next; s=s->next);

and now I need to alloc a new rfc822token, alloc a string with my defaultdomain, and fill the rfc822token with the right info. I guess. :)

First I would try simply commenting out the 2 calls to 'rfc822check' in 'rwrecip' in the "esmtp.c" file and see what happens. It looks to me like courier will do a user lookup on the bare name, which is what you want. I'll freely admit that I've only given this a cursory glance, but if it works, it saves you lots of trouble and if it doesn't then at least it didn't take long to try. :-)

iD8DBQFHkCL4GfIHDMaiC9cRAn4XAKCXDngoWb+lYA+B+R1hjncG9VB2FwCcCROi nEHbVEfg7rmaCG+BgbRKc1Q= =h5XX -----END PGP SIGNATURE-----