Re: Address verification database

Il 26/01/2012 01:42, Wietse Venema ha scritto: Daniel L. Miller: Can an alternative to "btree" be used for the verification database? Perhaps a SQL table? For persistent storage, the options are currently limited to hash and btree. Postfix 2.9 adds memcache to this list. Wietse Sor

Re: postscreen "Operation not permitted"

On 1/25/2012 9:05 PM, Noel Jones wrote: > On 1/25/2012 7:27 PM, Wietse Venema wrote: >> Apparently, FreeBSD packet filters can return an EPERM error >> when a packet does not match a valid state. >> ... >> So that could explain the EPERM (which has errno of 1). >> >> Wietse > > > OK, tha

Re: postscreen "Operation not permitted"

On 1/25/2012 7:27 PM, Wietse Venema wrote: > Apparently, FreeBSD packet filters can return an EPERM error > when a packet does not match a valid state. > ... > So that could explain the EPERM (which has errno of 1). > > Wietse OK, that server is using pf. The error doesn't seem to be

split by domain

Hi all, We are using Postfix 2.3.3 as external mx. It manages several our domains and just relays to spam check servers using transport and relay_domains. Currently if a message includes multiple our domains it relays as a one message. We would like to split by domain and relay to spam check serve

Re: postscreen "Operation not permitted"

Wietse Venema: > Noel Jones: > > With postfix-2.9-RC2 on FreeBSD 8.1 > > > > I assume the "Operation not permitted" message is an artifact of > > writing to a disconnected socket or such and nothing to worry > > about? Only happens on a small percentage of connections rejected > > by postscreen. >

Re: postscreen "Operation not permitted"

On Wed, Jan 25, 2012 at 07:37:54PM -0500, Wietse Venema wrote: > Noel Jones: > > With postfix-2.9-RC2 on FreeBSD 8.1 > > > > I assume the "Operation not permitted" message is an artifact > > of writing to a disconnected socket or such and nothing to > > worry about? Only happens on a small percent

Re: Address verification database

Daniel L. Miller: > Can an alternative to "btree" be used for the verification database? > Perhaps a SQL table? For persistent storage, the options are currently limited to hash and btree. Postfix 2.9 adds memcache to this list. Wietse

Re: postscreen "Operation not permitted"

Noel Jones: > With postfix-2.9-RC2 on FreeBSD 8.1 > > I assume the "Operation not permitted" message is an artifact of > writing to a disconnected socket or such and nothing to worry > about? Only happens on a small percentage of connections rejected > by postscreen. Network writes can fail for

Address verification database

Can an alternative to "btree" be used for the verification database? Perhaps a SQL table? -- Daniel

postscreen "Operation not permitted"

With postfix-2.9-RC2 on FreeBSD 8.1 I assume the "Operation not permitted" message is an artifact of writing to a disconnected socket or such and nothing to worry about? Only happens on a small percentage of connections rejected by postscreen. So far today (not a particularly busy server): # gre

Re: Restricting port 25 with cidr table

On 1/21/2012 3:58 AM, Nikolaos Milas wrote: > However, we could formulate gwservers.cidr as (for example): > > xxx.xxx.xxx.xxx OK > xxx.xxx.xxx.xxx OK > 127.0.0.1 OK > :::::: OK > :::::OK > ::1

Re: Restricting port 25 with cidr table

On 1/20/2012 3:54 PM, Wietse Venema wrote: > On 20/1/2012 3:24 ??, Nikolaos Milas wrote: >> By the way, I fail to see any difference between the two methods. It >> seems to me the same to use: >>smtpd_client_restrictions = check_client_access >> cidr:/etc/postfix/gwservers.cidr >>where gw

Re: Weird rejection

On Wed, Jan 25, 2012 at 12:03:22PM -0600, I wrote: > On Wed, Jan 25, 2012 at 11:08:30PM +0530, DN Singh wrote: > > Guys, I did find find the culprit, but it was not in the yahoo > > list, but the overall file. The entry was: > > > > ## > > co.inREJECT Bad domain 18

sender_canonical, generic and sender_bcc

Hello, I have a scenario with N e-mail accounts: us...@domain.com us...@domain.com us...@domain.com And I want to accomplish the following: 1-. Every sender e-mail address to be converted to gene...@domain.com. This means that when us...@domain.com send an e-mail to us...@domain.com the from addr

Re: Weird rejection

On Wed, Jan 25, 2012 at 11:08:30PM +0530, DN Singh wrote: > Guys, I did find find the culprit, but it was not in the yahoo > list, but the overall file. The entry was: > > ## > co.inREJECT Bad domain 1868 > ## > > I guess this should reject emails

Re: Weird rejection

Thank you very much guys, you're a lifesaver.. @Pierre: The script you wrote did a job of replacing, but did not replace the file itself, and instead showed the output on screen. So, I just redirected the output in another file, and it worked. Guys, I did find find the culprit, but it was not in

Re: Weird rejection

Am 25.01.2012 15:59, schrieb Ralf Hildebrandt: > * DN Singh : >> Duane, I am not using sender restrictions right now, but I can implement it. >> >> Ralf, can you please tell me a method to append incremental numbers at the >> end of each line? > > Use a text editor? > with small google i found

Re: Weird rejection

* DN Singh : > Duane, I am not using sender restrictions right now, but I can implement it. > > Ralf, can you please tell me a method to append incremental numbers at the > end of each line? Use a text editor? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universit

Re: Weird rejection

On Wed, Jan 25, 2012 at 7:40 PM, Duane Hill > wrote: >I understood the logic, but is there any way to automate the procedure to add this incremental number at the end of each line? Maybe something like this: > cat t.pl #!/usr/bin/perl use strict; my $i=0; while(<>) {

Re: Weird rejection

On Wed, Jan 25, 2012 at 7:40 PM, Duane Hill wrote: > On Wednesday, January 25, 2012 at 13:41:54 UTC, > dnsingh.dns@gmail.comconfabulated: > > > Duane, I am not using sender restrictions right now, but I can implement > it. > > > Ralf, can you please tell me a method to append incremental numbers

Re: Weird rejection

On Wednesday, January 25, 2012 at 13:41:54 UTC, dnsingh@gmail.com confabulated: > Duane, I am not using sender restrictions right now, but I can implement it. > Ralf, can you please tell me a method to append incremental numbers at the > end of each line? I need to do it as you pointed out.

Re: SV: Missing(?) function is Postfix

Johan Andersson: > Hi. > > Ok, thanks for the info. > I would recommend using this: /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/transport /etc/postfix/transport: # Inbound relay for example.com. See STANDARD_CONFIGURATION_README.html example.com relay:[mailhost.exa

Re: Weird rejection

Duane, I am not using sender restrictions right now, but I can implement it. Ralf, can you please tell me a method to append incremental numbers at the end of each line? I need to do it as you pointed out. I was searching for the same, but could not find out something that exactly does what I need

SV: Missing(?) function is Postfix

Hi. Ok, thanks for the info. Br Johan -Ursprungligt meddelande- Från: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] För Wietse Venema Skickat: den 25 januari 2012 14:29 Till: Postfix users Ämne: Re: Missing(?) function is Postfix Johan Andersson: > Hello

RE: Problems sending to Mobile Me

I did a little more messing around with this. The problem seems directly related to the OS that's running on the machine. When I use either postfix or telnet to connect on a machine running CentOS or an older version of Fedora it does not work correctly, however if I use a Windows or a machine

Re: Missing(?) function is Postfix

Johan Andersson: > Hello ! > > In sendmail it is possible to add this to mailertable > > domain.comsmtp:[server1] > . smtp:[server2]:[server3] > > If server2 is not responding, then send to server3. > > Is that function available in Postfix and if not, will it be (it > woul

Re: Weird rejection

On Wednesday, January 25, 2012 at 11:58:31 UTC, dnsingh@gmail.com confabulated: > On Wed, Jan 25, 2012 at 4:04 PM, Ralf Hildebrandt < > ralf.hildebra...@charite.de> wrote: >> * DN Singh : >> > Hello Group, >> > >> > I have configured some rejection domains in postfix access file, where it >>

Missing(?) function is Postfix

Hello ! In sendmail it is possible to add this to mailertable domain.comsmtp:[server1] .smtp:[server2]:[server3] If server2 is not responding, then send to server3. Is that function available in Postfix and if not, will it be (it would be nice to have :)

Re: Weird rejection

* DN Singh : > Also, these are recipient domains, and I am already using > reject_unknown_recipient_domain parameter in smtpd_recipient_restrictions, > but it does not reject these domains. This is why I have to do this > manually. > > Any reason for the check not happening?? My postconf -n outpu

Re: Weird rejection

On Wed, Jan 25, 2012 at 4:04 PM, Ralf Hildebrandt < ralf.hildebra...@charite.de> wrote: > * DN Singh : > > Hello Group, > > > > I have configured some rejection domains in postfix access file, where it > > rejects bad domains, or domains that do not exist. This list has been > > gradually develope

Re: Weird rejection

* DN Singh : > Hello Group, > > I have configured some rejection domains in postfix access file, where it > rejects bad domains, or domains that do not exist. This list has been > gradually developed over time. A weird behavior happened the last time I > updated it. I had added some typos/bad doma