Sample config files on the server

[e-fu]

can you provide example config files for postfixes main.cf and dovecot?

[rahul286]

I asked same in #1

Please check vendor/config/postfix/samples/

[e-fu]

yes, i saw that files. but still missing dovecot examples.

added this to postfix main.cf:

Enabling SMTP for authenticated users, and handing off authentication to Dovecot

smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes

smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination

virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-domains-maps.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf virtual_transport = mysql:/etc/postfix/mysql-virtual-transports.cf virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-domain-aliases.cf mysql:/etc/postfix/mysql-virtual-user-aliases.cf

but not sure if thats right. Also having problems with dovecot.

postfy looks great, but i think a lot of people just have problems to implement it on server side, mainly if they are no sysadmins...

[rahul286]

Got your point.

You may check my sample config - http://rtcamp.com/tutorials/mail/server/postfix-dovecot-ubuntu/ My sample config is not using posty at the moment but might help.

[e-fu]

thanks, will see if i get it running.

[lweis]

Hey,

there are still problems?

We are currently working with high pressure on the new release of posty_API, posty_Client, posty_webUI, posty_Chef and an installation howto!

the current roadmap can be found at http://posty-soft.org/roadmap.pdf

Cheers

the posty team

[e-fu]

got it to run, but w/o domain aliases. documentation or example conf files would be great. great project!

[chicobico]

A short example with the domain_aliases part in the main.cf. With this configuration the domain_aliases part works on my test machine. I hope this helps.

virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual-user-aliases.cf, proxy:mysql:/etc/postfix/mysql-virtual-domain-aliases.cf virtual_transport = dovecot transport_maps = proxy:mysql:/etc/postfix/mysql-virtual-transports.cf

If the problem still occurs please give me more details and reopen the issue.

[e-fu]

@chicobico yes, it works no internally when sending the email per smtp on the same server. but sending it from outside servers: NOQUEUE: reject: RCPT from nk11p03mm-asmtpout002.mac.com[17.158.232.237]: 554 5.7.1 efries@inetpeople.sg: Relay access denied;

[130] $ posty-client summary ✘ VirtualDomainAliases 1 VirtualDomains 2 VirtualUserAliases 0 VirtualUsers 2

i can send my dovevot.conf if someone is interested.

cheers E

[e-fu]

just for double check, is this right for dovecot? password_query = SELECT password FROM users_view WHERE email = '%u'

Still no virtual domains working.

[e-fu]

moved to: http://stackoverflow.com/questions/20020901/posty-api-config-files-for-postfix-and-dovecot

[chicobico]

Hi efries,

sorry for the late reply. Here are the actual dovecot-sql.conf querys. These are the queries from the latest api version with quota. The other problem with the detected relay is the next problem i trying to fix.

password_query = SELECT email as user, password, CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/') as userdb_home, 5000 as userdb_uid, 5000 as userdb_gid, quota FROM users_view WHERE email='%u';

user_query = SELECT email as user, CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/') as home, 5000 as uid, 5000 as gid, CONCAT('*:storage=', quota, 'B') AS quota_rule FROM users_view WHERE email = '%u';

[chicobico]

The Relay access denied occurs only on a domain alias address? Or on all addresses from outside?

[e-fu]

only on the domain alias from outside. sending with the intern smtp is working.

[avinashtanniru]

check this error.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.254.10/posty_api/api/v1/domains. This can be fixed by moving the resource to the same domain or enabling CORS.