[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qmail
Subject:    Re: SRS / what next after qmail + vmailmgr ?
From:       Michael DiMartino <michael () hudsonstreet ! us>
Date:       2020-07-18 18:13:34
Message-ID: CANX2mUHikig4dLu=17zoESCX2JxOeorVHuBtmmb_H7ObZv2ZDw () mail ! gmail ! com
[Download RAW message or body]

Remove from list

On Fri, Jul 17, 2020 at 6:13 PM Olivier Mueller <om-lists-qmail@omx.ch>
wrote:

> Hi Erwin & List,
>
> Le 26.06.20 à 00:47, Erwin Hoffmann a écrit :
> > Within my s/qmail, SRS is provided in a simpler case, supporting
> vmailmgr as well (I use it here, rather than vpopmail).
> > > Even if you don't intend to use s/qmail, you simply could compile it
> and extract srsforward and srsreverse.>
> >       https://www.fehcom.de/sqmail/sqmaildoc_05.html
>
> So, a few days later I finally managed to compile srsforward +
> srsreverse on my freebsd 12 box and I just try a few things. Everything
> with a .qmail file is running great and envelope rewriting as well, nice
> work!
>
>
> Now I just miss a way to make it work with my standard vmailmgr-managed
> users.  For example, in /home/example.org/, I have this srstest1 user:
>
> $ listvdomain srstest1
>
> User Mailbox Aliases
> srstest1 Yes remote1@example.net remote2@example.net
>
> Mails to srstest1@example.org should be stored locally in
> ~/users/srstest1/ (maildir) and be forwarded to the remote1 + remote2
> addresses.  It is the way it works now, but without SRS.
>
>
> If I want to use srsforward, it seems I need to manually create a
> /home/example.org/.qmail-srstest1 with:
>
> ./users/srstest1/
> |srsforward remote1@example.net remote2@example.net
>
> (first line for the local delivery, second for the srs-forwardings).
>
> Is it the way it is intended to work, or is there a possibility to have
> an automatic lookup in the vmailmgr table (passwd.cdb) from srsforward ?
>    I tried to pipe the commands, but it didn't work either.  How are you
> doing it with your vmailmgr users if I may ask ? I probably missed
> something.
>
> Otherwise I could theoretically still use this way for some power users,
> but it would require some cronjobs and/or omail-hooks generating all the
> .qmail-files based on the corresponding passwd.cdb files on any change.
>
>
>
> I will also try to use the patch from Marcelo Coelho sometime later, but
> as I'm using the mail/qmail-tls freebsd port (thanks erdgeist!) based on
> netqmail, it may be even more challenging because of the patching of an
> already patched source tree... :)
>
> Kind regards & nice week-end to you,
> Olivier
>
-- 
Sent from Gmail Mobile

[Attachment #3 (text/html)]

<div><div dir="auto">Remove from list</div></div><div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 17, 2020 at 6:13 PM \
Olivier Mueller &lt;<a \
href="mailto:om-lists-qmail@omx.ch">om-lists-qmail@omx.ch</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Erwin &amp; List,<br> <br>
Le 26.06.20 à 00:47, Erwin Hoffmann a écrit  :<br>
&gt; Within my s/qmail, SRS is provided in a simpler case, supporting vmailmgr as \
well (I use it here, rather than vpopmail).<br> &gt; &gt; Even if you don&#39;t \
intend to use s/qmail, you simply could compile it and extract srsforward and \
srsreverse.&gt; <br> &gt;           <a \
href="https://www.fehcom.de/sqmail/sqmaildoc_05.html" rel="noreferrer" \
target="_blank">https://www.fehcom.de/sqmail/sqmaildoc_05.html</a><br> <br>
So, a few days later I finally managed to compile srsforward + <br>
srsreverse on my freebsd 12 box and I just try a few things. Everything <br>
with a .qmail file is running great and envelope rewriting as well, nice <br>
work!<br>
<br>
<br>
Now I just miss a way to make it work with my standard vmailmgr-managed <br>
users.   For example, in /home/<a href="http://example.org/" rel="noreferrer" \
target="_blank">example.org/</a>, I have this srstest1 user:<br> <br>
$ listvdomain srstest1<br>
<br>
User Mailbox Aliases<br>
srstest1 Yes <a href="mailto:remote1@example.net" \
target="_blank">remote1@example.net</a> <a href="mailto:remote2@example.net" \
target="_blank">remote2@example.net</a><br> <br>
Mails to <a href="mailto:srstest1@example.org" \
target="_blank">srstest1@example.org</a> should be stored locally in <br> \
~/users/srstest1/ (maildir) and be forwarded to the remote1 + remote2 <br> addresses. \
It is the way it works now, but without SRS.<br> <br>
<br>
If I want to use srsforward, it seems I need to manually create a<br>
/home/<a href="http://example.org/.qmail-srstest1" rel="noreferrer" \
target="_blank">example.org/.qmail-srstest1</a> with:<br> <br>
./users/srstest1/<br>
> srsforward <a href="mailto:remote1@example.net" \
> target="_blank">remote1@example.net</a> <a href="mailto:remote2@example.net" \
> target="_blank">remote2@example.net</a><br>
<br>
(first line for the local delivery, second for the srs-forwardings).<br>
<br>
Is it the way it is intended to work, or is there a possibility to have <br>
an automatic lookup in the vmailmgr table (passwd.cdb) from srsforward ? <br>
     I tried to pipe the commands, but it didn&#39;t work either.   How are you <br>
doing it with your vmailmgr users if I may ask ? I probably missed <br>
something.<br>
<br>
Otherwise I could theoretically still use this way for some power users, <br>
but it would require some cronjobs and/or omail-hooks generating all the <br>
.qmail-files based on the corresponding passwd.cdb files on any change.<br>
<br>
<br>
<br>
I will also try to use the patch from Marcelo Coelho sometime later, but <br>
as I&#39;m using the mail/qmail-tls freebsd port (thanks erdgeist!) based on <br>
netqmail, it may be even more challenging because of the patching of an <br>
already patched source tree... :)<br>
<br>
Kind regards &amp; nice week-end to you,<br>
Olivier<br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature">Sent from Gmail Mobile</div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic