(10) *
default_destination_rate_delay (1) = 10 per second).
I'm clearly lost - how can I ensure 10 messages per second maximum sending
rate? A delay of 0 doesn't compute for me.
On Wed, Feb 23, 2022 at 10:29 AM Matus UHLAR - fantomas
wrote:
> On 23.02.22 10:21, Russell Jones wrote:
> >That configuration
ds,
> YM
>
> Le mer. 23 févr. 2022 à 17:08, Russell Jones a
> écrit :
>
>> Hi all,
>>
>> I am struggling to understand why my postfix configuration is not
>> allowing me to send 10 messages per second through my configured relayhost.
>> When watching t
Hi all,
I am struggling to understand why my postfix configuration is not allowing
me to send 10 messages per second through my configured relayhost. When
watching the logs, it is sending 1 message per second.
initial_destination_concurrency = 10
default_destination_concurrency_limit = 10
Thanks for the info all!
In order to KISS, I ended up just changing it to relay everything via
relayhost. This works as expected, remote addresses get relayed and local
addresses get delivered like they are supposed to.
On Fri, Jun 11, 2021 at 3:45 AM Michael Storz wrote:
> Am 2021-06-10
.
On Wed, Jun 9, 2021, 7:52 PM Viktor Dukhovni
wrote:
> On Wed, Jun 09, 2021 at 07:20:43PM -0500, Russell Jones wrote:
>
> > I have check_recipient_mx_access setup to route mail for certain
> providers
> > through a relay. This has been working well, until I discovered it is
Hi all,
I have check_recipient_mx_access setup to route mail for certain providers
through a relay. This has been working well, until I discovered it is
breaking delivery to local users that get CC'd in an email that is being
routed through this relay.
Here is how I have it setup:
Still interested in trying to figure this out if I can. I am not sure
what else to look for on this. Any assistance will be gratefully accepted!
On 1/18/2016 6:49 PM, Russell Jones wrote:
Sorry that was a typo, I meant I checked for
"destination_recipient_limit" and did not have an
Hi all,
I am trying to lower the concurrency for emails sent to *.rr.com
domains. I have configured the following, can anyone please tell me what
I am missing? Thanks in advance!
In main.cf:
transport_maps = hash:/etc/postfix/transport
default_destination_concurrency_limit = 2
Hi Wietse,
Thanks for replying! I have not set that. Everything I have set for this
I provided in my initial email. I double checked to see if I had
anything set for "destination_concurrency" and I do not.
On 1/18/2016 11:02 AM, Wietse Venema wrote:
Russell Jones:
Hi all,
I
Just to be clear that I do indeed know how to read, I was searching for
anything with "destination_recipient_limit" in the name, including
looking for slow_destination_recipient_limit. :-)
On 1/18/2016 6:49 PM, Russell Jones wrote:
Sorry that was a typo, I meant
Sorry that was a typo, I meant I checked for
"destination_recipient_limit" and did not have anything set with that
name in main.cf.
On 1/18/2016 6:32 PM, Russell Jones wrote:
Hi Wietse,
Thanks for replying! I have not set that. Everything I have set for
this I provided in
Hi all,
Upgrading mail server from Postfix 2.9 to 2.10. Could I get a quick
sanity check to ensure my (fairly simple) setup is sane with the new
smtpd_relay_restrictions? Thanks :-)
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated
reject_unauth_destination
On 4/13/2013 2:39 PM, Reindl Harald wrote:
i would ALWAYS include reject_unauth_destination BEFORE check_client_access
here
Thanks Reindl!
It was before, however I read on the Postfix docs that
reject_unauth_destination is no longer necessary in the
recipient_restrictions section, hence
On 4/13/2013 3:44 PM, b...@bitrate.net wrote:
you offer no service whatsoever on port 25? postfix is not listening on that
port? if that's truly the case, then, to be pedantic, you're running an msa,
not an mta, in which case you could argue that is an exception to the rule, and
such
, 2012 at 12:30:51AM -0500, Russell Jones wrote:
I have been following (or attempting to follow) these two sites I
found that showed how to set this up. They both show domain then
transport:
I don't see this at either site. All I found was transport:,
with custom transport names defined
Dukhovni wrote:
On Mon, Jul 30, 2012 at 09:57:10PM -0500, Russell Jones wrote:
Thanks Viktor. I feel like I am closer, just not quite there yet. I
am now getting the following error:
mail for 1.1.1.1 loops back to myself
main.cf:
sender_dependent_default_transport_maps =
hash:/etc/postfix
, Jul 30, 2012 at 11:33:40PM -0500, Russell Jones wrote:
I have a simple postfix 2.9.3 server with 2 IP addresses. I want
all mail sent from a sender address of *@example1 to go through
1.1.1.1, and all mail sent from a sender address of *@example2.com
to go through 1.1.1.2.
What does go through mean
for this particular feature it seems.
On 7/30/2012 11:56 PM, Russell Jones wrote:
What does go through mean?
The source IP is defined based on the sender's domain. This is what I
need to achieve: Recently there have been requests for sending mail
with source IP addresses that depend on the envelope
Thanks Viktor, the examples helped considerably. I now have it working
as intended :)
Hopefully this thread will help others in the future that may have
issues too.
On 7/31/2012 12:21 AM, Viktor Dukhovni wrote:
On Mon, Jul 30, 2012 at 11:56:05PM -0500, Russell Jones wrote:
The source
Hi all,
I am having a very difficult time getting
sender_dependent_default_transport_maps to actually work as
described.
I have a simple postfix 2.9.3 server with 2 IP addresses. I want all
mail sent from a sender address of *@example1 to go through
12:18 AM, Viktor Dukhovni wrote:
On Sun, Jul 29, 2012 at 08:26:24PM -0500, Russell Jones wrote:
[ No HTML posts, please! ]
/@domain2\.com$/ 1.1.1.2:smtp:
Why do you believe this is the correct syntax? The transport(5)
documentation specifies:
transport:nexthop
digging into this further, it looks like the only way to
do this is to ditch Procmail, and thus lose Virtualmin control.
Oh well :-(
On 4/26/2012 4:39 PM, /dev/rob0 wrote:
[ Reply-To: dove...@dovecot.org is set ]
On Thu, Apr 26, 2012 at 01:01:22PM -0500, Russell Jones wrote:
I can't seem
://code.google.com/p/fusecompress/
On 4/29/2012 8:25 PM, Russell Jones wrote:
Thanks!
I am indeed trying to compress an uncompressed maildir. I am currently
using a standard Virtualmin setup (Postfix, Procmail, Dovecot).
Enabling compression as explained below works great for sent mail, but
I really
Hi all,
I can't seem to figure out where in Postfix I can configure the filename
that is written for incoming mail. I am attempting to follow this
tutorial for enabling compression of mail in Dovecot
(http://wiki2.dovecot.org/Plugins/Zlib), and apparently I need to
configure the filenames to
Hi *,
My google-foo is failing me at this point, so I turn to you all. I
am using a standard Postfix setup and am sending messages via
Thunderbird. I am choosing under the Options menu "Delivery Status
Notification". The results:
DSN's for email sent
y/aa082597.htm)
On to a different question, does Postfix have any features I am
unaware of that can still generate a "success" message if the remote
mail server responds with a "250"?
On 11/30/2011 5:01 PM, Russell Jones wrote:
notices when mail is sent to this one
specific mail server I provided in my log output?
Russell
On 11/30/2011 5:50 PM, Wietse Venema wrote:
Russell Jones:
html
head
meta content=text/html; charset=ISO-8859-1
http-equiv=Content-Type
/head
body bgcolor=#FF text=#00
this with no luck.
On 11/30/2011 6:00 PM, Wietse Venema wrote:
Russell Jones:
Hi Wietse,
Thanks! That's different from what I read in that article then...
according to that article the remote mail server needs to support DSN as
well for the reports to be generated.
Per RFC 3461..3464
Thanks! Just got it working as intended =)
Nov 30 18:33:04 bigbertha postfix/smtp[22632]: discarding EHLO keywords: DSN
On 11/30/2011 6:33 PM, Wietse Venema wrote:
Russell Jones:
Ah that makes sense!
This problematic mail server does announce DSN when you telnet to it,
while Google, Yahoo
Hello,
I know that maximal_queue_lifetime is the time a message is queued
before it is sent back as undeliverable, however what is the
configuration option for how long a message is attempted to be
delivered, before a warning message is sent to the original sender
saying Hey, this message
Thank you!
Barney Desmond wrote:
2009/11/22 Russell Jones rjo...@eggycrew.com:
I know that maximal_queue_lifetime is the time a message is queued before it
is sent back as undeliverable, however what is the configuration option for
how long a message is attempted to be delivered
I have Postfix 2.3.3 installed, and am using standard file system quotas
for users. Whenever a user receives a message and the message cannot be
delivered to them due to being over quota, the following bounce messages
is sent back:
russell-example@server2.example.com
Aw. That deserves a sad face :-( .
I was hoping, since you can edit bounce.cf to say what you would like,
you could also edit the actual system error message.
Sahil Tandon wrote:
On Tue, 20 Oct 2009, Russell Jones wrote:
I have Postfix 2.3.3 installed, and am using standard file
Actually that's all the logs show when sending to a non-existent address
that resides on the same physical server, but I got it figured it.
Believe it or not, it was actually my AVG antivirus. It turns out that
when scanning outgoing mail, by default AVG will use its own Auto SMTP
server. For
For some reason, if a local user sends mail to another local user who
doesn't exist, my Postfix installation doesn't seem to notify the sender
of the error, nor deliver a bounce message to the sender.
Log snippet of what I am talking about:
Sep 28 00:29:48 server2 dovecot: imap-login: Login:
35 matches
Mail list logo
