benchmark for postfix

Hi This is regarding the performance testing of postfix 2.10.1. We are using directory server --> openldap and imap server --> dovecot. We have tested the setup with spirent and mail drops are less. But we want to document the results. While searching on internet for few days about a already docu

Re: benchmark for postfix

On Mon, Apr 23, 2018 at 07:00:59AM +, SAAHIL IFTEKHAR wrote: > We want some guidance on --> Is SPECmail 2009 is the only available > benchmark for mail servers or there are others too? We use mstone (http://mstone.sourceforge.net/) for testing mail throughput. > Any help will be really apprec

Re: aquamail helo option

On Sun, Apr 22, 2018 at 07:24:42PM -0400, David Mehler wrote: Is anyone using Android's Aquamail to send mail through postfix? If so, how do you have it configured? My postfix is rejecting mail from Aquamail because it's helo is: <[192.168.1.1]> basically it's internal ip. how do you know it'

Re: benchmark for postfix

Hi Thanks for replying. >>What are your target numbers? 1/h, 1k/h, 1M/h? Currently we are testing for 20 / 10 minutes i.e 1M/hr approx. >>We use mstone (http://mstone.sourceforge.net/) for testing mail throughput. Is it a software or it is a benchmark standard. Actually we want one standa

Re: aquamail helo option

Hi, I don't have any mua* options set in main.cf. As for helo I'm going to post my restrictions and their corresponding files going to be a few hours, but I'm sure it's helo. Thanks. Dave. On 4/23/18, Matus UHLAR - fantomas wrote: >>> On Sun, Apr 22, 2018 at 07:24:42PM -0400, David Mehler wro

Re: aquamail helo option

On 23.04.18 09:25, David Mehler wrote: I don't have any mua* options set in main.cf. that is not what I have asked. As for helo I'm going to post my restrictions and their corresponding files going to be a few hours, but I'm sure it's helo. you did post your restrictions and I have found no

Re: aquamail helo option

Matus UHLAR - fantomas: > >Apr 22 13:40:13 hostname postfix/submission/smtpd[34144]: NOQUEUE: > >reject: RCPT from Connecting-Host-and-IP: 554 5.7.1 : > >Relay access denied; from= to= > >proto=ESMTP helo=<[192.168.1.107]> > > this does not look like HELO rejection. I agree, and I wrote Postfix.

issue with outlook.com / office 365 distribution lists...

... or whatever they are called. Hello, I come to you for help after a few days of work trying to figure out how to go around what I understand to be a quirk of the office 365 mail service. Any help is greatly appreciated, and thank you in advance for it. So, context: 1) I work for a smallish

Re: issue with outlook.com / office 365 distribution lists...

> On Apr 23, 2018, at 12:25 PM, mario.barbosa+postfixus...@gmail.com wrote: > > Upon further inspection, I figured out what is probably obvious to you > by now: the office 365 lists do not change the 'Sender:' header of the > original message, and when it comes back to be delivered to its > '@ex

Re: issue with outlook.com / office 365 distribution lists...

Hello again, On 04/23/2018 06:55 PM, Viktor Dukhovni wrote: >> On Apr 23, 2018, at 12:25 PM, mario.barbosa+postfixus...@gmail.com wrote: >> >> Upon further inspection, I figured out what is probably obvious to you >> by now: the office 365 lists do not change the 'Sender:' header of the >> origina

Re: issue with outlook.com / office 365 distribution lists...

> On Apr 23, 2018, at 1:45 PM, mario.barbosa+postfixus...@gmail.com wrote: > > Got any pointers on how to do this? What should I put in my to-read list > next? I know of an implementation via custom hooks in amavisd-new, not open-source. Don't know whether there's anything off-the-shelf you can

inet_interfaces

I changed my inet_interfaces setting this morning, and stopped and started postfix (postfix stop; postfix start) # postconf -n inet_interfaces inet_interfaces = 127.0.0.1, 65.121.55.42 But when I am trying to send emails to a certain company, I am getting an SPF error (even though my entire net

Re: inet_interfaces

> On Apr 23, 2018, at 3:30 PM, @lbutlr wrote: > > I changed my inet_interfaces setting this morning, and stopped and started > postfix (postfix stop; postfix start) > > # postconf -n inet_interfaces > inet_interfaces = 127.0.0.1, 65.121.55.42 > > But when I am trying to send emails to a cert

Re: inet_interfaces

On 2018-04-23 (13:38 MDT), Viktor Dukhovni wrote: > >> On Apr 23, 2018, at 3:30 PM, @lbutlr wrote: >> >> I changed my inet_interfaces setting this morning, and stopped and started >> postfix (postfix stop; postfix start) >> >> # postconf -n inet_interfaces >> inet_interfaces = 127.0.0.1, 65.1

Re: inet_interfaces

> On Apr 23, 2018, at 3:50 PM, @lbutlr wrote: > > That does not match what the documentation says, which I quoted. Here it is > again. > > > When inet_interfaces specifies just one IPv4 and/or IPv6 address that is not > a loopback addr

Re: inet_interfaces

On 2018-04-23 (14:13 MDT), Viktor Dukhovni wrote: > > On Apr 23, 2018, at 3:50 PM, @lbutlr wrote: >> >> When inet_interfaces specifies just one IPv4 and/or IPv6 address that is not >> a loopback address, the Postfix SMTP client will use t

Re: inet_interfaces

> On Apr 23, 2018, at 5:09 PM, @lbutlr wrote: > >> If you also list "127.0.0.1" the bind address will not be set. This makes >> sense, because either address may be needed for some subset of the >> connections. The text could be more clear, but bottom line you need to set >> smtp_bind_addr

Re: inet_interfaces

On 2018-04-23 (15:30 MDT), Viktor Dukhovni wrote: > > With separate transports, one can have "-o smtp_bind_address=127.0.0.1" and > the stock "smtp" and "relay" transports can have "-o > smtp_bind_address=192.0.2.1" (or whatever you have for an external address). > Seems pretty light-weight to

Re: inet_interfaces

@lbutlr skrev den 2018-04-23 21:30: covisp.net. 86400 IN TXT "v=spf1 mx a ip4:65.121.55.40/29 -all" this domain have duplicates ipv4 in spf