hi thanks for your reply
i am not an expert on this but here is what i feel if it was forwarding then it is logical that there will be atleast two "delivered-to" address and all information displayed in the headers but in case of aliasing the goal is collect all emails pertaining to several users in a single box and be able to download and distribute it locally. to ascertain further i chkd with three other email servers 1) hmailserver (opensource ) 2) mailenable (mailenable.com) 3)imail (ipswitch.com) all of them show only the aliased email (alias_to_user @ mydomain.com) id in the headers and there was absolutely no reference to the actual pop3 email id where the email has finally arrived in the headers. for vpopmail i did a work around -- i was able to carryout the above requirement by placing .qmail-alias_to_user file under the main mydomain.com directory and then the headers come correctly via ssh console but this is a manual operation and there is no facility in the qmailadmin web interface for this all comments welcome regds rajesh > [EMAIL PROTECTED] wrote: >> hello all, >> >> problem related to routing emails after downloading from an account >> >> we have 1 pop3 account and around 10 users to be aliased to it >> >> idea all emails get routed to this account and fetchmail downloads and >> distributes it. >> >> here comes the problem >> when i use the /home/vpopmail/bin/valias command line or use the forward >> feature in qmail admin >> >> then this is how i receive emails (please see header below) which is >> WRONG >> >> a) mailsent from : [EMAIL PROTECTED] >> b) now there are two delivered-to addresses in the headers >> Delivered-To: [EMAIL PROTECTED] >> Delivered-To: alias_to_user @ mydomain.com >> >> ################## >> Return-Path: <user @ externaldomain.com> >> Delivered-To: user @ mydomain.com >> Received: (qmail 29023 invoked by uid 89); 26 Nov 2008 11:55:28 -0000 >> Delivered-To: alias_to_user @ mydomain.com >> Received: (qmail 29018 invoked by uid 89); 26 Nov 2008 11:55:28 -0000 >> Received: by simscan 1.3.1 ppid: 29011, pid: 29015, t: 0.0671s >> scanners: attach: 1.3.1 spam: 3.2.5 >> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on >> >> ################## >> >> now when i download using fetchmail the mail delivery routing to >> alias_to_user @ mydomain.com >> which are pop users created on my Localarea network does not work >> >> Logically if i do aliasing then there shud be no mention of >> user @ mydomain.com in the messages headers at all >> >> (pl see header below) so that fetchmail can route the mail correctly to >> alias_to_user @ mydomain.com >> >> ################## >> Return-Path: <user @ externaldomain.com> >> Delivered-To: alias_to_user @ mydomain.com >> Received: (qmail 29018 invoked by uid 89); 26 Nov 2008 11:55:28 -0000 >> Received: by simscan 1.3.1 ppid: 29011, pid: 29015, t: 0.0671s >> scanners: attach: 1.3.1 spam: 3.2.5 >> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on >> ################## >> >> >> does anybody have the solution for this ? >> > > Those headers are correct. The headers are supposed to include every > transaction. If mail comes in for [EMAIL PROTECTED], but is aliased to > [EMAIL PROTECTED] it will show BOTH addresses, since it was originally > destined for [EMAIL PROTECTED], but was ALSO delivered to > [EMAIL PROTECTED] This is the correct and proper behavior. Headers are > meant to be as detailed as possible to troubleshoot issues. The header > would be no use if it only showed [EMAIL PROTECTED], since that user > doesn't really exist anyway. > The problem is in your fetchmail script or your mail sorting. I'm not > sure if fetchmail only checks the first delivered-to entry or if it can > scan for multiples since I do not use fetchmail that much/deeply. You > could write a mailfilter script or even a bash script to handle this > though. > > --------------------------------------------------------------------- > QmailToaster hosted by: VR Hosted <http://www.vr.org> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
