Re: 100 Recipient Limit

> Hello, > > We have discovered an issue in our postfix configuration that appears to > limit the amount of recipients permitted in a single message to 100. > > The issue exhibits itself in the form of our application receiving a > timeout message after the 100th RCPT TO command and I have

Re: 100 Recipient Limit

On Wed, Nov 18, 2015 at 12:31:50PM +, Matt Bayliss wrote: > We have discovered an issue in our postfix configuration that appears to > limit the amount of recipients permitted in a single message to 100. This is not the case by default.

Concurrency limit (was: 100 Recipient Limit)

Viktor Dukhovni: > The limit of 100 worked well in 1997, and still works well on > smaller personal mail-servers. Beefier servers with lots memory, > CPU, disk and network may well be able to handle 1000 or more > concurrent connections. Email server performance is primarily limited by file

Re: 100 Recipient Limit

>> We have discovered an issue in our postfix configuration that appears to >> limit the amount of recipients permitted in a single message to 100. > >This is not the case by default. I thought it must be but what I'm seeing corresponds to a limit of 100 somewhere, false theory debunked thanks.

Re: 100 Recipient Limit

Matt Bayliss: > [3] Output of /var/log/maillog during the session with debug_peer_list set > to client > http://pastebin.centos.org/36256/ This ends with: Nov 18 10:28:52 mailserver postfix/smtpd[31664]: < unknown[1.1.1.1]: RCPT TO:

Re: socket: malformed response

>> On Nov 18, 2015, at 10:49, Wietse Venema wrote: >> >> You need to show PIPE DAEMON logging. That will show WHY the pipe >> daemon terminated with an error, WHY you are getting "connection >> refused" errors, and so on. >> >>$ grep 'postfix/pipe.*fatal'

Re: Filtering mail from outside users only

Thank you. It is not clear from the docs whether these are examples or literal, which is why I asked "are these literal?" > On Nov 18, 2015, at 03:53, Wietse Venema wrote: > > Vicki Brown: >> Also, when I try these entries literally, I get >> fatal: bind 1.2.3.4 port

Re: socket: malformed response

Vicki Brown: > > On Nov 18, 2015, at 03:45, Wietse Venema wrote: > > > > Please report the logfile record FROM PROCESS 74861. THAT logfile > > record says WHY it terminated with a fatal error. > > > > From mail.log > > Nov 17 02:38:29 g3po postfix/master[69788]: warning:

Re: socket: malformed response

Vicki Brown: > I have two long and complicated errors at approximately midnight on both Nov > 17 and Nov 18; however, the spam checking continued happily for 2 hours after > that. > > mail.log:Nov 18 00:02:31 g3po postfix/pipe[590]: E8F682F69538: > to=, relay=spamfilter,

Re: Filtering mail from outside users only

On November 18, 2015 9:29:29 AM Vicki Brown wrote: Also, when I try these entries literally, I get fatal: bind 1.2.3.4 port 25: Can't assign requested address means you have one port 25 listner in master.cf, if you need one more all must be specified pr ip and port not just

Re: Suggestions for more logging?

Vicki Brown: > Nov 17 23:33:28 g3po postfix/qmgr[87590]: warning: connect to transport > spamchk: Connection refused The pipe service "spamchk" is throttled because of fatal errors, and therevore connection requests are dropped by the kernel. You need to resolve the fatal pipe daemon errors.

Re: socket: malformed response

Vicki Brown: > Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: transport spamchk failure > -- see a previous warning/fatal/panic logfile record for the problem > description > Nov 17 02:38:29 g3po postfix/master[69788]: warning: process > /usr/libexec/postfix/pipe pid 74861 exit status 1

100 Recipient Limit

Hello, We have discovered an issue in our postfix configuration that appears to limit the amount of recipients permitted in a single message to 100. The issue exhibits itself in the form of our application receiving a timeout message after the 100th RCPT TO command and I have reproduced this

Re: Filtering mail from outside users only

Vicki Brown: > Also, when I try these entries literally, I get > fatal: bind 1.2.3.4 port 25: Can't assign requested address Those are examples. You should specify an IP address that is configured on your server. Wietsde

forwarding email from files format postfix

Hi, Someone made a little mistake (wrong TO) and some email (few thousand) were received on the wrong postfix server. now, I have files within a vmail folder. I need to forward those email to the correct smtp server (no-postfix) ... so I tried to do a batch script that use mail to send back

Suggestions for more logging?

I hunted up a better script for running SpamAssassin from postfix and tweaked it for more logging and better errors and I'm still seeing some odd behavior. e.g. from the system log: Nov 17 23:33:14 g3po spamchk[87681]: Spam filter piping to SpamAssassin: /usr/local/bin/spamc -x -E -s 10485760

Filtering mail from outside users only

I am reading http://www.postfix.org/FILTER_README.html , the section on "Filtering mail from outside users only" and I am befuddled. Am I correctly understanding that this recipe requires three smtp ... entries in master.cf? Where can I find

RE: Suggestions for more logging?

Try starting spamd with --listen-ip 127.0.0.1 --listen-ip ::1 Greetz, Louis > -Oorspronkelijk bericht- > Van: v...@cfcl.com [mailto:owner-postfix-us...@postfix.org] Namens Vicki > Brown > Verzonden: woensdag 18 november 2015 9:13 > Aan: Postfix users > Onderwerp: Suggestions for

Re: Filtering mail from outside users only

Also, when I try these entries literally, I get fatal: bind 1.2.3.4 port 25: Can't assign requested address -- confused... > On Nov 18, 2015, at 00:17, Vicki Brown wrote: > > I am reading http://www.postfix.org/FILTER_README.html > ,

Re: 100 Recipient Limit

Matt Bayliss: > Hello, > > We have discovered an issue in our postfix configuration that appears to > limit the amount of recipients permitted in a single message to 100. Please report Postfix logging, as requested in the mailing list welcome message. Wietse TO REPORT A PROBLEM see

Re: forwarding email from files format postfix

On 11/18/2015 2:53 AM, Stéphane MERLE wrote: > Hi, > > Someone made a little mistake (wrong TO) and some email (few > thousand) were received on the wrong postfix server. > now, I have files within a vmail folder. > I need to forward those email to the correct smtp server > (no-postfix) ... so I

Outbound Relays, Delivered-To, and "mail forwarding loop detected"

After many years it is now necessary for me to change my mail server to one on a different network. My old server network is going off the Internet at some point but it will remain with a local dynamic address. It will need to relay mail. I have set up a vpn between the old server and the new

Re: Outbound Relays, Delivered-To, and "mail forwarding loop detected"

Bob Proulx: > Nov 18 12:08:16 havoc postfix/cleanup[27515]: 910CE4A0: reject: header > X-X-Delivered-To: b...@proulx.com from localhost[127.0.0.1]; > from= to= proto=ESMTP > helo=: 5.7.1 mail forwarding loop detected This message is logged by the CLEANUP

RE: mail delivery to alias with command processing

Thanks. I tried "| cat > /tmp/foo" and the postfix config is fine. I should have done that first - I just assumed I had misunderstood something about postfix and botched the postfix config. Our /usr/local/bin/forwardstdin must have some courier environment dependency in it since it's been

Re: mail delivery to alias with command processing

Chris Boylan: > I'm trying receive emails to acknowledge-@CUSTOMERWEBSITE.com by way of > a virtual(8) domain and then get local(8) delivery using an aliases(5) config > with its | command processing. > > Issue is that the loader program (/usr/local/bin/forwardstdin below) we are > using is

mail delivery to alias with command processing

I'm trying receive emails to acknowledge-@CUSTOMERWEBSITE.com by way of a virtual(8) domain and then get local(8) delivery using an aliases(5) config with its | command processing. Issue is that the loader program (/usr/local/bin/forwardstdin below) we are using is reporting zero bytes read on

Re: Outbound Relays, Delivered-To, and "mail forwarding loop detected"

Wietse Venema wrote: > Bob Proulx: > > Nov 18 12:08:16 havoc postfix/cleanup[27515]: 910CE4A0: reject: header > > X-X-Delivered-To: b...@proulx.com from localhost[127.0.0.1]; > > from= to= proto=ESMTP > > helo=: 5.7.1 mail forwarding loop detected > > This