- Original Message -
> From: "Wietse Venema"
> To: "Postfix users"
> Sent: Monday, July 20, 2015 4:57:43 PM
> Subject: Re: Send a DSN report only to one specified email address
> Postfix implements DSN as specified in RFC 3464. The Postfix
> command-line interface and interaction with
Hi everyone,
Can anyone pinpoint me to a simple way to limit the outgoing number of
emails in a time frame per domain, without involving policyd and mysql,
or any other 3rd party script?
I'm looking for a simple restriction with a hash table or so.
Best Regards,
Istvan
On Thu, 23 Jul 2015 10:47:25 +0200
Istvan Prosinger wrote:
> Can anyone pinpoint me to a simple way to limit the outgoing number
> of emails in a time frame per domain, without involving policyd and
> mysql, or any other 3rd party script?
>
> I'm looking for a simple restriction with a hash tabl
Istvan Prosinger:
> Hi everyone,
>
> Can anyone pinpoint me to a simple way to limit the outgoing number of
> emails in a time frame per domain, without involving policyd and mysql,
> or any other 3rd party script?
http://www.postfix.org/postconf.5.html#transport_destination_rate_delay
http://w
Wietse,
thanks, but let me make it more clear - I'm not trying to limit the
number of emails towards the destination domains (like yahoo.com), but
from the domains the server is sending from (sender domains).
The idea behind this is not a "polite delivery policy" towards the other
servers, b
I would like to use something like
virtual_mailbox_domains = domain1.org domain2.org
virtual_uid_maps = hash:/etc/postfix/virtual_uids
virtual_transposrt = maildrop
with
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${user_from_vir
On Thu, Jul 23, 2015 at 09:08:53AM -0400, Marvin Renich wrote:
> I would like to use something like
>
> virtual_mailbox_domains = domain1.org domain2.org
> virtual_uid_maps = hash:/etc/postfix/virtual_uids
> virtual_transposrt = maildrop
>
> with
>
> maildrop unix - n n -
* Viktor Dukhovni [150723 09:17]:
> Not possible. The virtual_uid_maps parameter is a feature of the
> virtual(8) not the pipe(8) transport. And it stores a numeric uid,
> not a login name.
>
> You'll need to implement any required lookups in a wrapper
> program around the underlying maildrop t
On 7/23/2015 6:38 AM, Istvan Prosinger wrote:
> Wietse,
>
> thanks, but let me make it more clear - I'm not trying to limit the
> number of emails towards the destination domains (like yahoo.com),
> but from the domains the server is sending from (sender domains).
>
> The idea behind this is not
Hi!
Currently i'm in contact with someone who has the helo set to an invalid
hostname. Mails from their system are therefor rejected by my mailserver
beacuse i have:
smtpd_recipient_restrictions =
reject_invalid_helo_hostname
reject_unknown_helo_hostname
reject_non_fqdn_helo_hostname
Th
On Thu, Jul 23, 2015 at 06:26:57PM +0200, Sascha H?depohl wrote:
> So my question is: Are there any reasonable reasons to have an invalid
> helo hostname.
The sender is too cost/risk averse to make an effort to fix their
broken system. Whether that's reasonable depends on context.
> or should I
On Thu, 23 Jul 2015 18:26:57 +0200
Sascha Hüdepohl wrote:
> So my question is: Are there any reasonable reasons to have an invalid
> helo hostname or should i relax my settings?
No reasonable reasons, IMHO. You may consider to whitelist them; be
carefull, it is not straight and simple... :-)
Luc
On Tue, 21 Jul 2015 at 12:35 Viktor Dukhovni
wrote:
>
> But copying queue files is not recommended. That takes some care
> to get right. It is better to relay any queued mail from the old
> server to the new, or just turn off the inflow of new mail into
> the old server and let the queue "drain
13 matches
Mail list logo
