The domain name is being added by qmail-send, which picks up messages from the 
queue and decides whether they're for local or remote delivery.  If the 
recipient address doesn't have a domain name, it will append the contents of 
the ENVNOATHOST environment variable.  If that variable isn't set, it will 
append the contents of /var/qmail/control/envnoathost.  If that file doesn't 
exist, it will append the contents of /var/qmail/control/me.  If that file 
doesn't exist, it will use the text "envnoathost".

You shouldn't mess with the contents of /var/qmail/control/me, since lots of 
pieces of qmail use that file.  But maybe you could create a zero-byte file 
named /var/qmail/control/envnoathost.  If there were nothing to append, 
hopefully qmail-send wouldn't tack on the unneeded "@" symbol.  It'd be worth a 
test.

If that doesn't work, the only other way to fix it would probably be to patch 
qmail. :(

-- Sam Clippinger




On Jul 10, 2012, at 1:29 AM, J. Kendzorra wrote:

> Hi folks,
> 
> even though this is Off Topic on this list, I thought I'd ask for your 
> opinions. Setup is as follows: Spamdyke -> qmail -> Sieve -> dovecot-lda
> This is problematic for bounces that are being forwarded, like:
> - Inbound email is from <> going to local user
> - local user has a rule which says "redirect all mail externally"
> - email being reinjected by Sieve using sendmail call and "-f <>" 
> command line parameter
> - that results in an email sent which has ""<>"@example.com" in the 
> Return-Path which is denied by the destination server
> So what I'm looking for is a way to re-inject a bounce without 
> qmail-inject adding domain from plusdomain/messing with the 
> Return-Path/From at all. Any thoughts?
> 
> Thanks,
> J.
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users

_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to