smtpd_sasl load balance

Hello, is it possible to configure configure haproxy to work with postfix sasl and dovecot auth like this: clients -> 25:postfix -> 20025:haproxy -> 20025:auth-backend-1, 20025:auth-backend-2 The configuration I have now gives me this error when haproxy change backend server, and when server

Re: smtpd_sasl load balance

There is not mentioned if it will or will not work, that's why I experimented :) 2015 kov. 28 01:50 "Wietse Venema" rašė: > Edgaras Luko?evi?ius: > [ Charset windows-1252 converted... ] > > Hello, > > > > is it possible to configure configure haproxy to work with postfix sasl > and dovecot auth l

check_policy_service mysql lookup

Hi, i’m trying to do quota limits by this tutorial: https://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ I have all the parts working, but in the tutorial only one policy service is used: > smtpd_recipient_restrictions = >... >check_policy_service inet:mailstore.example.com

cleanup/qmgr timeouts

Hello, I’m getting a lot of these messages. Anyone have an idea what is wrong? Should I tune some settings or what? mail-backend-1 postfix/cleanup[24838]: warning: unix_trigger_event: read timeout for service public/qmgr mail-backend-2 postfix/cleanup[14219]: warning: unix_trigger_event: read

Re: cleanup/qmgr timeouts

related? On 22 Apr 2015, at 13:00, Edgaras Lukoševičius wrote: > Hello, > > I’m getting a lot of these messages. Anyone have an idea what is wrong? > Should I tune some settings or what? > > mail-backend-1 postfix/cleanup[24838]: warning: unix_trigger_event: read > timeo

Re: cleanup/qmgr timeouts

local_destination_concurrency_limit = 20 dovecot_destination_recipient_limit = 1 dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient} On 22 Apr 2015, at 13:09, Edgaras Lukoševičius wrote

Re: cleanup/qmgr timeouts

Default limit is: qmgr_message_active_limit = 2 I don’t have that many messages in active queue at any time. And the only way to avoid this warning is to either throttle new messages of try to deliver them faster? On 22 Apr 2015, at 14:13, Wietse Venema wrote: > Edgaras Luko?evi?ius: > [

Don't expand aliases before filer

Hello, some of the recipients have multiple aliases. Let’s say 10. If they receive email, aliases are expanded and one message is divided to 10. So instead of 1 there is 10 messages for content filter. How can I make postfix expand aliases only after content filter or, if content filter is not

virtual_alias_maps for non-existent virtual_mailbox_maps

Hello, I have aliases for recipients in virtual_alias_maps that do not exist in virtual_mailbox_maps. This is for users who want to *only* have forwarding without owning any mailboxes. By the documentation virtual_mailbox_maps are checked before virtual_alias_maps and so I get "Recipient addres

Re: virtual_alias_maps for non-existent virtual_mailbox_maps

Alright. Let's try again. main.cf 2525_end_of_data_restrictions = permit_mynetworks 2525_recipient_restrictions = reject_unauth_pipelining reject_unknown_recipient_domain permit_mynetworks reject_rbl_client bl.spamcop.net reject_authenticated_sender_login_mismatch ch

Re: virtual_alias_maps for non-existent virtual_mailbox_maps

> smtpd pass - - n - 500 smtpd This one. May 22 09:10:44 mx1 postfix/smtpd[1757]: NOQUEUE: reject: RCPT from xx..xxx[ddd.ddd.ddd.]: 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table; from= to= proto=ESMTP helo= 2015-05

sender_dependent_default_transport_maps for aliases?

Hello, i have few outbound transports in master.cf like this: outbound1 unix - - n - - smtp -o syslog_name=outbound1 -o smtp_helo_name=reverse.do.main -o smtp_bind_address=X.X.X.X outbound2 unix - - n - -

Re: sender_dependent_default_transport_maps for aliases?

All this is done to put users into our own "classes" (eg. spammers vs. non-spammers). Because there are clean and dirty IP pools and if we see that user *may be* abusing email (or any other) system we want to put them to "dirty" pool for some time. While this works with ordinary senders, it doe

Re: sender_dependent_default_transport_maps for aliases?

On 22/07/15 18:05, Viktor Dukhovni wrote: On Wed, Jul 22, 2015 at 05:55:04PM +0300, Edgaras Luko?evi?ius wrote: All this is done to put users into our own "classes" (eg. spammers vs. non-spammers). If your autheneticated submission user is spamming, suspend their ability to send outbound ema

Re: sender_dependent_default_transport_maps for aliases?

Thanks. On 22/07/15 18:49, Wietse Venema wrote: Edgaras Luko?evi?ius: All this is done to put users into our own "classes" (eg. spammers vs. non-spammers). Because there are clean and dirty IP pools and if we see that user *may be* abusing email (or any other) system we want to put them to "dir