Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Qmail: users

Forward Email by address

 

 

Qmail users RSS feed   Index | Next | Previous | View Threaded


jmoore at moorekin

Feb 10, 2010, 11:38 AM

Post #1 of 12 (2966 views)
Permalink
Forward Email by address

Is it possible to forward email based on email address and not the entire
domain. We are implementing Zimbra internally but still want qmail to be
the email "gateway" for virus and spam scanning. I would like to migrate
each user over to the new zimbra server one at a time. So, can I forward
jmoore [at] betaclub to the new zimbra server and still have
kcline [at] betaclub delivered locally?



Thanks!


kyle-qmail at memoryhole

Feb 10, 2010, 1:12 PM

Post #2 of 12 (2856 views)
Permalink
Re: Forward Email by address [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wednesday, February 10 at 02:38 PM, quoth jay Moore:
> So, can I forward jmoore [at] betaclub to the new zimbra server and
> still have kcline [at] betaclub delivered locally?

Of course you can.

The way I'd do it is via virtualdomains; you can establish for each
user you wish to have forwarded a special handler, like so:

jmoore [at] betaclub:forwardme

Then create the file /var/qmail/alias/.qmail-forwardme-default with
the following contents:

|qmail-remote [zimbra_IP] ${SENDER} ${EXT}@betaclub.org

Now, strictly speaking, if you do that, you'll get some weird-looking
log messages based on the output of qmail-remote (which is really
intended for use by qmail-lspawn). It's relatively easy to write a
little shell script wrapper around qmail-remote to straighten that out
and make it a more straightforward, but I leave that as an exercise
for the reader.

Another way you could do it is to use the forwardme alias to deliver
to a local Maildir and then use serialsmtp (or rather, maildirserial)
via cron to blast email over to the Zimbra server.

Either way would work.

~Kyle
- --
People who would give up their Freedom for security deserve neither.
-- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJLcyE7AAoJECuveozR/AWehGMQAJ5p0Q0G16VNFpGtm1cghkf4
44g3+XXoT168Cc/gb9afm+cEoERuUSum73ulY3BB5udmmn4x3qqKCW56dTLhWefw
7FXicaQbJrmI/OKSAiGsdzm/R7e35T0CpWXUWIZDh0T7+WLDPC0mtMVaemdEvpLH
jlvhv+Jk3u2e3BYUjlCOcD4hsDWUTQlE0UfYZ4VEGrH41B1EB/I1WxFGdyadLfWj
fV2o2f75gwL+Rh0SZm2vT8TiCW3uf7t/I5aypWM9716WZalI5aHrtHvB3NC5NXo2
02oohQ9JCQy/Et9HzUUaI3kKN0KPlZHFAfoiR7KeNuOK6aMOZBLuiNQEQXQHgLqn
z5xzrnn/PlbiNpueXAr6PjgbVk570a1/4qx8eXdoLPWo96wMrAgPdR2exZRnZ2z8
piI4gnRUvGi0CVMYAffgKZR2U05WNQwTNcN8f33fk0DB6Fp27Bos69huLn5qnISs
ccSByeeplZVa4zn0Dm0YsKoGKNLhCgtbA46bsAoyn1HJyXVZbW3SfNbXxHqbaCDM
vi1XM0HuvSUFVQXT1a46etVASGf6LDlV/RRs+4DCeDpzdWv8otH0q/6bIr7Md4JC
Oew6wC17/teF5avuP/dNsLPyXn3k3A2PLehGzkUIW+VxBeTrH3wh2IeGdxF0IrWb
/GKLHZukfFUQu7wDezgn
=4Abm
-----END PGP SIGNATURE-----


feh at fehcom

Feb 10, 2010, 1:22 PM

Post #3 of 12 (2854 views)
Permalink
Re: Forward Email by address [In reply to]

Hi,


--On Wednesday, February 10, 2010 14:38:33 -0500 jay Moore
<jmoore [at] moorekin> wrote:

>
>
> Is it possible to forward email based on email address and not the entire
> domain. We are implementing Zimbra internally but still want qmail to be
> the email “gateway” for virus and spam scanning. I would like to
> migrate each user over to the new zimbra server one at a time. So, can I
> forward jmoore [at] betaclub to the new zimbra server and still have
> kcline [at] betaclub delivered locally?

My SMTP Authentication patch (for qmail-remote) would be able to do this
tweaking.

Instead of setting up a domain-specific route, now you can do this per
'email' (SMTP originator) address.
I don't now, whether it solves your problem; this is good for remote
delivery.

One other thought would be to set up a local .qmail-default file (per
virtualdomain 'betaclub.org') including a fastforward instruction for the
above email addresses; this could be used for local delivery.

Hope, that helps.

regards.
--eh.
>
>
>
> Thanks!
>
>



Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/


ar-djblists at acrconsulting

Feb 10, 2010, 1:31 PM

Post #4 of 12 (2855 views)
Permalink
Re: Forward Email by address [In reply to]

On Wednesday 10 February 2010 19:38:33 you wrote:
> Is it possible to forward email based on email address and not the
> entire domain. We are implementing Zimbra internally but still want
> qmail to be the email "gateway" for virus and spam scanning. I would
> like to migrate each user over to the new zimbra server one at a time.
> So, can I forward jmoore [at] betaclub to the new zimbra server and
> still have
> kcline [at] betaclub delivered locally?

Yes. There are 2 ways I can think of to do this:

Use virtualdomains: Have an entry per user. As you migrate each user to
Zimbra, remove their virtualdomains entry (HUP qmail-send to notify it of
the change). Put your domain with the target IP address (of the Zimbra
server) in smtproutes - now any user in that domain not referenced in
virtualdomains or locals is forwarded to the server given in smtproutes.
This could be a bit tricky to retrofit, so test this with a dummy domain
first until you get it right. Alternatively...

Setup a 2nd instance of qmail on the same server. Let's assume this is in
/var/qmail2. Setup the smtproutes as above. Ensure your domain is not setup
in locals or virtualdomains so that this instance will always send mail for
your domain to your Zimbra server. When you wish to migrate a user
create/change their .qmail[-default] file to use the 'forward' command of
the 2nd qmail instead of delivering to their local mailbox, thus for
example,
|/var/qmail2/bin/forward $LOCAL [at] example
but note that depending on your setup $LOCAL may not be the right variable
to use. Kyle Wheeler describes this very well in a post from August 1st
2008:
> ...When qmail
> makes a domain virtual, it prepends addresses with a string. For
> example, if you had the following in your virtualdomains file:
>
> domain2.com:foo
>
> That means that domain2.com addresses are controlled by the user "foo"
> and all user [at] domain2 addresses are internally rewritten as
> foo-user [at] domain2 Thus, when they're delivered, $USER is "foo",
> $LOCAL is "foo-user" and RECIPIENT is "foo-user [at] domain2".
> Obviously, what you're needing is the extension to the address
> ("user"), which is stored in $EXT.
>
> Those environment variables are spelled out and fully described in the
> qmail-command man page.

cheers,

Andrew.
--
====================================================================
* Custom email solutions * Systems Administration * Networking
http://www.acrconsulting.co.uk/email/qmail.html
====================================================================


jmoore at moorekin

Feb 10, 2010, 1:35 PM

Post #5 of 12 (2860 views)
Permalink
Re: Forward Email by address [In reply to]

All,
----- "Erwin Hoffmann" <feh [at] fehcom> wrote:

> Hi,
>
>
> --On Wednesday, February 10, 2010 14:38:33 -0500 jay Moore
> <jmoore [at] moorekin> wrote:
>
> >
> >
> > Is it possible to forward email based on email address and not the
> entire
> > domain. We are implementing Zimbra internally but still want qmail
> to be
> > the email “gateway” for virus and spam scanning. I would like to
> > migrate each user over to the new zimbra server one at a time. So,
> can I
> > forward jmoore [at] betaclub to the new zimbra server and still have
> > kcline [at] betaclub delivered locally?
>
> My SMTP Authentication patch (for qmail-remote) would be able to do
> this
> tweaking.
>
> Instead of setting up a domain-specific route, now you can do this
> per
> 'email' (SMTP originator) address.
> I don't now, whether it solves your problem; this is good for remote
> delivery.

Does that mean I can use the following in smtproutes
jmoore [at] betaclub:<ip of new server>

Thanks!


robert.sander at epigenomics

Feb 10, 2010, 1:45 PM

Post #6 of 12 (2880 views)
Permalink
Re: Forward Email by address [In reply to]

In epi.ml.qmail, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Wednesday, February 10 at 02:38 PM, quoth jay Moore:
>> So, can I forward jmoore [at] betaclub to the new zimbra server and
>> still have kcline [at] betaclub delivered locally?
>
> Of course you can.
>
> The way I'd do it is via virtualdomains; you can establish for each
> user you wish to have forwarded a special handler, like so:
>
> jmoore [at] betaclub:forwardme
>
> Then create the file /var/qmail/alias/.qmail-forwardme-default with
> the following contents:
>
> |qmail-remote [zimbra_IP] ${SENDER} ${EXT}@betaclub.org
>

Instead of calling qmail-remote directly (and therefor having no
queueing feature) I suggest using /var/qmail/bin/forward:

Put

| /var/qmail/bin/forward $LOCAL [at] zimbra

into /var/qmail/alias/.qmail-forwardme-default where zimbra.domain.com
is the FQDN of your zimbra MTA.

On the Zimbra side you have to create zimbra.domain.com as an alias
domain to your real domain.

http://wiki.zimbra.com/index.php?title=Managing_Domains#ZCS_5.0.16_and_later

# zmprov createAliasDomain zimbra.domain.com domain.com zimbraMailCatchAllForwardingAddress @domain.com

Regards
--
Robert Sander


feh at fehcom

Feb 10, 2010, 1:50 PM

Post #7 of 12 (2839 views)
Permalink
Re: Forward Email by address [In reply to]

Hi,

--On Wednesday, February 10, 2010 16:35:00 -0500 jay Moore
<jmoore [at] moorekin> wrote:

Well, actually not within smtproutes, but rather:

authsenders
Authenticated sender. For each sender included in
authsenders:
sender:relay:port|user|password qmail-remote will try SMTP
Authen-
tication of type LOGIN or PLAIN with the provided user name
user
and password password (the authentication information) and
eventu-
ally relay the mail through relay on port port. The use of
relay
and port follows the same rules as for smtproutes Note: In
case
sender is empty, qmail-remote will try to deliver each
outgoing
mail SMTP authenticated. If the authentication information
is
missing, the mail is delivered none-authenticated.
authsenders
can be constructed as follows:

@example.com|generic|passwd
.subdomain.example.com|other|otherpw
mail [at] example|test|testpass
info [at] example:smtp.example.com:26|other|otherpw
:mailrelay.example.com|e=mc2|testpass

Since SMTP Auth uses no-auth as fallback you can typically ommit
username/password here.

BUT: Before applying the patch, please check your qmail installation
whether it complies with the conditions of my patch and whether the
suggested simpler methods can be used instead.

regards.
--eh.


> All,
> ----- "Erwin Hoffmann" <feh [at] fehcom> wrote:
>
>> Hi,
>>
>>
>> --On Wednesday, February 10, 2010 14:38:33 -0500 jay Moore
>> <jmoore [at] moorekin> wrote:
>>
>> >
>> >
>> > Is it possible to forward email based on email address and not the
>> entire
>> > domain. We are implementing Zimbra internally but still want qmail
>> to be
>> > the email “gateway” for virus and spam scanning. I would like to
>> > migrate each user over to the new zimbra server one at a time. So,
>> can I
>> > forward jmoore [at] betaclub to the new zimbra server and still have
>> > kcline [at] betaclub delivered locally?
>>
>> My SMTP Authentication patch (for qmail-remote) would be able to do
>> this
>> tweaking.
>>
>> Instead of setting up a domain-specific route, now you can do this
>> per
>> 'email' (SMTP originator) address.
>> I don't now, whether it solves your problem; this is good for remote
>> delivery.
>
> Does that mean I can use the following in smtproutes
> jmoore [at] betaclub:<ip of new server>
>
> Thanks!
>



Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/


kyle-qmail at memoryhole

Feb 10, 2010, 2:39 PM

Post #8 of 12 (2840 views)
Permalink
Re: Forward Email by address [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wednesday, February 10 at 10:45 PM, quoth Robert Sander:
>> |qmail-remote [zimbra_IP] ${SENDER} ${EXT}@betaclub.org
>>
>
>Instead of calling qmail-remote directly (and therefor having no
>queueing feature) I suggest using /var/qmail/bin/forward:

Of course you'd have queueing; if the delivery failed, qmail would try
again later, the same way it does if (for example) it fails to deliver
locally because you ran out of quota. All you have to do is wrap
qmail-remote in something that returns the right error code for failed
delivery.

~Kyle
- --
In all matters of opinion, our adversaries are insane.
-- Oscar Wilde
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJLczWFAAoJECuveozR/AWe5mYP/2NgIDW9RPmEVr21ASm4gtMK
Ao4bWCJY5bSJB+suzesqU+CzcjEwsFQw62gWErIskAi/od6Ovfopc3MeUEv7ZNCN
0P3TfmJ0QJP1Msvsp/f6KYhxagFTZTog53PKvsXJyRqDoWISrFkB7EkJSTS8Av9X
gTnyygv6I3FN8cuUTutAzHNY4gr88XwLX0Q4JXxialsgkEuKHF/jEAY+MZlDV8Ev
MlDWgfcfHwuVBRJetOQbfnFVWMT28yO/Whu/81P7kMSpE+Zh0jusBLAX38Lq+Y9V
AqGUjqcyEFp3h2ayYdiTiTUGSfdpSf2ZaKFjBn1JKan6LKNLQavbZfPUfWaobfS7
OsRJYuS6ufZP2DRe/FVKp4EMcxQ6UBn8u0nydOr9sOGNQFb10xd0+HAcM9ZyeLa2
C5lZFw1SfDdNIit67aiwmjK27UORzlCmwQEm2Y6EGacHDDk7XmmqtZ7HOu40elji
I5YL+iG/7FfhtFEzpePvePFgMI7BEeZt6QpIjgdSvEOrWwYN2LEdPC08HIvA2gEk
3r4Bij2Olu5waxnM6I/ZLx+dPMmv1SspTnrBTF/zgUMUqLD6lqVd6Gkr+ObJttxO
LMgXMbhyUU2eQTJRa3gTU0vSZLNO4YOkVA7DcjrgUKa8vOYncpqSnc6BKsQ2Wu3o
ZBqlM3hIi1RR4opLE85V
=xYbe
-----END PGP SIGNATURE-----


jasons at adventureaquarium

Feb 11, 2010, 7:47 AM

Post #9 of 12 (2822 views)
Permalink
RE: Forward Email by address [In reply to]

> -----Original Message-----
> From: Kyle Wheeler [mailto:kyle-qmail [at] memoryhole]
> Sent: Wednesday, February 10, 2010 4:13 PM
> To: qmail [at] list
> Subject: Re: Forward Email by address
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Wednesday, February 10 at 02:38 PM, quoth jay Moore:
> > So, can I forward jmoore [at] betaclub to the new zimbra server and
> > still have kcline [at] betaclub delivered locally?
>
> Of course you can.
>
> The way I'd do it is via virtualdomains; you can establish for each
> user you wish to have forwarded a special handler, like so:
>
> jmoore [at] betaclub:forwardme
>
> Then create the file /var/qmail/alias/.qmail-forwardme-default with
> the following contents:
>
> |qmail-remote [zimbra_IP] ${SENDER} ${EXT}@betaclub.org
>
> Now, strictly speaking, if you do that, you'll get some weird-looking
> log messages based on the output of qmail-remote (which is really
> intended for use by qmail-lspawn). It's relatively easy to write a
> little shell script wrapper around qmail-remote to straighten
> that out
> and make it a more straightforward, but I leave that as an exercise
> for the reader.
>
> Another way you could do it is to use the forwardme alias to deliver
> to a local Maildir and then use serialsmtp (or rather, maildirserial)
> via cron to blast email over to the Zimbra server.
>
> Either way would work.
>
> ~Kyle
> - --
> People who would give up their Freedom for security deserve neither.
> --
> Benjamin Franklin

I've got a similar deal with my newtork, one new server one older server both with the same domain space (old 10.252.0.10 new 10.252.0.2).
I tried this suggestion but I don't think it's quite right. I have a test account setup on the newserver (testflow) here's the log from my last test

Send log:
2010-02-11 10:35:53.596874500 info msg 183747: bytes 2434 from <jasons [at] adventureaquarium> qp 26339 uid 502
2010-02-11 10:35:53.599350500 starting delivery 179050: msg 183747 to local forwardme-testflow [at] adventureaquarium
2010-02-11 10:35:53.599394500 status: local 2/10 remote 0/15
2010-02-11 10:35:53.603253500 delivery 179049: success: did_1+0+0/
2010-02-11 10:35:53.603302500 status: local 1/10 remote 0/15
2010-02-11 10:35:53.610868500 delivery 179050: success: r
2010-02-11 10:35:53.610916500 status: local 0/10 remote 0/15

I'm seeing a connection atempt to the new server, and if it did forwardme-testflow doesn't exisit. I think I have something wrong here.

.qmail-forwardme-default:
|qmail-remote 10.252.0.2 ${SENDER} ${EXT}@adventureaquarium.com

virtualdomains:
testflow [at] adventureaquarium:forwardme

Thoughs??

Jason



..><((((>


kyle-qmail at memoryhole

Feb 11, 2010, 8:22 AM

Post #10 of 12 (2816 views)
Permalink
Re: Forward Email by address [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thursday, February 11 at 10:47 AM, quoth Jason Staudenmayer:
>Send log:
>2010-02-11 10:35:53.596874500 info msg 183747: bytes 2434 from <jasons [at] adventureaquarium> qp 26339 uid 502
>2010-02-11 10:35:53.599350500 starting delivery 179050: msg 183747 to local forwardme-testflow [at] adventureaquarium
>2010-02-11 10:35:53.599394500 status: local 2/10 remote 0/15
>2010-02-11 10:35:53.603253500 delivery 179049: success: did_1+0+0/
>2010-02-11 10:35:53.603302500 status: local 1/10 remote 0/15
>2010-02-11 10:35:53.610868500 delivery 179050: success: r
>2010-02-11 10:35:53.610916500 status: local 0/10 remote 0/15
>
>I'm seeing a connection atempt to the new server, and if it did forwardme-testflow doesn't exisit. I think I have something wrong here.
>
>.qmail-forwardme-default:
>|qmail-remote 10.252.0.2 ${SENDER} ${EXT}@adventureaquarium.com

Strictly speaking, that IP address *SHOULD* be inside brackets
(according to the qmail-remote man page), like this:

|qmail-remote [10.252.0.2] ${SENDER} ${EXT}@adventureaquarium.com

Like I said, though, using qmail-remote directly will result in two
things: 1. weird log messages (e.g. the "success: r") and 2. failures
won't be recognized properly.

To do it reliably, you need a wrapper to deal with the way that
qmail-remote handles reporting the outcome of a delivery attempt.

Since nobody seems interested in that part of what I wrote, here's a
simple wrapper script that would do such a thing:

#!/bin/sh
/var/qmail/bin/qmail-remote "$@" | \
while read -d $'\0' result ; do
case "$result" in
K*) # success
echo ${result:1}
exit 0;;
Z*) # temporary failure
echo ${result:1}
exit 71;;
D*) # permanent failure
echo ${result:1}
exit 31;;
esac
done

(and, for what it's worth, that's a slight modification of a script
that's in my "Qmail Quickstarter" book)

~Kyle
- --
Last comes the beverage of the Orient shore, Mocha, far off, the
fragrant berries bore. Taste the dark fluid with a dainty lip,
Digestion waits on pleasure as you sip.
-- Pope Leo XII
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJLdC6wAAoJECuveozR/AWezhkQAKlO+/YeDAvmjI3yRxqYbpzs
oL7beEHIF4f5q49/VI0x6rLDoJ7W5RcXrrwPQwCWAQVtvda0Kf33VjaVC3/YLE1O
SLOycgwCp1edZ8DbV72gXk+guS3Gr3wqU2EqLugcIF/8d38LykKk9HpsW/FZZHBL
I/q8mgRmcUXH4ybqUSgTV9obKMMzYE8ekGKQKSKyZqgLgDtElEACWCkBniTosUPb
fM11KAs5YmB2JRZcLmkqz/Wfp4Fn4d2GtPP7gsGS/jpwbTF8ioKlYaK5ctmpsgpD
AgcpkPUrpWDV6cLUB5KvuqTBhhEOeZGj13R50Zk/E5H6WhRAoghk5EuxdhysflQI
B4WfJxGHsCgy5aReatnY2I2MdrOLR1yvlrsPTPYZcnZWWpMe3eaN1EoTKrTGGp/d
rs4kOBGeeZzJFTkipRW2wtWUvPRuZxDeCJwBtMa1e7NmcAUOpsinH0VeBEyyEEPM
0tzgKmkLM8BOOqRWS5nBx6Pj83oByC8eu3q/nJoHjRxYZJTtrmXuGFsyGBwT3rnq
jw3YgNYCmsB9w5rixqV0deOlfaEcndWVWipuZOuq3fCiZcbN+JKjukluX0ZX0MUP
Rj3rs1ZAQsPQdGrlK5TRbh9ohN8nAr0fOYOUOREKr8p3yFSrFYDNJbkd1g4aDr3B
RaXzIxyItnx/JcxbvTdu
=CbVm
-----END PGP SIGNATURE-----


jasons at adventureaquarium

Feb 11, 2010, 8:42 AM

Post #11 of 12 (2811 views)
Permalink
RE: Forward Email by address [In reply to]

> -----Original Message-----
> From: Kyle Wheeler [mailto:kyle-qmail [at] memoryhole]
> Sent: Thursday, February 11, 2010 11:22 AM
> To: qmail [at] list
> Subject: Re: Forward Email by address
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Thursday, February 11 at 10:47 AM, quoth Jason Staudenmayer:
> >Send log:
> >2010-02-11 10:35:53.596874500 info msg 183747: bytes 2434
> from <jasons [at] adventureaquarium> qp 26339 uid 502
> >2010-02-11 10:35:53.599350500 starting delivery 179050: msg
> 183747 to local forwardme-testflow [at] adventureaquarium
> >2010-02-11 10:35:53.599394500 status: local 2/10 remote 0/15
> >2010-02-11 10:35:53.603253500 delivery 179049: success: did_1+0+0/
> >2010-02-11 10:35:53.603302500 status: local 1/10 remote 0/15
> >2010-02-11 10:35:53.610868500 delivery 179050: success: r
> >2010-02-11 10:35:53.610916500 status: local 0/10 remote 0/15
> >
> >I'm seeing a connection atempt to the new server, and if it
> did forwardme-testflow doesn't exisit. I think I have
> something wrong here.
> >
> >.qmail-forwardme-default:
> >|qmail-remote 10.252.0.2 ${SENDER} ${EXT}@adventureaquarium.com
>
> Strictly speaking, that IP address *SHOULD* be inside brackets
> (according to the qmail-remote man page), like this:
>
> |qmail-remote [10.252.0.2] ${SENDER} ${EXT}@adventureaquarium.com
>
> Like I said, though, using qmail-remote directly will result in two
> things: 1. weird log messages (e.g. the "success: r") and 2. failures
> won't be recognized properly.
>
> To do it reliably, you need a wrapper to deal with the way that
> qmail-remote handles reporting the outcome of a delivery attempt.
>
> Since nobody seems interested in that part of what I wrote, here's a
> simple wrapper script that would do such a thing:
>
> #!/bin/sh
> /var/qmail/bin/qmail-remote "$@" | \
> while read -d $'\0' result ; do
> case "$result" in
> K*) # success
> echo ${result:1}
> exit 0;;
> Z*) # temporary failure
> echo ${result:1}
> exit 71;;
> D*) # permanent failure
> echo ${result:1}
> exit 31;;
> esac
> done
>
> (and, for what it's worth, that's a slight modification of a script
> that's in my "Qmail Quickstarter" book)
>
> ~Kyle
> - --
> Last comes the beverage of the Orient shore, Mocha, far off, the
> fragrant berries bore. Taste the dark fluid with a dainty lip,
> Digestion waits on pleasure as you sip.
> --

Thanks Kyle,
I'll try the script and fix the brackets (I wasn't sure if they should stay). What about the address itself though?
Is there any way to get it to forward without the forwardme- part prefixed?

THANKS
Jason



..><((((>


kyle-qmail at memoryhole

Feb 11, 2010, 8:48 AM

Post #12 of 12 (2810 views)
Permalink
Re: Forward Email by address [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thursday, February 11 at 11:42 AM, quoth Jason Staudenmayer:
>Thanks Kyle,
> I'll try the script and fix the brackets (I wasn't sure if they should stay). What about the address itself though?
>Is there any way to get it to forward without the forwardme- part prefixed?

Ahh, that wasn't clear from your email. Try using ${DEFAULT} instead
of ${EXT}.

~Kyle
- --
You can not establish sound security, on borrowed money. You can not
keep out of trouble, by spending more than you earn.
-- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iQIcBAEBCAAGBQJLdDT4AAoJECuveozR/AWe4yQQAKVqmk2quwP+3Gf8IuPa0fYk
BW7iFaWvK2zwKKQaywGZvQD7MLrg1oJK700EXOtz0tcNKUMh4eJRvFHjfdj+9sde
0F4vGG5fCegkWhE44sPsuS8nExfpzeM2++R6mQDBLa+28jT/7Yno6HLRZoqXGyio
MpEjd4C842pBTcddXCYNpZ2LKDGNJ7fADpqckrukhS566oMnRXTj0xq44JcRy0/Y
u9ggXIG7l2vD/x2qBlWDn683CePmoMHzcEGwlkDoRPyVNcRXXRAw0X+rPOH/rX+h
iv34VZR9RwKpPRwZjj0X7G3hyN1tdx0xSDuZ4HgQOa8WATVTbJBpH9Dp59FfYDbv
l/hqZ7qhST8GH7HlVV/6MA6G5Z+U98fG/iAUw/AhOOVoyOet96NwRl6usEcZd8rH
NpA4lNZxXmJv1dgwb/s+FhW9ReWwtBMd4xgaV1CHmAKdMym4+OxL6LTlFjDJnUBM
hpW7IjqghK/vRYxtCl/eJn5dTtno2xgRDbb9wNaRYSSie121ZZEiuYllGBRPCFCb
Lh1At+oYNmIrbfsAXeK5sMr8tDWP3X0TPorJ6CjcLTHylAEihN3nXl9NDRv43+xl
YF4J44NTIrsROvdPPX6GZg1W9LT3oUuuGpEtsi9qvpixUdGG5YeRcH0euqDGIAM1
3qSjccdwulkvWlBOVm4L
=F+wY
-----END PGP SIGNATURE-----

Qmail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.