Am 11.02.2013 04:53, schrieb Simon Walter:
> On 02/11/2013 05:46 AM, Reindl Harald wrote:
>>
>> what are you using for IMAP?
>> if dovecot throw away the whole SASL crap!
>>
> Don't you mean "...the whole *Cyrus* SASL crap"? Isn't "smtpd_sasl_type =
> dovecot" using the dovecot implementation
>
Hi,
Due to our traffic increasing, I'd like to split our corporate e-mail
traffic from our transactional traffic (mostly account creations
confimation and order confirmation e-mails) to different outbound smtp
IP address.
The way we can identify corporate users is either by distinct IP address
or
Noel Jones megan.vbhcs.org> writes:
> Seems like the easiest solution is to put permit_sasl_authenticated
> BEFORE reject_rbl_client. Then no whitelisting is needed.
>
> -- Noel Jones
Hi, thanks for your answer.
Yes, that would be useful, except for malware that steals your credentials,
and
On 2/11/2013 4:00 AM, Fabio Sangiovanni wrote:
> Noel Jones megan.vbhcs.org> writes:
>
>> Seems like the easiest solution is to put permit_sasl_authenticated
>> BEFORE reject_rbl_client. Then no whitelisting is needed.
>>
>> -- Noel Jones
>
> Hi, thanks for your answer.
> Yes, that would be
Just a heads up for any FreeBSD users who were bitten by the resent
openssl bug. The FreeBSD ports version has been updated to
openssl-1.0.1_7 (/usr/ports/security/openssl/) and works fine now with
Postfix. I just installed and tested it. There is no need to rebuild
Postfix either.
--
Jerry ✌
pos
Noel Jones megan.vbhcs.org> writes:
> Your method of manually whitelisting any IP that happens to be
> spamhaus listed doesn't scale very well. Every time some authorized
> user travels somewhere, stops at a wifi hotspot, or their home IP
> changes, will need to call you to get whitelisted before
Viktor Dukhovni dukhovni.org> writes:
> Replace "OK" with:
>
> /etc/postfix/whitelist_client.cidr:
> 192.0.2.1/32permit_sasl_authenticated
>
Sorry Viktor,
I have another question: what happens if a client is whitelisted AND it fails
SASL authentication?
I suppose that the foll
Hello,
I am using Postfix 2.9.4 on CentOS 6.3 as a gateway server with the
following postscreen settings:
postscreen_dnsbl_threshold = 2
postscreen_dnsbl_sites =
b.barracudacentral.org*2,
zen.spamhaus.org*2,
psbl.surriel.com*2
postscreen_dnsbl_action = enforce
postscree
Am 11.02.2013 17:13, schrieb Nikolaos Milas:
> Sometimes I receive complaints from some mail server operators that
> barracudacentral causes blocks of mail from
> their server, and "Very few email providers use Barracuda for their RBL's, so
> it is not an RBL we check very often
> or rely on"
On 2/11/2013 11:13 AM, Nikolaos Milas wrote:
Hello,
I am using Postfix 2.9.4 on CentOS 6.3 as a gateway server with the
following postscreen settings:
postscreen_dnsbl_threshold = 2
postscreen_dnsbl_sites =
b.barracudacentral.org*2,
zen.spamhaus.org*2,
psbl.surriel.com*2
postscreen_dnsbl_act
On 2/11/2013 10:13 AM, Nikolaos Milas wrote:
> Hello,
>
> I am using Postfix 2.9.4 on CentOS 6.3 as a gateway server with the
> following postscreen settings:
>
> postscreen_dnsbl_threshold = 2
> postscreen_dnsbl_sites =
> b.barracudacentral.org*2,
> zen.spamhaus.org*2,
>
On Mon, Feb 11, 2013 at 03:19:52PM +, Fabio Sangiovanni wrote:
> I have another question: what happens if a client is whitelisted AND it fails
> SASL authentication?
The whitelist only applies to authenticated users. Unauthenticated users
are treated like everyone else.
> I suppose that the
Am 11.02.2013 19:56, schrieb Miha Valencic:
> Hi!
>
> Just want to double check if I am planning this correctly. We're migrating
> users from one system to another, and
> want to HOLD incoming messages for certain recipients during migration. For
> that purpose, we'll create a file with
> user
Hi,
running:
Postfix 2.9.5
Output of uname -a:
SunOS hostname 5.10 Generic_147440-27 sun4v sparc sun4v
Running multiple instances in a multi-instance setup: the instance that
is used and for which an SMTP client has problems is named postfix-app.
Output of postconf -n :
# /opt/postfix/sbin
Viktor Dukhovni dukhovni.org> writes:
> You're working too hard, the suggested settings should work just fine.
Would you be so kind to point me to some readings on the matter? The only
relevant piece of documentation seems to be RESTRICTION_CLASS_README, but, even
after reading that, it's not
Rolf E. Sonneveld:
> In general, Postfix is running fine and this Postfix instance is also
> running fine. However, there is one SMTP client (of which we are not in
> control), that sends messages with long lines to this server running
> Postfix. There is a problem with the communication between
Hi,
on my backup relay server i find these lines in the logs.
i rebuild openssl and postfix.
i am on gentoo linux.
openssl 1.0.1c
postfix 2.9.6
on the final destination postfix server in the logs all is fine.
this only appears on the backup relay server:
Feb 11 22:52:52 fallbackhost postfix/
we...@zackbummfertig.de:
> Feb 11 22:52:52 fallbackhost postfix/smtp[18823]: warning: TLS library
> problem: 18823:error:04075070:rsa routines:RSA_sign:digest too big for
> rsa key:rsa_sign.c:127:
> Feb 11 22:52:52 fallbackhost postfix/smtp[18823]: warning: TLS library
> problem: 18823:error:140
I am seeing the following in the postfix logs, and we are having a delivery
problem to blarg.com. However the destination_concurrency_limit reported at
20 took my by surprise. I was under the impression we had already set it
higher.
Feb 11 12:36:08 email postfix/qmgr[23132]: warning: mail for blar
We override the syslog_name in the master.cf so that we can run pflogsumm
on the resulting log files (split out by rsyslog) and we began noticing
discrepancies.
Typical line in master.cf
smtp104_120_110_27 unix - - n - 150 smtp -o
smtp_bind_address=104.120.110.27 -o syslog_name=postfix-app1 -o
s
Hi
Thanks for you answers
I continue with the problem and I don't know where I can check more. At
now the situation is
-Sends mails deferred
-In logs appears:
Feb 12 01:20:50 mailserver postfix/smtpd[16653]: warning:
smtpd_tls_security_level: unsupported TLS level "verify", using "encrypt"
Feb
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-2.10.0.html]
Postfix stable release 2.10.0 is available. As of now, Postfix 2.6
is no longer updated.
Main changes (see the RELEASE_NOTES file for details):
* Separation of relay policy (
Donovan Bray:
> smtp104_120_110_27 unix - - n - 150 smtp -o
> smtp_bind_address=104.120.110.27 -o syslog_name=postfix-app1 -o
> smtp_helo_name=mail-27.redacted.com
This overrides the logging from the Postfix smtp(8) client.
> We noticed that there were errors in the main mail.log file that refer
Am 2013-02-12 01:07, schrieb Wietse Venema:
we...@zackbummfertig.de:
Feb 11 22:52:52 fallbackhost postfix/smtp[18823]: warning: TLS
library
problem: 18823:error:04075070:rsa routines:RSA_sign:digest too big
for
rsa key:rsa_sign.c:127:
Feb 11 22:52:52 fallbackhost postfix/smtp[18823]: warning
On Mon, Feb 11, 2013 at 11:58:07PM +0100, we...@zackbummfertig.de wrote:
> on my backup relay server i find these lines in the logs.
> i rebuild openssl and postfix.
> i am on gentoo linux.
>
> openssl 1.0.1c
Gentoo builds software from source, are you sure you built OpenSSL
1.0.1c and not the t
On Tue, Feb 12, 2013 at 01:36:15AM +0100, deconya wrote:
> Thanks for you answers
>
> I continue with the problem and I don't know where I can check more. At
> now the situation is
>
> -Sends mails deferred
>
> -In logs appears:
>
> Feb 12 01:20:50 mailserver postfix/smtpd[16653]: warning:
> s
26 matches
Mail list logo
