Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not setting client_* symbols when using Postfix #50

Open
amartin-git opened this issue Jan 27, 2022 · 3 comments
Open

Not setting client_* symbols when using Postfix #50

amartin-git opened this issue Jan 27, 2022 · 3 comments

Comments

@amartin-git
Copy link

Hello,

I'm currently testing pymilter with Postfix and have noticed that the client_* symbols are not being set:

self.getsymval('{client_addr}') None
self.getsymval('{client_name}') None
self.getsymval('{client_port}') None

Postfix states that the symbols are set:

http://www.postfix.org/MILTER_README.html

Is this something that's introduced by pymilter or do I need to dig into postfix/libmilter? Thanks.

@kitterma
Copy link
Collaborator

Before sdgathman asks, I use pymilter with postfix, but I don't use those macros, so I can't comment on this.

@amartin-git
Copy link
Author

My apologies - figured out that the client_* macros aren't enabled by default in postfix and they have to be manually added to the milter_*_macros configuration directives. Example (in postfix main.cf):

milter_connect_macros = j {daemon_name} {daemon_addr} {client_addr} {client_name} {client_port} v _

@sdgathman
Copy link
Owner

This bug reminds me that this project needs a README-postfix.md. I will reopen as a documentation bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants