Sending with tagged sender address #4022
Comments
|
Cannot reproduce with a tagged sender with mailcow-dockerized from master of Wed Mar 10 15:06:32 2021: Do you have any kind of custom changes in postfix configuration? |
Not any that I’d be aware of. Btw: just updated our mailcow instance before re-trying. Unfortunately still not working. |
|
Same here with latest version of mailcow. Modifications of Is there anything I can provide to bring more light into this issue? |
Anyway ... even with disabling this modification, I'm not able send with tagged sender address: |
|
Hi, looking deeper into this. The relevant part of the
Where is the part in Thanks, Jan. |
|
Looking with Is this the expected way? |
|
@waja i have a different understanding. According to postfix manual: So if you use user+foo and it does not find anything, it should automatically try user |
|
@monofox thanks for this pointer. I looked now for this and http://www.postfix.org/virtual.5.html has written the following:
Looks like I should verify propagate_unmatched_extensions. I'm still wondering as it seems I'm the only one facing this issue and postfix is running without any modifcations. Anyway ... with alias addresses it's the same: I'm out of ideas at the moment. :( |
|
The
For me, i'm testing with a clear mailbox + tag as well as alias + tag (no domain alias). What would be interesting, if you enable the smtp debug in postfix. In the past, if i had to do this, i used |
|
You can guess what? In #4022 (comment) it was broken. Now (running latest Looking into https://github.com/mailcow/mailcow-dockerized/commits/master/data/conf/postfix/master.cf I see 51e3521, 05f6e28 and 28ab998. But I don't see what can cause this hassle. But now I have a nice debug logfile. :) |
|
Hmmm .... okay ... it has todo with my local configuation. I've another user The debug log is attached. @andryyy any idea? |
|
Okay .... this does only happen when |
To understand your test case - you've a user How is the Would be interesting to see the result of the SQL. Could imagine, that he has a problem to find the '*' entry prior the other. |
|
nope. My test case is:
FROM: When the mailbox user If the mailbox user Looks like the address lookup is clashed somehow. |
|
Confirm @waja SELECT goto FROM alias
WHERE address='[email protected]'
AND active='1'
AND (domain IN
(SELECT domain FROM domain
WHERE domain='test.org'
AND active='1')
OR domain in (
SELECT alias_domain FROM alias_domain
WHERE alias_domain='test.org'
AND active='1'
)
)
UNION
SELECT logged_in_as FROM sender_acl
WHERE send_as='@test.org'
OR send_as='[email protected]'
OR send_as='*'
OR send_as IN (
SELECT CONCAT('@',target_domain) FROM alias_domain
WHERE alias_domain = 'test.org')
OR send_as IN (
SELECT CONCAT('user+test','@',target_domain) FROM alias_domain
WHERE alias_domain = 'test.org')
AND logged_in_as NOT IN (
SELECT goto FROM alias
WHERE address='[email protected]')
UNION
SELECT username FROM mailbox, alias_domain
WHERE alias_domain.alias_domain = 'test.org'
AND mailbox.username = CONCAT('user+test','@',alias_domain.target_domain)
AND (mailbox.active = '1' OR mailbox.active ='2')
AND alias_domain.active='1'If its executed with SELECT goto FROM alias
WHERE address='[email protected]'
AND active='1'
AND (domain IN
(SELECT domain FROM domain
WHERE domain='test.org'
AND active='1')
OR domain in (
SELECT alias_domain FROM alias_domain
WHERE alias_domain='test.org'
AND active='1'
)
)
UNION
SELECT logged_in_as FROM sender_acl
WHERE send_as='@test.org'
OR send_as='[email protected]'
OR send_as='*'
OR send_as IN (
SELECT CONCAT('@',target_domain) FROM alias_domain
WHERE alias_domain = 'test.org')
OR send_as IN (
SELECT CONCAT('user','@',target_domain) FROM alias_domain
WHERE alias_domain = 'test.org')
AND logged_in_as NOT IN (
SELECT goto FROM alias
WHERE address='[email protected]')
UNION
SELECT username FROM mailbox, alias_domain
WHERE alias_domain.alias_domain = 'test.org'
AND mailbox.username = CONCAT('user','@',alias_domain.target_domain)
AND (mailbox.active = '1' OR mailbox.active ='2')
AND alias_domain.active='1'Result: Its because of the You might try with following query in SELECT goto FROM alias
WHERE address='%s'
AND active='1'
AND (domain IN
(SELECT domain FROM domain
WHERE domain='%d'
AND active='1')
OR domain in (
SELECT alias_domain FROM alias_domain
WHERE alias_domain='%d'
AND active='1'
)
)
UNION
SELECT logged_in_as FROM sender_acl
WHERE (NOT INSTR('%s', '+') AND send_as='@%d')
OR send_as='%s'
OR (NOT INSTR('%s', '+') AND send_as='*')
OR send_as IN (
SELECT CONCAT('@',target_domain) FROM alias_domain
WHERE alias_domain = '%d')
OR send_as IN (
SELECT CONCAT('%u','@',target_domain) FROM alias_domain
WHERE alias_domain = '%d')
AND logged_in_as NOT IN (
SELECT goto FROM alias
WHERE address='%s')
UNION
SELECT username FROM mailbox, alias_domain
WHERE alias_domain.alias_domain = '%d'
AND mailbox.username = CONCAT('%u','@',alias_domain.target_domain)
AND (mailbox.active = '1' OR mailbox.active ='2')
AND alias_domain.active='1'The above SQL is checking with |
|
@monofox Oh, I missed your message. I'll have a look into it over the weekend and will give feedback. Many thanks! |
|
We should evaluate a proper fix. Perhaps a piped map in Postfix can help too. Like stopping after a given result. |
hmm ... is there a way to override the |
If i do it, i go into the container change file and make a |
Looks like that didn't worked. But have to dig further when back at home with debugging mode. |
Looks like sending mail fails in this case in general because of a syntax error: |
Yes, copy & paste error. The |
|
Okay ... that works well. Now I'm asking me, how I can implement a temporary workaround. Using a script works well to replace the config and reload postfix inside the container manually. Placing this script inside |
As i've also mailman integrated by me, i had to override some existing variables in extra.cf. In theory, you could do the same for your |
|
Hi, I just wanted to report that this is broken again with my changes 6 weeks ago, I've to dig into it later when got some free time. |
|
It was probably just overwritten. I will try to find a proper fix. Sorry. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
github-actions
bot
added
the
stale
|
Hmmm… I don‘t wanna getting annoying… but is there a chance getting this fixed? Is there anything that I can do to increase the chance? :/ |
github-actions
bot
removed
the
stale
|
Just wanted to notice you, that it looks like this issue seems to be not an issue anymore at least with 8116bf5: I removed the workaround mentioned in #4022 (comment), in my |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
milkmaker
added
the
stale
|
What is the current state of this? This feature would be useful sometimes, especially since you cannot create an alias pointing to a tagged mail address. I'd like to send mails from a tagged address such that if the recipient responds, it's automatically sorted instead of always having to use my main mail address (one more example: Github allows comments via mail, but only from addresses on your account and I have a tagged address stored in my account) |
|
As I stated in #4022 (comment), this seems to be fixed and is no issue anymore (at least on my setup). |
|
Just updated to the latest available mailcow. Still getting "not owned by $mailbox", so no, for me it still doesn't work natively |
|
Updated to latest |
|
There must be something I'm doing wrong then or which must be misconfigured, here's the error from thunderbird:
As far as I am aware I have no modifications running aside from |
Prior to placing the issue, please check following: (fill out each checkbox with an
Xonce done)Summary
When trying to send with a tagged address (e.g.
[email protected]->[email protected]), the server rejects that mail as if the address weren’t owned by the mailbox/user.Logs
Reproduction
Create a new mailbox with default permissions.
Try to send a mail from a tagged address through this new user.
System information
docker version)docker-compose version)The text was updated successfully, but these errors were encountered: