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

List:       mlmmj
Subject:    Re: [mlmmj] Using mlmmj with Postfix using non-virtual aliases ERROR: unknown user
From:       Emil Hemdal <emil.hemdal.em () gmail ! com>
Date:       2014-05-08 10:17:21
Message-ID: CAO8L7B6XxKmhyduY3pgTQxexaawUygUW=07wyVzUqZRvOapHcg () mail ! gmail ! com
[Download RAW message or body]

Ah, that the transport solves the permission issue so that mlmmj is run
with the mlmmj user.

/Emil


2014-05-08 10:53 GMT+02:00 Ben Schmidt <mail_ben_schmidt@yahoo.com.au>:

> OK, cool.
>
> Just be aware of the possible security problems detailed in README.postfix
> if you don't use a transport or similarly secure mechanism with Postfix.
> They might not matter in your setup, but you should at least be aware of
> them.
>
> Smiles,
>
> Ben.
>
>
>
>
> On 8/05/14 4:25 PM, Emil Hemdal wrote:
>
>> Hello,
>>
>> I followed the README instead of the README.postfix and it solved my
>> problem!
>>
>> Thanks for the help!
>>
>> /Emil
>>
>>
>> 2014-05-07 23:34 GMT+02:00 Ben Schmidt <mail_ben_schmidt@yahoo.com.au
>> <mailto:mail_ben_schmidt@yahoo.com.au>>:
>>
>>
>>         May  4 13:37:19 mydomain postfix/local[7254]: EED2181041:
>>         to=<list_info+subscribe@__localhost.mlmmj>,
>>         orig_to=<list_info+subscribe@__mydomain.tld>, relay=local,
>> delay=0.14,
>>
>>         delays=0.08/0.02/0/0.04, dsn=5.1.1, status=bounced (unknown user:
>>         "list_info+subscribe")
>>
>>     ...
>>
>>         My transport file contains:
>>         mydomain.tld--list_info@__localhost.mlmmj
>> mlmmj:mydomain.tld/list_info
>>
>>
>>         My aliases file contains:
>>         list_info:              list_info@localhost.mlmmj
>>
>>
>>     After a very quick look, I think the transport file should read:
>>
>>     list_info@localhost.mlmmj mlmmj:list_info
>>
>>     I.e. if you're not using virtual domains, no need to include
>>     mydomain.tld. The important thing is that the left hand side of
>>     transport matches the right hand side of aliases
>>     (list_info@loclahost.mlmmj) and the part after mlmmj: matches the
>> name
>>     of the list directory (relative to the list spool directory).
>>
>>     Ben.
>>
>>
>>
>>
>>

[Attachment #3 (text/html)]

<div dir="ltr"><div>Ah, that the transport solves the permission issue so that mlmmj \
is run with the mlmmj user.</div><div><br></div><div>/Emil</div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2014-05-08 10:53 GMT+02:00 Ben \
Schmidt <span dir="ltr">&lt;<a href="mailto:mail_ben_schmidt@yahoo.com.au" \
target="_blank">mail_ben_schmidt@yahoo.com.au</a>&gt;</span>:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">OK, cool.<br> <br>
Just be aware of the possible security problems detailed in README.postfix if you \
don&#39;t use a transport or similarly secure mechanism with Postfix. They might not \
matter in your setup, but you should at least be aware of them.<br>


<br>
Smiles,<br>
<br>
Ben.<div><br>
<br>
<br>
<br>
On 8/05/14 4:25 PM, Emil Hemdal wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div>
 Hello,<br>
<br>
I followed the README instead of the README.postfix and it solved my problem!<br>
<br>
Thanks for the help!<br>
<br>
/Emil<br>
<br>
<br>
2014-05-07 23:34 GMT+02:00 Ben Schmidt &lt;<a \
href="mailto:mail_ben_schmidt@yahoo.com.au" \
target="_blank">mail_ben_schmidt@yahoo.com.au</a><br></div> &lt;mailto:<a \
href="mailto:mail_ben_schmidt@yahoo.com.au" \
target="_blank">mail_ben_schmidt@<u></u>yahoo.com.au</a>&gt;&gt;:<div><br> <br>
            May   4 13:37:19 mydomain postfix/local[7254]: EED2181041:<br></div>
            to=&lt;list_info+subscribe@__<u></u>localhost.mlmmj&gt;,<br>
            orig_to=&lt;list_info+subscribe@_<u></u>_mydomain.tld&gt;, relay=local, \
                delay=0.14,<div><br>
            delays=0.08/0.02/0/0.04, dsn=5.1.1, status=bounced (unknown user:<br>
            &quot;list_info+subscribe&quot;)<br>
<br>
      ...<br>
<br>
            My transport file contains:<br></div>
            mydomain.tld--list_info@__<u></u>localhost.mlmmj \
mlmmj:mydomain.tld/list_info<div><br> <br>
            My aliases file contains:<br>
            list_info:                     list_info@localhost.mlmmj<br>
<br>
<br>
      After a very quick look, I think the transport file should read:<br>
<br>
      list_info@localhost.mlmmj mlmmj:list_info<br>
<br>
      I.e. if you&#39;re not using virtual domains, no need to include<br>
      mydomain.tld. The important thing is that the left hand side of<br>
      transport matches the right hand side of aliases<br>
      (list_info@loclahost.mlmmj) and the part after mlmmj: matches the name<br>
      of the list directory (relative to the list spool directory).<br>
<br>
      Ben.<br>
<br>
<br>
<br>
<br>
</div></blockquote>
</blockquote></div><br></div>



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