On Sat, Oct 10, 2015 at 2:23 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Dan Lists:
> > > > Out: 451 4.3.0 Error: queue file write error
> > Oct 10 09:13:39 nook postfix/cleanup[18080]: fatal: pcre map
> > /usr/local/etc/postfix/body_checks, line 17: matc
I am receiving the transcript file with the error "Error: queue file write
error." It appears that postfix is timing out the connection after 10
minutes. The thing that disturbs me is that nothing is logged. Is there
a way to get postfix to put something in the logs?
Here is the transcript:
On Sat, Oct 10, 2015 at 11:30 AM, Viktor Dukhovni <
postfix-us...@dukhovni.org> wrote:
> On Sat, Oct 10, 2015 at 10:53:12AM -0500, Dan Lists wrote:
>
> > Out: 451 4.3.0 Error: queue file write error
> >
> > And here are the log entries:
> >
> > Oc
We relay email for our customers. They had some accounts Phished. I
wanted to hold email from those users so I could see the spam that was
going out and requeue the valid email.
In main.cf I have:
smtpd_sender_restrictions =
check_sender_access hash:$config_directory/sender_domains,
On Thu, Dec 6, 2012 at 5:09 PM, Noel Jones njo...@megan.vbhcs.org wrote:
On 12/6/2012 4:29 PM, Dan Lists wrote:
We relay email for our customers. They had some accounts Phished. I
wanted to hold email from those users so I could see the spam that was
going out and requeue the valid email
On Tue, Dec 4, 2012 at 5:48 AM, Wietse Venema wie...@porcupine.org wrote:
Taking a quick look at the source, it looks like 2.8 does not use the
thread-safe getpwnam_r. It does not appear that postfix is threaded,
so it should be safe to not use getpwnam_r.
It has NOTHING TO TO WITH THREADS.
On Wed, Dec 5, 2012 at 11:55 AM, Wietse Venema wie...@porcupine.org wrote:
I will not base Postfix development on UNDOCUMENTED return values.
That is unmaintainable.
I've brought it up on the FreeBSD lists. I suggested that it is a bug
for getpwnam_r to act the way it is. I'll probably end
On Fri, Nov 30, 2012 at 1:49 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
Nov 30 10:39:59 server postfix/local[50947]: warning: error looking up
passwd info for user: Invalid argument
The getpwnam_r() SYSTEM LIBRARY ROUTINE reports an error,
with errno set to EINVAL (Invalid
On Mon, Dec 3, 2012 at 5:14 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
[ Charset ISO-8859-1 unsupported, converting... ]
On Fri, Nov 30, 2012 at 1:49 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
Nov 30 10:39:59 server postfix/local[50947]: warning: error looking up
On Mon, Dec 3, 2012 at 7:42 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
Does postfix need to treat the EINVAL as if the user does not exist?
Is there a way to change the behavior of getpwnam*?
EINVAL is not a documented result code.
http://pubs.opengroup.org/onlinepubs
I recently upgraded our mail servers from FreeBSD 7.3 running postfix
2.8.7 to FreeBSD 8.3 running postfix 2.9.3. We have account
information stored in mysql and are using libnns-mysql to access the
information through the normal password routines.
After the upgrade, when a user does not exist I
I am looking to switch one or more of my blacklists to run from
postscreen. I send custom replies based on the blacklist, which
reduces the number of calls I get. The relevant part of my current
configs:
smtpd_client_restrictions =
reject_rbl_client zen.local,
reject_rbl_client
On Thu, Mar 8, 2012 at 4:06 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
How much traffic can postscreen handle? Each mail server in our
cluster handles 800,000 to 1,000,000 messages per day. We typically
This is mainly limited by the whitelist database latency: the
time
On Wed, Mar 14, 2012 at 2:09 PM, Wietse Venema wie...@porcupine.org wrote:
I assume you are referring to the temporary whitelist. I do not see
any way to configure what is uses to store the temporary whitelist.
Is it configurable? Is there any way to share the temp whitelist
between
How much traffic can postscreen handle? Each mail server in our
cluster handles 800,000 to 1,000,000 messages per day. We typically
have 60-120 smptd processes, with peaks as high as 320. Adding a
greeting delay will result in a lot of open connections. Can
postscreen handle this volume even
I am seeing the following in my logs:
Apr 26 10:18:43 mailhost postfix/smtpd[46627]: connect from
unknown[98.118.152.26]
However, the IP does resolve:
mailhost # host 98.118.152.26
26.152.118.98.in-addr.arpa domain name pointer onlinecourseevaluations.com.
mailhost # host
When a user mistypes an email address domain (eg @monsant.com), the
message is sitting in the queue for days before they know about it.
We'd like to give them immediate feedback instead of making them wail.
I'm trying to have the outbound mail server permanently reject email
with an invalid
On Fri, Jan 29, 2010 at 12:22 PM, Noel Jones njo...@megan.vbhcs.org wrote:
On 1/29/2010 11:57 AM, Dan Lists wrote:
When a user mistypes an email address domain (eg @monsant.com), the
message is sitting in the queue for days before they know about it.
We'd like to give them immediate feedback
On Fri, Jan 29, 2010 at 1:17 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
[ Charset ISO-8859-1 unsupported, converting... ]
$ host monsant.com
Host monsant.com not found: 2(SERVFAIL)
This is a temporary error. The name server for monsant.com could not be
contacted. ?You
We host email for several domains. Occasionally an account will get
phished and our outbound server will get blacklisted by hotmail and
others. We'd like to separate the outbound email so that one domain
with a phished account doesn't get all outbound email blacklisted.
I'm trying to set up an
On Fri, Apr 24, 2009 at 6:48 AM, Wietse Venema wie...@porcupine.org wrote:
FYI,
The header_checks parameter does not control whether or not Milter
operation is invoked, so your observations are incorrect.
If you want to pursue this further, show a telnet mail submission
and the
I'm running postfix 2.5.6, and I'm using amavis through the milter interface
by setting 'smtpd_milters= inet:[127.0.0.1]:10023'.
I'm trying to set up a different port for skipping amavis checks on email
that has already been checked. In master.cf I have:
2525inetn - n
On Thu, Apr 23, 2009 at 6:14 PM, Wietse Venema wie...@porcupine.org wrote:
First, show that Postfix receives mail via port 2525. This requires
a transcript of a telnet session, and the Postfix logging for the
corresponding email delivery.
Second, show with ps command output that port 2525
23 matches
Mail list logo
