Another thing you might want to look at is your $HOST variable. Not sure where it comes into play in exim, but with my sendmail/procmail setup, in my .procmail/rc.tmda, I have:
#RECIPIENT="[EMAIL PROTECTED]" RECIPIENT="[EMAIL PROTECTED]" This affects a few headers. With the first line above, $HOST expands to froody.rupture.net. With the second, it's hardwired to rupture.net. ie: From: Jon Nathan <[EMAIL PROTECTED]> vs. From: Jon Nathan <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] From: Jon Nathan <[EMAIL PROTECTED]> Play around with it etc. -jon -- Jon Nathan [EMAIL PROTECTED] * Tim Legant <[EMAIL PROTECTED]> [10-23-2003 16:25]: > > Nils Vogels <[EMAIL PROTECTED]> writes: > > > For some reason, %(confirm_accept_address)s does not give me the right > > hostname, alltho I force it in the config above. > > The HOSTNAME variable is not used when generating the > confirm_accept_address. Instead, confirm_accept_address is based on > recipient_address. You can explicitly override this using the > CONFIRM_ADDRESS variable. > > http://tmda.net/[EMAIL PROTECTED] > > > My FQDN of the box is box1.example.org, and the > > %(confirm_accept_address)s just keeps on being in the form of > > [EMAIL PROTECTED], while the RCPT TO states > > [EMAIL PROTECTED] > > > > On thing that might be related, is that Postfix is doing > > virtual-domains, and the user that the email is being delivered to is > > locally known as [EMAIL PROTECTED] > > This is probably the problem. The recipient_address variable is > exactly what Postfix places in the RECIPIENT environment variable, > with no manipulation of any sort. If this is a problem that can't be > solved through Postfix, you can massage it in your config file like > this. > > rcptaddr = os.environ['RECIPIENT'] > try: > i = rcptaddr.rindex('@') > rcpt, host = rcptaddr[:i], rcptaddr[i+1:] > domain = '.'.join(host.split('.')[-2:]) > os.environ['RECIPIENT'] = rcpt + '@' + domain > except ValueError: > pass > > If the resulting recipient_address is what you want to have your > confirm_accept_address based on, then you don't need to worry about > the CONFIRM_ADDRESS setting mentioned above. > > > Tim > > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
