Qmail
[Top] [All Lists]

Re: Smtproutes & Local Mailboxes

To: qmail@list.cr.yp.to
Subject: Re: Smtproutes & Local Mailboxes
From: Kyle Wheeler <kyle-qmail@memoryhole.net>
Date: Fri, 25 May 2007 07:16:00 -0600
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
Dkim-signature: v=0.5; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=received:received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; q=dns/txt; s=default; bh=VTCi8GdojdJCM6Z++9uVvT3SOo4=; b=B4IywItmL4wbUSiv43doRroVxCa+317TXjFYFQH5nQqcgENVD6o7uacEULnAkKO+vA/HvSrCSkCcRrtXJ/rcm9uFt8Wrpi/8sRXHvLCLAEjkFH4kBvRKHhhednT2Xzy2cHfrKzXk1g+ogUzJeyYfRJs6ocy/PCewtZYOaNoBMyo=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=aTG5rdTw/L1ZTJiDHx8NmHQSPJAPyla/0Tyre5kBOGwSGDuFLzabQjsCIvTlbziWV1vUO5ElM0nT3619SpgZXDO554UuPyQ1wBibVYERg3TzJCZpuAkMuhIbScxR55RFGDyp9GUDAA1itZ1SlbwY6Gv+RiLbIFmaktoZLDMAxD4=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent;
Domainkey-status: good
In-reply-to: <465609AE020000D30000BF51@gwia1-lx.mvnhealth.com>
Mail-followup-to: qmail@list.cr.yp.to
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <465609AE020000D30000BF51@gwia1-lx.mvnhealth.com>
User-agent: Mutt/1.5.15 (2007-05-20)
On Thursday, May 24 at 09:54 PM, quoth Matthew Yette:
Thanks for getting back to me, Kyle.

No problem.

Your FROM address does not have to match anything. It can be entirely made up if you like (this is why phishing is possible).

The problem I bring up about the "fake", backup domain (something like, matt@example.backup) that lives on the filtering box, is that some mail servers will reject the sender if the sending domain doesn't actually exist (as example.backup doesn't), hence my desire to have the backup domain be the same as the real domain.

My point is, when you send mail from the backup server, the return address can be whatever you want, including the "real" domain (i.e. example.com). This will not affect qmail's routing of the message at all.

Is there a way to filter for a domain (example.com), and pass the messages along via smtproutes to that company's mail server, while also maintaining a copy of each message (via qmail-tap?) in a vpopmail domain of the same name (example.com) that lives local on that box, so that messages could still be sent from the web interface?

...what? What makes you think you *can't* do that already?

If a domain of the same name lives on the filter box, it won't honor the smtproutes entry, and it will just deliver the mail locally instead. I wish it would copy it to the mailbox on the local box via qmail-tap, AND honor smtproutes and forward it along.

Ummm, no.

smtproutes controls delivering messages that have a recipient in example.com, not messages that have a return address in example.com. So if you have, say, example.com in your smtproutes file, and you send a message with a return address of foo@example.com, that message will be delivered exactly the same way it would be if example.com was NOT in smtproutes (or any of qmail's other config files (except badmailfrom)). Unless you're doing some very weird filtering, the SENDER doesn't affect how mail is delivered to RECIPIENTS. The sender can be a domain in smtproutes, a domain in rcpthosts, a domain in virtualdomains, or a domain that isn't anywhere in qmail's config: the message will be delivered the same way and to the same place in all cases.

~Kyle
--
Never think that war, no matter how necessary, no matter how justified, is not a crime.
                                                   -- Ernest Hemingway

Attachment: pgpmW5FyNa7aq.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>