Re: randmap getting precedence in transport_maps?

Em 25/02/2022 11:39, Wietse Venema escreveu: Nicolas JEAN: Tested: adding above randmap also 'supersedes' a local_transport_map containing the domain-matching "my.domain virtual:"... I don't understand how "my.domain :" and "my.domain virtual:" can have di

Re: randmap getting precedence in transport_maps?

Em 24/02/2022 17:14, Wietse Venema escreveu: Nicolas JEAN: Having "my.domain :" or "my.domain lmtp:unix:private/dovecot-lmtp" doesn't modify default behaviour (set by virtual_transport = lmtp:unix:private/dovecot-lmtp), and yields such a log line: to=, relay=my.domain[

Re: randmap getting precedence in transport_maps?

Em 24/02/2022 14:03, Wietse Venema escreveu: Nicolas JEAN: Feb 24 15:18:38 my.domain postfix/smtp[4628]: B08949E76C: to=, relay=relay2.com[2.2.2.2]:587, delay=0.76, delays=0.04/0.01/0.38/0.33, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 29A7484FC6) If I'm correct, thecontact@my.domain

Re: randmap getting precedence in transport_maps?

Hi Wietse, Thanks for your quick answer! Wietse Venema: /etc/postfix/local_transport_map my.domain ?? : .my.domain ? : (where myhostname = myorigin = virtual_mailbox_domains = my.domain) Did notice any warnings from Postfix with "do not list domain XXX in both YYY and ZZZ"? Not

randmap getting precedence in transport_maps?

Hi everyone, I'm trying to implement load balancing thanks to /transport_maps/ and /randmap/ as described in postfix 3.0 release notes[1]. /etc/postfix/local_transport_map my.domain    : .my.domain   : (where myhostname = myorigin = virtual_mailbox_domains = my.domain) Then I have in

Re: The historical roots of our computer terms

Le 07/06/2020 à 20:25, Ralph Seichter a écrit : > Sources, please. A colleague of Kenyan heritage told me that he is, in his > own words, "sometimes amused but mostly annoyed by the American political > correctness movement". To my European eyes (living in France, born in Austria, Hungarian

Postfix restrictions

Hi, I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7). SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami. Besides the official Postfix documentation, I've read a few articles about Postfix spam restrictions, namely these :

RE: Virtual Alias Domains

ovni Envoyé : samedi 28 septembre 2019 18:18 À : postfix-users@postfix.org Objet : Re: Virtual Alias Domains On Sat, Sep 28, 2019 at 03:55:04PM +, Nicolas Breuer wrote: > I'm not sure you understand the issue. Sadly, you've got the wrong end of the stick. Your logs start with: Sep

RE: Virtual Alias Domains

No. I'm not sure you understand the issue. Normally both the email must be in virtual file & domain in virtual_domain file. If the domain is not present in domain file, should be rejected with (MX loops back to me) If the email is not in virtual, should be rejected with (user unknow) I tried to

RE: Virtual Alias Domains

t;!/file/name" is supported only in Postfix version 2.4 and later. -Message d'origine- De : owner-postfix-us...@postfix.org De la part de Wietse Venema Envoyé : samedi 28 septembre 2019 15:47 À : Postfix users Objet : Re: Virtual Alias Domains Nicolas Breuer: > > Hello, >

RE: Virtual Alias Domains

Hello, I'm running Postfix 3. I try to add a mailbox without aliasing the domain. The delivery is accepted, should not be because the domain is not in local domain file ? virtual_alias_domains = /etc/postfix/local-host-names virtual_alias_maps = hash:/etc/postfix/virtual

Re: Need clarification about Content-Type on email

the ehlo command Postfix SMTP server announces SMTPUTF8 support in the EHLO response. Good luck. Nicolas. On 22 November 2017 at 08:46, wodel youchi <wodel.you...@gmail.com> wrote: > Hi, > > I need some clarification about Content-Type on an email. > > Who does fix the

Re: Conditional sender rewrite based on recipient address

El 2017-11-03 15:15, Noel Jones escribió: On 11/3/2017 6:26 AM, nico...@devels.es wrote: El 2017-11-03 11:05, wie...@porcupine.org escribió: Noel Jones: On 11/2/2017 7:48 AM, nico...@devels.es wrote: > Hi, > > I'm running Postfix 2.9.6 and I'm trying to do a conditional sender > rewrite based

Re: Conditional sender rewrite based on recipient address

El 2017-11-03 11:05, wie...@porcupine.org escribió: Noel Jones: On 11/2/2017 7:48 AM, nico...@devels.es wrote: > Hi, > > I'm running Postfix 2.9.6 and I'm trying to do a conditional sender > rewrite based on recipient address. Machine sends e-mails as > r...@internal-domain.com by default, but

Conditional sender rewrite based on recipient address

Hi, I'm running Postfix 2.9.6 and I'm trying to do a conditional sender rewrite based on recipient address. Machine sends e-mails as r...@internal-domain.com by default, but if the recipient is u...@external-domain.com I want to rewrite sender to be r...@different-domain.com. To do so,

Re: Extracting delivery attempts from log files

There also this project: https://sourceforge.net/p/x-itools/wiki/Home/ Le 22/08/2016 à 03:42, Steve Atkins a écrit : On Aug 21, 2016, at 5:13 AM, Wietse Venema wrote: Robert Schetterer: Am 21.08.2016 um 05:10 schrieb Steve Atkins: I find I need to extract a list of

Negative look-ahead assertions in maps

Hi, What would be the equivalent of negative look-ahead assertions in Postfix's map files? I have: main.cf: sender_canonical_maps = regexp:/etc/postfix/canonical_maps /etc/postfix/canonical_maps: /^((?!foo[0-9]+).*)@domain1.com$/ ${1}@domain2.com I want that any mail that comes

Re: Negative look-ahead assertions in maps

El 2016-02-04 13:24, wie...@porcupine.org escribió: nico...@devels.es: Hi, What would be the equivalent of negative look-ahead assertions in Postfix's map files? 1) Postfix has are table-driven features such as canonical_maps, alias_maps, etc. 2) These features use table lookup

Re: sender_canonical_maps for incoming e-mails

El 2016-01-19 18:37, wie...@porcupine.org escribió: Nicol?s: Hi, We have a filter located outside our organization for outgoing mail which rewrites the Return-Path to their domain, in the form: username=abc@theirdomain.com. Once the filter processes the message, it's forwarded to the

Re: blocking compromised sasl users ?

Is 104.200.78.121 listed in your $permit_mynetworks parameter, or a CIDR that contains it? Did you postmap /etc/postfix/sasl_access? Did you try c...@dom.org.au as entry? Did you try cas@ as entry? Regards, Nicolás El 2015-10-07 14:47, Voytek escribió: On Thu, October 8, 2015 12:42 am,

Re: Block specific outgoing email

El 2015-08-26 11:41, Antonio Alberola escribió: Hello, I would like know if it's possible to block outgoing emails with a specific subject, but only if the email is sent to a specific recipient. Thanks, Antonio Alberola It is possible but you will need to build your own filter to do that

Re: pcre matching

El 2015-08-18 17:33, Alex escribió: Hi, If that is the preferred method, what is the real purpose of header_checks? Solely for Subject and To? Even more useful than checking the Subject, I use header_checks to check some properties on attachments. In fact, I've picked Wietse's example on

Re: pcre matching

El 2015-08-18 16:15, Alex escribió: Hi, I'm trying to match a pattern in a header_checks pcre file and can't figure out why it's not matching. In /etc/postfix/header_checks.pcre, I have: /^From:.*exampleuser@gmail\.com$/ REJECT # postmap -q 'exampleuser' pcre:/etc/postfix/header_checks.pcre #

Re: How to block annoying/dangerous smtpd connections?

Those lines make no harm, although they may become annoying. I guess that an external tool like Fail2Ban can be very helpful here, but be careful to establish an ample enough policy in the Fail2Ban service to not block your own users if they fail to authenticate against your mail server.

Re: header_checks not working

El 2015-03-12 12:31, Krinninger, Reinhold escribió: Hello, i use this header_check: I assume that you're actually using header_checks (ended in **s**) and that your table type is regex: in order this to work. /etc/postfix/header_checks: /^From: (?!.*\root).*\@itmu\-smtp2\.br\.de\/

Re: Chained content filters

El 2015-03-09 21:31, Roger Walters escribió: Hello, I have a few chained content filters based on pipe, so when the first script ends its task, it sends the processed headers to the second script and so on. It is clear how to get the content back to Postfix as an input, using the sendmail

Re: count sending email per month

Hello, The X-Itools ELSE (https://sourceforge.net/p/x-itools/wiki/) can also do it but it's maybe a too big thing for what you want to do. Version 0.9.19 has been released yesterday evening. Best regards Nicolas PGP fingerprint: 5F35 862E 00E1 D774 7FA4 3A71 EBED FA58 58C6 45D2 Le 25/02/2015

E-mail Log Search Engine and GreyLSE Postfix Policy Server v0.9.19 released

Server has a built-in *SPF engine*, and SPF rules can be implemented using the ELSE Web user Interface. It's also updated for Postfix v3. - The *ELSE* implements *GeoIP* (from MaxMind) and *Google MAPS*: it's possible to see the location of any IP Address on a google MAP. Enjoy :) Nicolas -- PGP

Re: Add header based on number of recipients

- Have you identified the e-mail server having those compromised accounts? If yes forbid this server to relay using your Postfix servers. If you don't want or cannot do it... - Then have you identified what e-mail accounts exactly are compromised? If yes temporarily close or disabled those

E-mail Log Search Engine v0.9.18 released

*, or - *a mix of Postfix/Anvil, Fail2ban, Firewall, Monitoring, Reporting* Enjoy :) -- Nicolas attachment: hahnn.vcf

Re: How to Configure forward (redirect) for specific from email address

regarding the recipient email address... Well, a kind of... Or if I understand you well, if your goal is to send all email flow of u...@test.com sender systematically to the same recipient (user1), you probably need a routing decision taken only on the sender email address... Regards, Nicolas Le 26

Re: emporarily block all messages from a particular IP

relay of my work lab was hit by this last week. -- Nicolas

Re: Simultaneously specifying both a recipient and a transport?

not sure what I should do if one destination suceeds while the other one fails… Cheers, -- Nicolas Boullis

Re: Simultaneously specifying both a recipient and a transport?

crashes, and the archive copy is never sent. Point taken, but it’s still much better than the current situation where up to 24 hours of e-mail may be lost… Cheers, -- Nicolas Boullis

Simultaneously specifying both a recipient and a transport?

, and makes it somewhat more complex to reimport that backup as I have to rewrite the recipients. So is there a way I can ask Postifix, in my recipent_bcc map that the message hould be copied to sameu...@example.net *with the bsmtp transport*? Cheers, -- Nicolas Boullis

Re: Simultaneously specifying both a recipient and a transport?

regards, -- Nicolas Boullis

Re: pflogsum don't count postscreen rejects

Hello there, I'll also take any material or log file snippet provided about postscreen to implement a parser in the ELSE project, and generate any usefull stats. Regards, Nicolas HAHN Le 29/08/2014 01:57, Jim Seymour a écrit : On Mon, 25 Aug 2014 16:12:12 +0200 li...@rhsoft.net li

Re: pflogsum don't count postscreen rejects

3 | HANGUP | 6 5 | PASS NEW | 1 It's just incredible the number of emails dropped by DNSBL!! Regards, Nicolas HAHN Le 29/08/2014 08:40, Nicolas HAHN a écrit : Hello there, I'll also take any material or log file snippet provided about postscreen to implement a parser in the ELSE

Re: Automated personal whitelist (?)

you sent me also, in order to not pollute to much the Postfix mailing list. If any other are interested, let me know. Best regards, Nicolas HAHN Le 21/08/2014 23:03, Ronald F. Guilmette a écrit : Is there anything which is either a part of, or that works with Postfix that is capable

Re: Automated personal whitelist (?)

of that in my greylister... Best regards, Nicolas Le 21/08/2014 23:30, Noel Jones a écrit : On 8/21/2014 4:03 PM, Ronald F. Guilmette wrote: Is there anything which is either a part of, or that works with Postfix that is capable of automagically maintaining a personal whitelist of specific e-mail

Re: SASL authentication failure: cannot connect to saslauthd server

El 2014-08-12 22:29, pavel degtiarev escribió: Hi there, I know this is a common error but I swear I checked everything, yet still get that error trying to setup Postfix with Cyrus SASL on Debian wheezy. Here’s my confgs: /etc/postfix/sasl/smtp.comf: Be careful with the extension.

Postfix log analyzer tool V0.9.17 released

, Nicolas attachment: hahnn.vcf

New Postfix log analyzer tool V0.9.16 released (PostgreSQL DB 9.2.x based)

regards, Nicolas

Re: Google rejecting IPv6 mails

catches up. I did half of this. On my home server, I disabled IPv6 on the postfix smtp client. The smtp server still accepts incoming IPv6 connections. I did not see any problem since then. -- Nicolas

Re: disable ipv6 when sending to gmail ?

On Tue, Aug 20, 2013 at 02:23:21PM -0400, Wietse Venema wrote: Nicolas KOWALSKI: I am not able to have an IPv6 rDNS record with my ISP, only an IPv4 one. I guess this is why it works when using IPv4 (tested by forcing inet_protocols = ipv4), and does not work any more with IPv6

Re: disable ipv6 when sending to gmail ?

for the mail to be retried to another host? 450 some-text-here or 450-subcode some-text-here ? Thanks, -- Nicolas

Re: disable ipv6 when sending to gmail ?

On Wed, Aug 21, 2013 at 09:15:46AM -0400, Wietse Venema wrote: Nicolas KOWALSKI: On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote: Argh. You need to replace the 5.X.X. This pattern replaces both fives just to be sure. /^5(\d\d )5(.*your:ipv6:addr:here

Re: disable ipv6 when sending to gmail ?

On Wed, Aug 21, 2013 at 09:15:46AM -0400, Wietse Venema wrote: Nicolas KOWALSKI: On Wed, Aug 21, 2013 at 06:44:55AM -0400, Wietse Venema wrote: Argh. You need to replace the 5.X.X. This pattern replaces both fives just to be sure. /^5(\d\d )5(.*your:ipv6:addr:here

disable ipv6 when sending to gmail ?

IPv4 interface? Thanks, -- Nicolas

New Postfix log analyzer tool V0.9.15 released (PostgreSQL DB 9.2.x based)

/files/X-Itools%20releases/E-mail%20Log%20Search%20Engine/ *Please note that all releases of this software are considered RD. Use it at your own risks.* Kind regards, Nicolas attachment: hahnn.vcf

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

Le 24 avr. 2013 à 20:00, Wietse Venema wie...@porcupine.org a écrit : Nicolas HAHN: The archietcture is not a good excuse for me, I'm sorry. As a coder, allowing a software to start despite the fact there is a FATAL is a total non-sens. And saying finally that is just a daemon which

Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

is happening? Does somebody had this issue? Is there a known limit we cannot go above for message_size_limit setting in main.cf? Thanks for your help. Regards, Nicolas This message was sent using IMP, the Internet Messaging Program.

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

Nicolas HAHN: Does somebody knows what is happening? no because you missed to send any log-information maybe to less memory to proceed messages with 150 MB This message was sent using IMP, the Internet Messaging Program.

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

Postfix memory usage does not depend on message size. Far more likely some filter has message size issues, or perhaps mailbox_size_limit has not been raised to match, or the OP failed to reload Postfix, so that the message size limit was different in some processes. Each time I've reloaded

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

by itself when starting (or when configuration is reloaded) between various inter-dependent configuration settings, and display in the logs at least some warnings when such kind of issue is detected :) Best regards, Nicolas

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

1. Don't send bounces to postmaster, just generate and read log summaries that may highlight aggregate problems with your mail stream. notify_classes = This applies to any MTA handing mail for a large number of users, it is fine to have postmaster notices for a machine

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

, and REFUSE to start because of fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit. Don't you think? But I learn I learn (well... I try) Wietse Venema wie...@porcupine.org a écrit : Nicolas HAHN: Postfix feature request: that would be nice that Postfix

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

that for versions 0.9.14 or 0.9.15. There is always something positive to take somewhere :) BR. nicolas Wietse Venema wie...@porcupine.org a écrit : Nicolas HAHN: Postfix feature request: that would be nice that Postfix be able to do this kind of basic checks by itself when starting (or when

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

This is a reply to myself because I'm reviewing the way it works. Yes, but if I'm right, the log message is emitted at the time there is an e-mail processed (by postfix/local for my issue). In fact, the fatal is written in the logs each minute and 1 second for this issue in my case by the

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

Can you post the fatal error messages you found, especially the messages that log why the queue manager was restarting, as that is the real problem. Here is what I found: 2013-04-24T10:04:38.005665+00:00 iccpfxor04 postfix/local[9370]: fatal: main.cf configuration error: mailbox_size_limit

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

Yea. Thanks, i've seen it the first time you posted it. But that's not for this reason I'll change my mind about this. BR. nicolas Wietse Venema wie...@porcupine.org a écrit : Nicolas HAHN: What I consider just abnormal as already written is that for me (so it's my opinion), Postfix should

Re: Message_size_limit issue with postfix v 2.8.8-1 on RHEL 6

nagios]# service nagios restart Running configuration check...done. Stopping nagios: ...done. Starting nagios: done. [root@server nagios]# But OK I understand your points and will stop to post my blabla. /dev/rob0 r...@gmx.co.uk a écrit : On Wed, Apr 24, 2013 at 05:23:09PM +0200, Nicolas HAHN wrote

New Postfix log analyzer tool V0.9.13 released (PostgreSQL DB 9.2.x based)

it for Postfix versions 2.8 logs in the comming days, and I hope except the QID, the format of the logs is the same :-) I'm available if you wish to answer questions and provide information/support as I need to create and provide complete set of documentations. Kind regards, Nicolas

Re: New Postfix log analyzer tool, statistics, grapher, ... PostgreSQL DB 9.2.x based

a écrit : On Apr 11, 2013, at 7:29, Nicolas HAHN ha...@erios.org wrote: a Linux server It requires Linux? Why would it require Linux? attachment: hahnn.vcf

Re: New Postfix log analyzer tool, statistics, grapher, ... PostgreSQL DB 9.2.x based

not validated for other OS than RHEL 6. But again, if people in the community want to deploy it, test it, install it, debug it, validate it on other platforms, then that will be a win-win deal for sure :) There are so much to be done... Kind regards, Nicolas attachment: hahnn.vcf

New Postfix log analyzer tool V0.9.11 released (PostgreSQL DB 9.2.x based)

%20releases/E-mail%20Log%20Search%20Engine/ Now will start to commit version 0.9.12 :) Kind regards, Nicolas attachment: hahnn.vcf

[Bug fix in previous email] New Postfix log analyzer tool, statistics, grapher, ... PostgreSQL DB 9.2.x based

Dear Postfix Community, Instead of reading in my previous email: The archive I just uploaded this morning deal with Postfix version =2.8.x logs. Please read: The archive I just uploaded this morning deal with Postfix version _*=2.8.x*_ logs. This is a misstyping from me ;) attachment:

New Postfix log analyzer tool, statistics, grapher, ... PostgreSQL DB 9.2.x based

regards, Nicolas attachment: hahnn.vcf

Re: Accept and store locally any mail received

, and example.com is listed in mydestination. This works perfectly. Thanks a lot Noel. -- Nicolas

Accept and store locally any mail received

on how to configure postfix this way? Thanks, -- Nicolas

Introduction question about whitelisting

Hi, I'm an Austrian Linux user living and working in South France. I've just setup a basic - and working - mail server on Debian Squeeze, using Postfix and Dovecot. I've installed policyd-weight for basic spam filtering. Since the defaults are quite restrictive, I thought I'd try with a bit

Re: Introduction question about whitelisting

Le 20/03/2012 17:53, Noel Jones a écrit : You sure that mail is really from hotmail? The IP shown in your log snippit is owned by Microsoft, but doesn't seem to have an rDNS hostname; that's quite unusual for hotmail as it's common practice to reject clients with no rDNS. And the HELO name

Questions about queue cli commands

Hello, I have a few simple questions to be sure using the right commands to do what I want : Situation - I have mails in the queue (I can see them with mailq). A) I want to delete them - postqueue -f - postsuper -d ALL - mailq | awk '{if (NF == 7) print $1'} | postsuper -d - Are

Re: Questions about queue cli commands

On 06/27/2011 11:24 AM, Patrick Proniewski wrote: Salut, On 27 juin 2011, at 11:09, Nicolas Michel wrote: I have mails in the queue (I can see them with mailq). A) I want to delete them - postqueue -f nope, it will just flush the queue (force a new delivery attempt) - postsuper -d ALL

Encrypted connection from mta to mta?

Hello, I was asking myself about the kind of connection used by a MTA to contact another one. For exemple, I know that we can setup in a MUA an SSL (or TLS) connection when configuring the SMTP connection. So the connection between the MUA and the MTA is encrypted. But can we configure

Re: How to reject bad hosts

On 08/09/2010 05:15 PM, Noel Jones wrote: On 8/9/2010 9:29 AM, Nicolas Michel wrote: Hello, I want to know if there is a way to reject connections from host not listed in the MX records of the domain it claims to be. For example : a host with IP WWW.XXX.YYY.ZZZ try so send a mail to my domain

Re: How to reject bad hosts

On 08/09/2010 06:34 PM, Stan Hoeppner wrote: Nicolas Michel put forth on 8/9/2010 9:29 AM: For example : a host with IP WWW.XXX.YYY.ZZZ try so send a mail to my domain (we'll call it mydomain.be) and claims that the sender is u...@otherdomain.com Example of forging, typical of spammers

Re: How to reject bad hosts

On 08/09/2010 10:43 PM, Martin Schütte wrote: On 08/09/10 16:29, Nicolas Michel wrote: I want to know if there is a way to reject connections from host not listed in the MX records of the domain it claims to be. Try http://www.policyd-weight.org/ It checks and compares the client IP, its

Re: How to deliver to Cyrus imapd mailboxes

/main.cf: mailbox_transport = cyrus:unix:/var/spool/postfix/public/lmtp IMHO mailbox_transport should be set to lmtp:unix:/var/spool/postfix/public/lmtp -- NIcolas

Re: local_recipient_maps into an ldap

Victor Duchovni a crit: On Thu, Sep 03, 2009 at 01:04:01PM +0200, Nicolas Michel wrote: In that file (ldap-localusers.cf), I set this : server_host = zimbra.pcsol.be search_base = ou=people,dc=pcsol,dc=be query_filter = ((mail=%s)(accountStatus=active

local_recipient_maps into an ldap

Hello, I have a zimbra server for managing mail accounts. I have a postfix mail server before it. Mails from outdoor arrive on that server before being relayed to the zimbra server. I want to search from the postfix server into the ldap of zimbra the users/aliases to reject every mail

Re: local_recipient_maps into an ldap

Olivier Nicole a crit: Nicolas, server_host = zimbra.pcsol.be Are you sure your server is running on port 389? Would you run TLS? >From your Postfix machine, can you access the LDAP server on zimbra machine (no firewall)? I would try ldapsearch command on the post

Integration of content_filter and mailbox/alias

...@domain.tld us...@domain.tld (and send two mails - user1@ and user2@) sendmail -oi -f sen...@domain.tld us...@domain.tld So, user2@ receive two mails. Do you have an idea to prevent this problem? Any advices? Thanks a lot. Regards, -- -Nicolas.

Re: Integration of content_filter and mailbox/alias

/sendmail -oi -f ${sender} ${recipient} If virtual_alias_maps is read in these two lines, there's problem with this configuration: us...@domain.tld us...@domain.tld us...@domain.tld us...@domain.tld I hope you could help me. Regards, Nicolas On Fri, 31 Jul 2009 15:44:36 +0200

Re: Integration of content_filter and mailbox/alias

=no_address_mappings Regards, Nicolas On Fri, 31 Jul 2009 16:00:26 +0200 Nicolas Letellier nico...@nicoelro.net wrote: I use Postfix 2.4.7. In other terms, I don't want virtual_alias_maps be read in these two lines: 1 smtp inet n - n - - smtpd -o content_filter

Re: user permissions

Thank you a lot. I didn't know that solution. Le mardi 26 mai 2009 à 07:34 -0500, Noel Jones a écrit : Nicolas Michel wrote: Thanks for your help. But that tips is not really what I'm searching for. The class restriction is a global restriction : some users have full permission

user permissions

This is my first post on this mailing list so hi to everyone ;) I have a special demand : I want that a user can't send mails but only to some pre-defined e-mail adresses. For example : my user t...@domain.com can send mails to rob...@domain.com, r...@domain2.fr and ke...@domain2.fr but to nobody

mailboxes and aliases for an address

= proxy:mysql:/usr/local/etc/postfix/mysql/virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/usr/local/etc/postfix/mysql/virtual_mailbox_maps.cf virtual_minimum_uid = 143 virtual_transport = dovecot virtual_uid_maps = static:143 -- Nicolas Letellier [EMAIL PROTECTED]

Re: mailboxes and aliases for an address

On Mon, 3 Nov 2008 12:12:35 +0100 ML [EMAIL PROTECTED] wrote: Le 3 nov. 08 à 12:02, Nicolas Letellier a écrit : Hello. I would like to have this possibility in postfix : I have [EMAIL PROTECTED] It's a mailbox (pop or imap), and it's TOO an alias (to [EMAIL PROTECTED]) When

Postfix heavy load under freebsd: Too many open files

) Thanks, -- Nicolas Haller

Re: Postfix heavy load under freebsd: Too many open files

Oops, sorry, I don't see this page. Someone know what is wrong? You need to adjust the PER PROCESS open file limits. Thank you! -- Nicolas Haller

Re: Whitelist a host using check_client_access before the rbl check?

On Mon, Aug 04, 2008 at 02:40:54PM -0400, Brian Evans - Postfix List wrote: Nicolas KOWALSKI wrote: On Mon, Aug 04, 2008 at 12:29:34PM -0400, Brian Evans - Postfix List wrote: A *better* way is force them to Authenticate using SASL. See http://www.postfix.org/SASL_README.html Postfix

Whitelist a host using check_client_access before the rbl check?

smtpd_tls_session_cache_timeout = 3600s Any help would be appreciated, Thanks, -- Nicolas

Re: Whitelist a host using check_client_access before the rbl check?

On Mon, Aug 04, 2008 at 08:58:01AM -0400, Charles Marcus wrote: Let me give this one a try... I *think* i see the problem... On 8/4/2008, Nicolas KOWALSKI ([EMAIL PROTECTED]) wrote: Aug 4 14:17:18 petole postfix/smtpd[23545]: NOQUEUE: reject: RCPT from 225.96.68-86.rev.gaoland.net

Re: Whitelist a host using check_client_access before the rbl check?

On Mon, Aug 04, 2008 at 10:56:36AM -0400, Brian Evans - Postfix List wrote: Nicolas KOWALSKI wrote: On Mon, Aug 04, 2008 at 08:58:01AM -0400, Charles Marcus wrote: On 8/4/2008, Nicolas KOWALSKI ([EMAIL PROTECTED]) wrote: Aug 4 14:17:18 petole postfix/smtpd[23545]: NOQUEUE: reject

Re: Whitelist a host using check_client_access before the rbl check?

On Mon, Aug 04, 2008 at 12:29:34PM -0400, Brian Evans - Postfix List wrote: Brian Evans - Postfix List wrote: Nicolas KOWALSKI wrote: The client said 'EHLO demisel.dyndns.org'. This is the value that check_helo_access can find, though somewhat unreliable to whitelist. I apparently have