SASL auxprop ldapdb result attribute

Hi, I want to have postfix do sasl with auxprop ldapdb and not with dovecot anymore. Reason: I have a rnsMSDovecotEnable flag in ldap to disable imap/pop3 accounts. But this also would disable postfix as well, which I do not want for accounts that just relay mail over postfix. I need to have this

Re: ip reputation

On Tue, 2011-01-25 at 15:25 +0100, Bissio2000 wrote: > Hi all, > > we have some problem with our ip reputation on other provider. We are using > our postfix server as delivery server for some mailing lists (about > 5000/8000 users); after a few days the destination providers (as hotmail, or > yah

Re: SASL auxprop ldapdb result attribute

> Now how can I tell auxprop ldapdb to ask for this attribute and not > userPassword? > > I know this question is somewhat off topic. But which is the right > place? Guess post_masters_ for sure can help me :-) Sometimes you just write to a mailing list, because you did not find a solution. And y

Re: postfix/trivial-rewrite: warning: mysql query failed: Illegal mix of collations

John Fawcett: > Claudio > the problem is happening because your column definition for "domain" > column has character set latin1 (which by default has collation > latin_swedish_ci) and the data being passed from postfix is in utf8 > (which by default has collation utf8_general_ci). Actually, there

Re: Blacklist per-domain

On Wed, Jan 26, 2011 at 6:20 PM, Victor Duchovni wrote: > On Wed, Jan 26, 2011 at 06:14:26PM +0100, polloxx wrote: > >> > > We want to implement blacklisting sender email addresses on a per-domain >> > > basis.  I know it can be done by Amavis but I would like to implement >> > > this directly in

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

On 01/26/2011 06:39 PM, Victor Duchovni wrote: > On Wed, Jan 26, 2011 at 09:31:48AM +0100, J4K wrote: > >> # ps auxwww|grep master >> root 1333 0.0 0.0 37160 2416 ?Ss Jan20 0:01 >> /usr/lib/postfix/master > If there is only one instance of Postfix running, and it was started 5

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

J4K: > On 01/26/2011 06:39 PM, Victor Duchovni wrote: > > On Wed, Jan 26, 2011 at 09:31:48AM +0100, J4K wrote: > > > >> # ps auxwww|grep master > >> root 1333 0.0 0.0 37160 2416 ?Ss Jan20 0:01 > >> /usr/lib/postfix/master > > If there is only one instance of Postfix running, a

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

On 01/27/2011 03:03 PM, Wietse Venema wrote: > J4K: >> On 01/26/2011 06:39 PM, Victor Duchovni wrote: >>> On Wed, Jan 26, 2011 at 09:31:48AM +0100, J4K wrote: >>> # ps auxwww|grep master root 1333 0.0 0.0 37160 2416 ?Ss Jan20 0:01 /usr/lib/postfix/master >>> If

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

> There was no klunky.co.uk in the main.cf:mydestination setting that > you showed, therefore you were showing the wrong main.cf file. > > To find all main.cf files on the system: > > # find / -name main.cf -ls J4K: > # find / -name main.cf -ls > 2625638 -rw-r--r-- 1 root root

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

On 01/27/2011 04:02 PM, Wietse Venema wrote: >> There was no klunky.co.uk in the main.cf:mydestination setting that >> you showed, therefore you were showing the wrong main.cf file. >> >> To find all main.cf files on the system: >> >> # find / -name main.cf -ls > J4K: >> # find / -name main.cf

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

> mydestination = localhost.localdomain, localhost > myhostname = klunky.co.uk ... > virtual_mailbox_domains = > proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf Just for kicks, try: postconf -e "mydestination =" postfix reload Then check again. -- Ralf Hildebrandt Geschäftsbereich

Re: postfix/trivial-rewrite[ ]: warning: do not list domain klunky.co.uk in BOTH mydestination and virtual_mailbox_domains

J4K: > mydestination = localhost.localdomain, localhost There is no way that Postfix will log that klunky.whatever.uk is listed in mydestination. Take it up with your helpful up-stream Postfix maintainer. Wietse

Work-in-progress: trickle attack defense

I added the following entry to the wip.html file on the Postfix website. Wietse Trickle attack defense Trickle attacks are old, but have received attention recently in the context of web servers. The idea is that an attacker sends a request slowly, for example, one byte at a time. Since

Re: migrate postfix and mail queue

Thanks for your response. I read the RELEASES_NOTES and my upgrade was fine. Cheers Daniel Madaoui --On 26 janvier 2011 07:04:11 -0500 Wietse Venema wrote: Daniel Madaoui: if I migrate from postfix 2.2.7 to 2.8.0 postfix, what 's up with the mails contained in the mails queues. Will th

Re: Blacklist per-domain

On 1/27/2011 7:22 AM, polloxx wrote: On Wed, Jan 26, 2011 at 6:20 PM, Victor Duchovni wrote: On Wed, Jan 26, 2011 at 06:14:26PM +0100, polloxx wrote: We want to implement blacklisting sender email addresses on a per-domain basis. I know it can be done by Amavis but I would like to implement

Re: Work-in-progress: trickle attack defense

Wietse Venema wrote: I added the following entry to the wip.html file on the Postfix website. Wietse Trickle attack defense The postscreen daemon, available with Postfix 2.8 and later, already implements time limits to receive one complete SMTP command line. Postscreen uses a default t

Re: Work-in-progress: trickle attack defense

Randy Ramsdell wrote: Wietse Venema wrote: I added the following entry to the wip.html file on the Postfix website. Wietse Trickle attack defense The postscreen daemon, available with Postfix 2.8 and later, already implements time limits to receive one complete SMTP command line. Postscre

Re: Work-in-progress: trickle attack defense

On Thu, Jan 27, 2011 at 12:04:26PM -0500, Randy Ramsdell wrote: >> 300s for each line as in: mail from: blah ---> 300s? > > What I am getting at here is that the attack will still succeed if using it > for DOS. I am not trying trivialize this work, but understand how this will > stop an attack v

Re: basic question: permit SMTP from recipients or whitelist ?

On 1/27/11 7:11 AM, sunhux G wrote: I'm setting up a postfix mailserver. Only a handful (of about 6 domains , ie x...@dsta.gov.sg , x...@starnet.gov.sg , x...@ncssmsonbehalf.com.sg , x...@accenture.com

postfix sasl auth (SMTP auth)

hi friend, I have a postfix server install on my work, and I have too configured a sasl auth mechanismus, my question is, how can I say to postfix tha use only the SMTP auth mechanismus. Why i ask this question. Because if i use a mail client without any autentication machanismus to send mails the

Re: basic question: permit SMTP from recipients or whitelist ?

On Thu, Jan 27, 2011 at 02:11:02PM +0800, sunhux G wrote: > I'm setting up a postfix mailserver. Only a handful (of about 6 domains , > ie x...@dsta.gov.sg , x...@starnet.gov.sg, x...@ncssmsonbehalf.com.sg , > x...@accenture.com ) are allowed to email to my postfix server. When you say that on

about sender_login_maps

Hello Postfix's main.cf has a feature that is reject_sender_login_mismatch. I use this feature. But I 'd like to be special mail users which can send any mail despite reject_sender_login_mismatch. I have a domain alias . for example @domain.comand @smtp.domain.com I would like everyone in

Re: Blacklist per-domain

Le 27/01/2011 14:22, polloxx a écrit : > On Wed, Jan 26, 2011 at 6:20 PM, Victor Duchovni > wrote: >> On Wed, Jan 26, 2011 at 06:14:26PM +0100, polloxx wrote: >> > We want to implement blacklisting sender email addresses on a per-domain > basis. I know it can be done by Amavis but I would

Re: postfix sasl auth (SMTP auth)

On Thu, Jan 27, 2011 at 04:08:20PM -0500, Leonel Florin Selles wrote: > ... if I use a mail client without any > authentication mechanisms to send mails the server sends the mails, and I > need that the only way to send mails be the SMTP auth. To enable SASL: http://www.postfix.org/SASL_READ

Re: about sender_login_maps

On Thu, Jan 27, 2011 at 11:17:45PM +0200, Bulent Malik wrote: > I have a domain alias . for example @domain.comand @smtp.domain.com > I would like everyone in @smtp.domain.comto send any mail to anywhere > with @domain.com > > I have a smtpd_sender_login_maps > cat smtpd_sender_logi

Multiple Milters Separator?

If we're using mutliple milters (with smtpd_milters), is it appropriate to separate them with: a space? smtpd_milters = inet:localhost:10035 inet:localhost:10036 a comma? smtpd_milters = inet:localhost:10035,inet:localhost:10036 a comma and a space? smtpd_milters = inet:localhost:10035, inet:loc

Re: Multiple Milters Separator?

Steve Jenkins: [ Charset ISO-8859-1 unsupported, converting... ] > If we're using mutliple milters (with smtpd_milters), is it > appropriate to separate them with: > > a space? > smtpd_milters = inet:localhost:10035 inet:localhost:10036 > > a comma? > smtpd_milters = inet:localhost:10035,inet:loc

Disclaimer corruption with alterMIME

I've got Postfix and alterMIME configured on Ubuntu 10.10 Everything is working perfectly except that the disclaimer that is inserted by alterMIME is inserting an equal sign followed by a space. This is not there in the disclaimer.txt file. How do I fix this? Thank you,

Re: Disclaimer corruption with alterMIME

On Thu, Jan 27, 2011 at 08:39:50PM -0600, Michael Westman wrote: > I've got Postfix and alterMIME configured on Ubuntu 10.10 Everything > is working perfectly except that the disclaimer that is inserted by > alterMIME is inserting an equal sign followed by a space. This is not > there in the dis