I have started receiving the transcript below from one of our email servers.
The pattern is consistent with one email queued and being retried from
serv1.copahost.com, i.e. it repeats from same host, but less and less
frequently as if backing off.
I've tried to contact the remote admin to see i
Zhang Huangbin wrote:
>
> On Oct 10, 2009, at 2:55 AM, Eero Volotinen wrote:
>
>> I am currently using postfix 2.3.x on RHEL for mail proxy and mailserver.
>>
>> Is there any good reason to update to 2.6 ? and if is, is there any
>> good and stable rpm repositories for RHEL 5 on web ?
>
> As i k
Zhang Huangbin:
>
> On Oct 10, 2009, at 2:55 AM, Eero Volotinen wrote:
>
> > I am currently using postfix 2.3.x on RHEL for mail proxy and
> > mailserver.
> >
> > Is there any good reason to update to 2.6 ? and if is, is there any
> > good and stable rpm repositories for RHEL 5 on web ?
>
>
Simon Waters:
> In: RCPT TO:
> Out: 451 4.3.5 Server configuration error
The details are logged to the MAILLOG file.
Postfix does not disclose config errors in
responses to random SMTP clients.
Wietse
On Tuesday 13 October 2009 11:38:36 Wietse Venema wrote:
> Simon Waters:
> > In: RCPT TO:
> > Out: 451 4.3.5 Server configuration error
>
> The details are logged to the MAILLOG file.
Darn missed it when I looked.
Oct 13 06:30:57 bannerman postfix/smtpd[17691]: warning: unknown smtpd
restrict
Zhang Huangbin kirjoitti:
On Oct 10, 2009, at 2:55 AM, Eero Volotinen wrote:
I am currently using postfix 2.3.x on RHEL for mail proxy and mailserver.
Is there any good reason to update to 2.6 ? and if is, is there any
good and stable rpm repositories for RHEL 5 on web ?
As i know, postfix
This has been a problem from day one of my postfix installation. I get
the following error in my maillog:
postfix/smtpd[1088]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or directory
This error appears sometimes 2-3 or more times in a row. I'm
Dan Schaefer kirjoitti:
This has been a problem from day one of my postfix installation. I get
the following error in my maillog:
postfix/smtpd[1088]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or directory
This error appears sometimes 2-3 or
Dan Schaefer wrote:
> This has been a problem from day one of my postfix installation. I get
> the following error in my maillog:
>
> postfix/smtpd[1088]: warning: SASL authentication problem: unable to
> open Berkeley db /etc/sasldb2: No such file or directory
>
This is a message from the Cyrus SA
* Dan Schaefer :
> This has been a problem from day one of my postfix installation. I
> get the following error in my maillog:
>
> postfix/smtpd[1088]: warning: SASL authentication problem: unable to
> open Berkeley db /etc/sasldb2: No such file or directory
a) you configured Cyrus SASL to use th
Eero Volotinen wrote:
Dan Schaefer kirjoitti:
This has been a problem from day one of my postfix installation. I
get the following error in my maillog:
postfix/smtpd[1088]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or directory
This error ap
Dan Schaefer wrote:
Eero Volotinen wrote:
Dan Schaefer kirjoitti:
This has been a problem from day one of my postfix installation. I
get the following error in my maillog:
postfix/smtpd[1088]: warning: SASL authentication problem: unable to
open Berkeley db /etc/sasldb2: No such file or dire
I noticed that I have this line:
smtp_sasl_password_maps = mysql:$config_directory/mysql_smtpd.cf
Should I also have this line for smtpd as well?
smtpd_sasl_password_maps = mysql:$config_directory/mysql_smtpd.cf
Are you using dovecot or cyrus? Dovecot has it's own sasl interface
which works
I have a postfix 2.3.3 server, and I *think* I have SASL set up right.
The reason I think it is right is that I have an iphone that connects
fine to Postfix, and sends emails fine through port 587 with the
following logs:
Oct 13 23:33:21 server04 postfix/smtpd[988]: connect from
unknown[1
One thing I note is that "telnet mail.simonandkate.net 587" does not
return AUTH in the list offered:
220 mail.simonandkate.net ESMTP Postfix
EHLO simon.whatever
250-mail.simonandkate.net
250-PIPELINING
250-SIZE 26214400
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
So it
* Simon Wilson :
> I have a postfix 2.3.3 server, and I *think* I have SASL set up
> right. The reason I think it is right is that I have an iphone that
> connects fine to Postfix, and sends emails fine through port 587
> with the following logs:
>
> Oct 13 23:33:21 server04 postfix/smtpd[988]: co
* Eero Volotinen :
>
> >One thing I note is that "telnet mail.simonandkate.net 587" does
> >not return AUTH in the list offered:
> >
> >220 mail.simonandkate.net ESMTP Postfix
> >EHLO simon.whatever
> >250-mail.simonandkate.net
> >250-PIPELINING
> >250-SIZE 26214400
> >250-ETRN
> >250-STARTTLS
> >
you need to use openssl s_client -connect mailserver:port to get the
auth advertising, so pure telnet is not encrypted connection.
Sorry, the correct commandline is:
openssl s_client -starttls smtp -connect mailhost:port
--
Eero
Am Tuesday 13 October 2009 15:52:32 schrieb Simon Wilson:
> Now my wife has just got a Nokia E51. When it tries to send using SMTP
> to the same port 587, it tries to use CRAM-MD5, and the send fails:
>
> Oct 13 23:35:37 server04 postfix/smtpd[988]: setting up TLS connection
> from unknown[58.171.2
2009/10/14 Eero Volotinen :
> Because of:
>
> smtpd_tls_auth_only (default: no)
> When TLS encryption is optional in the Postfix SMTP server, do not announce
> or accept SASL authentication over unencrypted connections.
>
> This feature is available in Postfix 2.2 and later.
>
> you need to use ope
Quoting Patrick Ben Koetter :
The saslauthd password verification service can't deal with
shared-secret
mechanisms such as cram-md5.
Remove "cram-md5" from $mech_list in /usr/lib64/sasl2/smtpd.conf
and the Nokia
E51 should be able to auth.
p...@rick
You guys rock... I am so impressed by no
Hi, all.
smtpd_sender_login_maps is missing in proxy_read_maps, is it a good
idea to add it by default? so that we can use proxymap(8) in
smtpd_sender_login_maps (with default proxy_read_maps).
--
Best Regards.
Zhang Huangbin
- Open Source Mail Server Solution for Red Hat(R) Enterprise L
Eero Volotinen wrote:
I noticed that I have this line:
smtp_sasl_password_maps = mysql:$config_directory/mysql_smtpd.cf
Should I also have this line for smtpd as well?
smtpd_sasl_password_maps = mysql:$config_directory/mysql_smtpd.cf
Are you using dovecot or cyrus? Dovecot has it's own sasl
Hello everybody,
A software we use in house is sending e-mails that are processed by postfix
which relays them to an exchange server that has a connection to the internet
(unlike the sending server).
Recently, the admin of the exchange server forwarded me the following error
message our server
On Tuesday 13 October 2009 15:40:32 Iseli, Erich wrote:
>
> I then had a look at the messages kept in /var/spool/postfix/hold with
> postcat and I couldn't believe my eyes: actually postfix must be mangling
> something since the "from"-address is absolutely correct!
> sender: @domain.com
The sen
* Iseli, Erich :
> From ""@domain.com Tue Oct 13 13:53:47 2009
envelope sender
> Return-Path: <""@domain.com>
envelope sender
> From:Name
header from
> I then had a look at the messages kept in /var/spool/postfix/hold with
> postcat and I couldn't believe my eyes: actually postfix mus
* Iseli, Erich :
> Hello everybody,
>
> A software we use in house is sending e-mails that are processed by postfix
> which relays them to an exchange server that has a connection to the
> internet (unlike the sending server).
The software you use inhouse does not specify a valid envelope sender.
Zhang Huangbin:
> Hi, all.
>
> smtpd_sender_login_maps is missing in proxy_read_maps, is it a good
> idea to add it by default? so that we can use proxymap(8) in
> smtpd_sender_login_maps (with default proxy_read_maps).
I see no problem with doing this.
Wietse
>
> --
> Best Regards
On Tue, Oct 13, 2009 at 01:05:18PM -0400, Wietse Venema wrote:
> Zhang Huangbin:
> > Hi, all.
> >
> > smtpd_sender_login_maps is missing in proxy_read_maps, is it a good
> > idea to add it by default? so that we can use proxymap(8) in
> > smtpd_sender_login_maps (with default proxy_read_maps)
Victor Duchovni:
> On Tue, Oct 13, 2009 at 01:05:18PM -0400, Wietse Venema wrote:
>
> > Zhang Huangbin:
> > > Hi, all.
> > >
> > > smtpd_sender_login_maps is missing in proxy_read_maps, is it a good
> > > idea to add it by default? so that we can use proxymap(8) in
> > > smtpd_sender_login_ma
Hello all -
I've run Postfix for many years, and really is an excellent piece of work.
Whist rebuilding a server recently I decided to try integrating the
anti-virus and anti-SPAM filters via smtpd's milter interface. I've always
previously done so via a content filter (amavisd-new).
To be
> >From
> Received: from CLIENT (client.my.domain [xx.xx.xx.xx]) by server.my.domain
> Message-ID:
Postfix always produces Received: headers that include "by servername
(Postfix) with protocolname", followed by "for " if the
message has only one recipient.
If that information is deleted, then y
Wietse Venema:
> > From
> > Received: from CLIENT (client.my.domain [xx.xx.xx.xx]) by server.my.domain
> > Message-ID:
First of all, that "From " line is an mbox header that
POSTFIX never sends to milter applications.
> Postfix always produces Received: headers that include "by servername
> (Po
On Oct 14, 2009, at 4:42 AM, Wietse Venema wrote:
A little background may be in order.
Thanks Victor and Wietse for your detail description.
In my case, smtpd_sender_login_maps only lookup username field in LDAP/
MYSQL, so i think it's safe to add it in proxy_read_maps manually.
right?
On Wed, Oct 14, 2009 at 10:25:49AM +0800, Zhang Huangbin wrote:
>
> On Oct 14, 2009, at 4:42 AM, Wietse Venema wrote:
>>
>> A little background may be in order.
>
> Thanks Victor and Wietse for your detail description.
>
> In my case, smtpd_sender_login_maps only lookup username field in
> LDAP/M
Fons van der Beek wrote:
Hello all,
I have a SBS server that has several users from different domains,
receiving mails for several domains on the SBS box is no problem.
The problem is in sending.
Suppose I use postfix as an outgoing smarthost, but this smart host
should rewrite the senders a
36 matches
Mail list logo
