Am 04.09.2012 08:37, schrieb Robert Schetterer:
> Am 03.09.2012 20:36, schrieb Eddy Ilg:
>> Dear Postfix List,
>>
>>
>> I'd like to continously update whitelist for spamassassin of recipients
>> that my sasl users have sent mail to (i.e. when the recipients reply
>> they will surely not be consider
Am 03.09.2012 20:36, schrieb Eddy Ilg:
> Dear Postfix List,
>
>
> I'd like to continously update whitelist for spamassassin of recipients
> that my sasl users have sent mail to (i.e. when the recipients reply
> they will surely not be considered as spam). I am not using per-user
> spamassassin co
On 9/2/2012 11:14 AM, Sam Jones wrote:
On Sun, 2012-09-02 at 15:39 +, Viktor Dukhovni wrote:
On Sun, Sep 02, 2012 at 10:43:07AM +0100, Sam Jones wrote:
More to satisfy my own curiosity than anything else, I'm wondering about
the performance that could be squeezed out of Postfix in a bulk m
On Mon, 2012-09-03 at 19:36:46 -0400, b...@bitrate.net wrote:
> i have an mx which then subsequently delivers incoming mail from the
> internet to another computer [ via relay_transport =
> relay-mda:[mda.example.com]:smtp-relay ] for further processing.
> while performing some maintenance on mda.
On 9/3/2012 5:44 PM, Joey Prestia wrote:
> On 9/3/2012 10:43 AM, Viktor Dukhovni wrote:
>> Sadly, Yahoo discriminates the Postfix connection cache which limits
>> connection re-use by time rather than delivery count. Limiting by
>> delivery count behaves poorly when one or more of the MX hosts for
Am 04.09.2012 01:15, schrieb Titanus Eramius:
>> where do you see a risk of silent data corruption?
>>
>> if this would be the case it would be simply
>> impossible have a omplete dbmail-database running
>> on a replication salve over 3 years with a lot of
>> foreign constraints and a major schem
hi-
i have an mx which then subsequently delivers incoming mail from the internet
to another computer [ via relay_transport =
relay-mda:[mda.example.com]:smtp-relay ] for further processing. while
performing some maintenance on mda.example.com, i'd like to configure postfix
on the mx to accep
On Tue, 04 Sep 2012 00:39:08 +0200
Reindl Harald wrote:
> Am 03.09.2012 23:56, schrieb Titanus Eramius:
> >
> > MySQL Replication, which seems a bit dodgy, with the risk of silent
> > data corruption.
>
> where do you see a risk of silent data corruption?
>
> if htis would be the case it would
On Mon, 2012-09-03 at 23:56 +0200, Titanus Eramius wrote:
> So, I guess my question is: How do you, good and experienced folks,
> keep your backup MXs updated?
>
> I've looked at two solutions so far:
> MySQL Replication
+1 for mysql replication for backup mail servers. It's been pretty
reliable
On 9/3/2012 10:43 AM, Viktor Dukhovni wrote:
> On Sun, Sep 02, 2012 at 08:07:21PM -0700, Joey Prestia wrote:
>
>> yahoo_destination_concurrency_limit = 20
>
> This setting is trumpted by the setting below:
>
>> yahoo_destination_rate_delay = 1s
>
> You have serialized deliveries to Yahoo, they
Am 03.09.2012 23:56, schrieb Titanus Eramius:
> Hello good folks
>
> I have recently brought my very first mailserver online, and have been
> testing it for the past month or so. Since the setup needs to be
> redundant, I have also brought a secondary mailserver online on it's own
> domain, and
Hello good folks
I have recently brought my very first mailserver online, and have been
testing it for the past month or so. Since the setup needs to be
redundant, I have also brought a secondary mailserver online on it's own
domain, and everything seems to run smoothly.
It's a Debian, Postfix, D
Dear Postfix List,
I'd like to continously update whitelist for spamassassin of recipients
that my sasl users have sent mail to (i.e. when the recipients reply
they will surely not be considered as spam). I am not using per-user
spamassassin configurations (only a global configuration).
I'v
On Sun, Sep 02, 2012 at 08:07:21PM -0700, Joey Prestia wrote:
> yahoo_destination_concurrency_limit = 20
This setting is trumpted by the setting below:
> yahoo_destination_rate_delay = 1s
You have serialized deliveries to Yahoo, they happen one at a time.
Given that each delivery takes ~5s, the
On Sun, 2012-09-02 at 22:46 +0200, Lorens Kockum wrote:
> The exact same question was sent by someone calling himself
> "Ron White" to the exim mailing list at almost exactly the same
> time. Peddling one's services by soliciting comparisons with
> competitors is so passé . . .
>
Yes, it was. Well
an...@isac.gov.in:
> Dear List,
>
> I have following header_check
>
> /^X-ABC:.*XYZ.*/ DUNNO
This matches X-ABC: followed by whatever, followed by XYZ.
> !/^X-ABC:.*XYZ.*/ FILTER smtp:a.b.c.d:
This matches ALL OTHER MESSAGE HEADERS.
Wietse
DTNX Postmaster wrote:
They aren't my perfect world criteria, but a direct quote from Sam
Jones' earlier buzzword compliant reply.
It was meant to illustrate the often ridiculous nature of vendor
benchmarks, how useless they are in real world situations, and
therefore how silly it is to pick s
On 9/3/2012 3:50 AM, Stan Hoeppner wrote:
> On 9/2/2012 10:07 PM, Joey Prestia wrote:
>> Hi all,
>>
>> I am familiar with yahoo being difficult to send email to
>
> [snip]
>
>> Can anyone offer any guidance on what direction I need to go?
>
> Start here:
> http://help.yahoo.com/l/us/yahoo/mail/p
Dear List,
I have following header_check
/^X-ABC:.*XYZ.*/ DUNNO
!/^X-ABC:.*XYZ.*/ FILTER smtp:a.b.c.d:
I tried these header checks with warn, and only one is getting matched
based on headers which I send.
But, what I find is, when actual mail is sent, always second header
gets acti
On Sep 3, 2012, at 13:05, Stan Hoeppner wrote:
> On 9/3/2012 12:02 AM, DTNX Postmaster wrote:
>
>> In other words, if 'we strip this back to hypothetical and assume a
>> perfect world without any issues', this 'GreenArrow' maxes out at
>> 300,000 messages per hour. Postfix can send 10,8 million
On 9/3/2012 12:02 AM, DTNX Postmaster wrote:
> In other words, if 'we strip this back to hypothetical and assume a
> perfect world without any issues', this 'GreenArrow' maxes out at
> 300,000 messages per hour. Postfix can send 10,8 million messages per
> hour, more than 35 times as fast*.
In
On 9/2/2012 10:07 PM, Joey Prestia wrote:
> Hi all,
>
> I am familiar with yahoo being difficult to send email to
[snip]
> Can anyone offer any guidance on what direction I need to go?
Start here:
http://help.yahoo.com/l/us/yahoo/mail/postmaster/bulkv2.html
--
Stan
On Mon, Sep 03, 2012 at 10:28:06AM +0200, Helga Mayer wrote:
[...]
> >user name jhondoe
> >password 12345678
> >
> >but when user authenticate 12345678__-- authenticate again.
> >
> >but when users enter a12345678 can't authenticate
> The first 8 characters matter. This looks like a problem of the
On 09/03/2012 09:51 AM, Selcuk Yazar wrote:
Hi,
we have weird issue on postfix smtp
authenticaion(postfix-openldap-dovecot).
one user enter wrong characters after his correct password
authentication again.
i mean
user name jhondoe
password 12345678
but when user authenticate 12345678__--
* Viktor Dukhovni :
> Running a high volume bulk email platform is not a software problem.
> It is a logistics problem. Enrolling on the whitelists and feedback
> loops of various large email providers, handling bounce-backs,
> jumping through rate-limit hoops, ...
Absolutely.
--
Ralf Hildebran
* Sam Jones :
> More to satisfy my own curiosity than anything else, I'm wondering about
> the performance that could be squeezed out of Postfix in a bulk mailing
> capacity.
The problem is mostly on the receiving side, when the receiving system
starts throtteling you.
> I have a client that cur
26 matches
Mail list logo
