address extension fails for mailman

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

address extension fails for mailman

thorthor
I have a mailman3 installation and postfix. One problem arises when a new
subscriber replies to listname*+token*@klubb.example.com. Postfix doesn't
match the email with postfix_lmtp, and instead rejects the mail as no local
user is found.From postfix log:What have I done wrong?



--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Wietse Venema
thorthor:
> I have a mailman3 installation and postfix. One problem arises when a new
> subscriber replies to listname*+token*@klubb.example.com. Postfix doesn't
> match the email with postfix_lmtp, and instead rejects the mail as no local
> user is found.From postfix log:What have I done wrong?

Well, that depends on what you have done. What have you done in
terms of configuration, and what are the actual symptoms.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor
Hmm.. That's why I posted the log and configuration. Seems those parts have
been deleted from the post. I'll add it as soon as I get to the office.



--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor
This post should contain the log and main.cf.







--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Christian Kivalo
On 2017-09-29 10:07, thorthor wrote:
> This post should contain the log and main.cf.
Don't attach, post inline

> --
> Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html

--
  Christian Kivalo
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor
In reply to this post by thorthor
Here is my  main.cf
<http://postfix.1071664.n5.nabble.com/file/t6656/output3.txt>   and output
in  /var/log/mail.log
<http://postfix.1071664.n5.nabble.com/file/t6656/output2.txt>   after
sending an email from localhost.

And here,  /var/log/mail.log
<http://postfix.1071664.n5.nabble.com/file/t6656/realmaillog.txt>   excerpts
from sending from an external client.



--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Matus UHLAR - fantomas
On 29.09.17 01:36, thorthor wrote:
>Here is my  main.cf
><http://postfix.1071664.n5.nabble.com/file/t6656/output3.txt>   and output
>in  /var/log/mail.log
><http://postfix.1071664.n5.nabble.com/file/t6656/output2.txt>   after
>sending an email from localhost.
>
>And here,  /var/log/mail.log
><http://postfix.1071664.n5.nabble.com/file/t6656/realmaillog.txt>   excerpts
>from sending from an external client.

Sep 28 08:42:00 ip-172-31-28-174 postfix/local[4413]: B6DAA54DDC:
to=<[hidden email]>, relay=local, delay=0.01,
delays=0.01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "abcliste")

this looks like the extension works properly: abcliste+something is expanded
to user "abcliste" that is unknown

--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"Where do you want to go to die?" [Microsoft]
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor



Here is my  main.cf
<http://postfix.1071664.n5.nabble.com/file/t6656/output3.txt>   and output
in  /var/log/mail.log
<http://postfix.1071664.n5.nabble.com/file/t6656/output2.txt>   after
sending an email from localhost.

And here,  /var/log/mail.log
<http://postfix.1071664.n5.nabble.com/file/t6656/realmaillog.txt>   excerpts
from sending from an external client.

Sep 28 08:42:00 ip-172-31-28-174 postfix/local[4413]: B6DAA54DDC:
to=<[hidden email]>, relay=local, delay=0.01,
delays=0.<a href="tel:01%2F0%2F0%2F0" value="+4701000" target="_blank">01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "abcliste")

this looks like the extension works properly: abcliste+something is expanded
to user "abcliste" that is unknown

--

Ok, so if there had been a local user "abcliste" , the "+something" part would have been ignored and the message delivered, which I understand. Now, this is a mailman installation where "abcliste" is found in the local_recipients_map. If I could only make postfix check the local_recipients_map file also when incoming mail has the "+something" extension, I would be good. When incoming mail is sent to "abcliste", the local_recipients_map has a match, and message is relayed to mailman.

Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Wietse Venema
Thor Atle Rustad:

> > Here is my  main.cf
> >> <http://postfix.1071664.n5.nabble.com/file/t6656/output3.txt>   and
> >> output
> >> in  /var/log/mail.log
> >> <http://postfix.1071664.n5.nabble.com/file/t6656/output2.txt>   after
> >> sending an email from localhost.
> >>
> >> And here,  /var/log/mail.log
> >> <http://postfix.1071664.n5.nabble.com/file/t6656/realmaillog.txt>
> >>  excerpts
> >> from sending from an external client.
> >>
> >
> > Sep 28 08:42:00 ip-172-31-28-174 postfix/local[4413]: B6DAA54DDC:
> > to=<[hidden email]>, relay=local, delay=0.01,
> > delays=0.01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "abcliste")
> >
> > this looks like the extension works properly: abcliste+something is
> > expanded
> > to user "abcliste" that is unknown
> >
> > --
> >
> > Ok, so if there had been a local user "abcliste" , the "+something" part
> would have been ignored and the message delivered, which I understand. Now,
> this is a mailman installation where "abcliste" is found in the
> local_recipients_map. If I could only make postfix check the
> local_recipients_map file also when incoming mail has the "+something"
> extension, I would be good. When incoming mail is sent to "abcliste", the
> local_recipients_map has a match, and message is relayed to mailman.

/etc/postfix/main.cf:
    recipient_delimiter = +

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor

/etc/postfix/main.cf:
    recipient_delimiter = +

        Wietse
I have had recipient_delimiter = + since day 1. The mailman instructions call for that. 
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Matus UHLAR - fantomas
In reply to this post by thorthor
>> this looks like the extension works properly: abcliste+something is
>> expanded
>> to user "abcliste" that is unknown

On 01.10.17 20:32, Thor Atle Rustad wrote:
> Ok, so if there had been a local user "abcliste" , the "+something" part
>would have been ignored and the message delivered, which I understand. Now,
>this is a mailman installation where "abcliste" is found in the
>local_recipients_map. If I could only make postfix check the
>local_recipients_map file also when incoming mail has the "+something"
>extension, I would be good. When incoming mail is sent to "abcliste", the
>local_recipients_map has a match, and message is relayed to mailman.

please show us config/logs from situation where this is true.
It's hard to find error when you actually show us different error.

--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
LSD will make your ECS screen display 16.7 million colors
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Wietse Venema
In reply to this post by thorthor
Thor Atle Rustad:
> >
> >
> > /etc/postfix/main.cf:
> >     recipient_delimiter = +
> >
> >         Wietse
> >
> I have had recipient_delimiter = + since day 1. The mailman instructions
> call for that.

Prove it. Show output from

postconf -n recipient_delimiter
postconf -P '*/*/recipient_delimiter'

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor


2017-10-01 22:17 GMT+02:00 Wietse Venema <[hidden email]>:
Thor Atle Rustad:
> >
> >
> > /etc/postfix/main.cf:
> >     recipient_delimiter = +
> >
> >         Wietse
> >
> I have had recipient_delimiter = + since day 1. The mailman instructions
> call for that.

Prove it. Show output from

postconf -n recipient_delimiter
postconf -P '*/*/recipient_delimiter'

        Wietse
$ postconf -n recipient_delimiter;postconf -P '*/*/recipient_delimiter'
recipient_delimiter = +
postconf: warning: unmatched request: "*/*/recipient_delimiter"

Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Wietse Venema
In reply to this post by thorthor
> Sep 28 08:42:00 ip-172-31-28-174 postfix/local[4413]: B6DAA54DDC:
> to=<[hidden email]>, relay=local, delay=0.01,
> delays=0.01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "abcliste")

What does this even have to do with recipient_deliter? Your
local_recipent_maps setting does not seem to match your PAM
configuration for the system password database.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

Wietse Venema
Wietse Venema:
> > Sep 28 08:42:00 ip-172-31-28-174 postfix/local[4413]: B6DAA54DDC:
> > to=<[hidden email]>, relay=local, delay=0.01,
> > delays=0.01/0/0/0, dsn=5.1.1, status=bounced (unknown user: "abcliste")
>
> What does this even have to do with recipient_deliter? Your
> local_recipent_maps setting does not seem to match your PAM
> configuration for the system password database.

Or main.cf:alias_maps, as the case may be.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: address extension fails for mailman

thorthor
It has now been confirmed by the mailman3 team that the map generation for the regexp files in mailman is incomplete. They are working on a solution.  For those interested, see my post here: https://gitlab.com/mailman/mailman/issues/401.