Re: [exim] ACL and conditions

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Justin Koivisto
Datum:  
To: Wakko Warner
CC: exim-users
Betreff: Re: [exim] ACL and conditions
Wakko Warner wrote:
> Justin Koivisto wrote:
>
>>Now, in my exim4/mainlog, I get the following:
>>
>>rejected RCPT <justin@???>: Koivi.com email too big message.
>>
>>However, the bounced message from the sending server says:
>>
>>... while talking to mail.koivi.com.:
>>
>>>>>>>>DATA
>>
>><<< 550 unknown user
>>550 5.1.1 <justin@???>... User unknown
>><<< 503 valid RCPT command must precede DATA
>>
>>I was hoping that the message I defined would be there... How do I do that?
>
> Exim did not show the 5.1.1 message. You might want to try using the -bt
> and/or the -bv options of exim to test the address (Don't do this on the
> daemon)


OK, using -bt, I get this:

mail:~# exim4 -bt justin@???
R: system_aliases for koivi@???
R: userforward for koivi@???
R: procmail for koivi@???
R: maildrop for koivi@???
koivi@???
     <-- koivi@???
     <-- justin@???
   router = spamcheck_router, transport = spamcheck


So I try to send a large message, and I get this in my mainlog and
rejectlog files:

2004-10-01 15:39:09 H=mesabi1.rangenet.com (mesabi.rangenet.com)
[206.146.208.16] F=<justink@???> rejected RCPT
<justin@???>: KOIVI.COM: The largest message that will get through
here is 500K. Your message was 1313285.

So this part is working now. The bounced message still looks like:

    ----- Transcript of session follows -----
... while talking to mail.koivi.com.:


>>>>>> DATA


<<< 550 unknown user
550 5.1.1 <justin@???>... User unknown
<<< 503 valid RCPT command must precede DATA

Reporting-MTA: dns; mesabi.rangenet.com
Received-From-MTA: DNS; waf.rangenet.com
Arrival-Date: Fri, 1 Oct 2004 15:35:56 -0500

Final-Recipient: RFC822; justin@???
Action: failed
Status: 5.1.1
Remote-MTA: DNS; mail.koivi.com
Diagnostic-Code: SMTP; 550 unknown user
Last-Attempt-Date: Fri, 1 Oct 2004 15:36:21 -0500

Any insight as to what exactly is going on here? justin is NOT a local
user on the system, and this router is *before* the vdom_aliases one
that maps it to the correct username.

--
Justin Koivisto