Hello postfix-users,
For a selected time period today, the postfix/postscreen DNSBL rank
log entries are summarized as:
1744 DNSBL rank 2
12458 DNSBL rank 3
5113 DNSBL rank 4
1099 DNSBL rank 5
1 DNSBL rank 7
Q1: Given the postscreen invocation in main.cf below the sig, what is
t
On 3/12/2011 7:31 PM, Wietse Venema wrote:
[snip]
The problem is that the larger alphabet and longer queue IDs increase
the possibility that existing words will appear inside queue IDs
(consider that the letters C, F, K and U are in the base 32 alphabet
and that a queue ID can be 12 characters l
> The idea is to prepend the 30 least significant bits of the time
> in seconds to the queue ID.
Btw, 6 more hours to the next 'pretty' decimal unix timestamp: 13
Mark
Today I was testing an option for long Postfix queue IDs (queue
file names) that won't be reused for about 30+ years. The idea is
to prepend the 30 least significant bits of the time in seconds to
the queue ID.
For the long queue IDs I chose an encoding that packs more bits in
a queue ID characte
Le Sat 12/03/2011, Vincent Lefevre disait
> This is a bit old, but...
>
> On 2011-02-17 07:47:29 -0600, Noel Jones wrote:
> > On 2/17/2011 7:32 AM, Nikolaos Milas wrote:
> > >Thanks Witsie,
> > >
> > >Could the use of an IMAP client program (workstation-based or
> > >web-based, like Squirrelmail)
Reinhard Vicinus:
> On 12/03/11 16:56, Wietse Venema wrote:
> > per-user transport map entries:
> >
> > u...@example.comlmtp:
> > ot...@example.com local:
> >
> i think that won't work, because it only allows different transports per
> user. But i want multiple transports per user: mail
Reinhard Vicinus put forth on 3/12/2011 10:44 AM:
> On 12/03/11 16:56, Wietse Venema wrote:
>> per-user transport map entries:
>>
>> u...@example.comlmtp:
>> ot...@example.comlocal:
>>
>>
> i think that won't work, because it only allows different transports per
> user. But i want multi
On 12/3/2011 7:03 μμ, /dev/rob0 wrote:
That ONE message, a "maildir file", is subject to
virtual_mailbox_limit. The maildir structure itself is not.
As discussed earlier in this thread, in order to enforce maildir quotas
the best solution is to use Dovecot with LDA or LMTP and define quotas
On Sat, Mar 12, 2011 at 04:51:22PM +0100, Vincent Lefevre wrote:
> This is a bit old, but...
>
> On 2011-02-17 07:47:29 -0600, Noel Jones wrote:
> > On 2/17/2011 7:32 AM, Nikolaos Milas wrote:
> > >Thanks Witsie,
> > >
> > >Could the use of an IMAP client program (workstation-based or
> > >web-bas
Vincent Lefevre put forth on 3/12/2011 9:51 AM:
> The maximal size in bytes of an individual virtual(8) mailbox or
> maildir file, or zero (no limit).
>
>
> Is it a bug in the documentation?
No, it's not a bug. As you know maildir storage format stores one email
_per fi
On 12/03/11 16:56, Wietse Venema wrote:
per-user transport map entries:
u...@example.comlmtp:
ot...@example.com local:
i think that won't work, because it only allows different transports per
user. But i want multiple transports per user: mail for all user should
be delivere
Wietse Venema put forth on 3/12/2011 8:43 AM:
> Stan Hoeppner:
>> It appears I did understand Giovanni's need correctly. He should be
>> able to use Sahil's checkdbl.pl daemon with some modifications. He'd
>> simply check that X-custom-header exists. If it doesn't,
>
> Wietse:
>> header_check
Stan Hoeppner:
> Wietse Venema put forth on 3/12/2011 9:00 AM:
>
> > With Postfix, ALL SMTP DESTINATIONS are subject to MX lookup unless
>
> Thank you for clarifying this Wietse. I don't recall seeing this
> explicitly stated in postconf 5
This SMTP client property is documented in the SMTP cli
On 12/3/2011 5:55 μμ, Wietse Venema wrote:
There is no code to store multiple original recipients with each
recipient in queue files, to read multiple original recipients from
queue files, to log multiple original recipients, to prepend multiple
X-Original-To: headers upon delivery, or other cod
Reinhard Vicinus:
> Hi,
>
> i'm in the process of replacing the lmtp backend of our mailservers. For
> testing the new lmtp backend i would like to deliver mails for selected
> users to both, the new and the old lmtp backend.
>
> In the past i have made a similar transition but with exim as mta
Nikolaos Milas:
> Sorry Wietse,
>
> I would never say Postfix is a probabilistic machine - we all trust it
> fully.
>
> But, if a message is sent to: a...@example.com, j...@example.com,
> n...@example.com and jack is a member of group aliases: all and noc, and
> even jack is an alias to real a
Wietse Venema put forth on 3/12/2011 9:00 AM:
> With Postfix, ALL SMTP DESTINATIONS are subject to MX lookup unless
Thank you for clarifying this Wietse. I don't recall seeing this
explicitly stated in postconf 5, but I do recall seeing "use [] to
disable MX lookups" in the text of many paramete
This is a bit old, but...
On 2011-02-17 07:47:29 -0600, Noel Jones wrote:
> On 2/17/2011 7:32 AM, Nikolaos Milas wrote:
> >Thanks Witsie,
> >
> >Could the use of an IMAP client program (workstation-based or
> >web-based, like Squirrelmail) to access the incoming ("new/"
> >Maildir) mailbox, someho
Hi,
i'm in the process of replacing the lmtp backend of our mailservers. For
testing the new lmtp backend i would like to deliver mails for selected
users to both, the new and the old lmtp backend.
In the past i have made a similar transition but with exim as mta. With
exim this is very easi
Sorry Wietse,
I would never say Postfix is a probabilistic machine - we all trust it
fully.
But, if a message is sent to: a...@example.com, j...@example.com,
n...@example.com and jack is a member of group aliases: all and noc, and
even jack is an alias to real address: jack.br...@example.com
Stan Hoeppner:
> I've often wondered why MX lookups aren't disabled automatically when
> setting relayhost=.
Wietse:
> Because there is no way to turn it on! A feature that can't be
> turned off is a bug.
Stan Hoeppner:
> Maybe I asked my question in the wrong way Wietse. What I'm wondering
>
Nikolaos Milas:
> Is it possible to have both duplicate elimination AND (additional)
> logging of the original recipient(s) along with the final recipient
> addresses? This is a valuable piece of information.
No, because the information would be incorrect.
If you receive a message for X with m
Stan Hoeppner:
> It appears I did understand Giovanni's need correctly. He should be
> able to use Sahil's checkdbl.pl daemon with some modifications. He'd
> simply check that X-custom-header exists. If it doesn't,
Wietse:
> header_checks can't detect missing headers.
Stan Hoeppner:
> The hea
A question related to those settings:
When we activate these settings (in v. 2.8.1) duplicates are eliminated
indeed, but in the logs I see that there is no more any indication of
the original recipient.
Is it possible to have both duplicate elimination AND (additional)
logging of the origin
On 3/12/2011 7:14 AM, Stan Hoeppner wrote:
Wietse Venema put forth on 3/11/2011 8:57 PM:
Stan Hoeppner:
It appears I did understand Giovanni's need correctly. He should be
able to use Sahil's checkdbl.pl daemon with some modifications. He'd
simply check that X-custom-header exists. If it doe
Am 12.03.2011 14:19, schrieb Stan Hoeppner:
> Wietse Venema put forth on 3/11/2011 8:55 PM:
>> Stan Hoeppner:
>>> I've often wondered why MX lookups aren't disabled automatically when
>>> setting relayhost=.
>>
>> Because there is no way to turn it on! A feature that can't be
>> turned off is a
Wietse Venema put forth on 3/11/2011 8:55 PM:
> Stan Hoeppner:
>> I've often wondered why MX lookups aren't disabled automatically when
>> setting relayhost=.
>
> Because there is no way to turn it on! A feature that can't be
> turned off is a bug.
>
> Wietse
Maybe I asked my question in
Wietse Venema put forth on 3/11/2011 8:57 PM:
> Stan Hoeppner:
>> It appears I did understand Giovanni's need correctly. He should be
>> able to use Sahil's checkdbl.pl daemon with some modifications. He'd
>> simply check that X-custom-header exists. If it doesn't,
>
> header_checks can't dete
On Sat, 12 Mar 2011, mouss wrote:
- write your own policy server or milter
Hi,
There is a GeoIP policy server out there if you search around, it is
called: geoip-policyd-0.01.tar.gz
With some modifications, it works quite nicely.
Justin.
Le 11/03/2011 12:50, Ulrich Mierendorff a écrit :
> On 09.03.2011 21:38, Murray S. Kucherawy wrote:
>>> -Original Message-
>>> From: owner-postfix-us...@postfix.org
>>> [mailto:owner-postfix-us...@postfix.org] On Behalf Of Victor Duchovni
>>> Sent: Tuesday, March 08, 2011 2:02 PM
>>> To: po
Le 10/03/2011 16:35, Mark Watts a écrit :
>
> I'd like to be able to reject connections from remote IP addresses if
> they're from certain countries (or conversely only allow from certain
> countries).
>
> What are my options for doing this in/with postfix?
- you can also use
http://coun
31 matches
Mail list logo
