On Thu, 21 Jan 2010 19:35:25 -0500 (EST), wie...@porcupine.org (Wietse
Venema) wrote:
Martijn de Munnik:
Jan 21 17:02:30 marcus postfix/qmgr[16421]: 523FD1C11A:
from=mart...@youngguns.nl, size=650750, nrcpt=1 (queue active)
Jan 21 17:02:30 marcus postfix/smtp[16449]: 523FD1C11A: host
It works like a charm.
Thanks a lot.
On Thu, 2010-01-21 at 13:36 -0500, Wietse Venema wrote:
Victor Duchovni:
On Thu, Jan 21, 2010 at 02:57:17PM +0100, Mickael CANEVET wrote:
Hi,
I'd like postfix to treat EX_CANTCREAT (73) as temporary failure.
I use this command to
Stan Hoeppner put forth on 1/22/2010 1:28 AM:
I've wondered for a couple of months why my rbl check is being skipped. I've
not seen a spamhaus entry in my logs since Sept 25 '09. Interestingly,
postgrey
is being called now and then, and it is after the rbl check in main.cf. Any
idea why
Messages containing leading whitespace in the recipient address are
rejected.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient address rejected: User unknown in virtual alias table;
* Doug Robbins drobb...@smartlabrador.ca:
Messages containing leading whitespace in the recipient address are
rejected.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient address
Doug Robbins:
Messages containing leading whitespace in the recipient address are
rejected.
Only if the recipient does not exist.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient
Hi List,
RFC2821 section 4.5.3.2 Timeouts reads
An SMTP server SHOULD have a timeout of at least 5 minutes while it
is awaiting the next command from the sender.
When I try to connect to an one.com mx (mx-cluster1.one.com or
mx-cluster2.one.com) I notice they will close the connection after
Stan Hoeppner wrote:
1. Spamhaus has banned Google Public DNS resolver queries.
Stan,
Do you have a good enough reason to not run your own name resolver on
your front MX machine?
IMO relying on third parties for DNS on an MX is bad design.
Mikael
On 22-Jan-2010 10:11 AM, Wietse Venema wrote:
Doug Robbins:
Messages containing leading whitespace in the recipient address are
rejected.
Only if the recipient does not exist.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]:
On Fri, Jan 22, 2010 at 09:40:58AM -0330, Doug Robbins wrote:
Is there something I can do to avoid these rejections (other than
the obvious -- get dba...@example2.com to fix his address book)?
A milter could remove recipients with spaces and add back ones without
spaces. To do it completely
On Fri, Jan 22, 2010 at 02:13:17PM +0100, Ralf Hildebrandt wrote:
Is there something I can do to avoid these rejections (other than the
obvious -- get dba...@example2.com to fix his address book)?
Hm, you could try and alias soli...@example.com to
soli...@example.com
But how???
The
* Victor Duchovni victor.ducho...@morganstanley.com:
This said, far better to just reject this, and let the sender correct
their address list.
Yes.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Stan Hoeppner:
1. Spamhaus has banned Google Public DNS resolver queries. I
didn't know this until today. If Postfix is using Google Public
DNS resolvers, rbl queries to zen.spamhaus.org fail but Postfix
(Debian Lenny 2.5.5-1.1) logs NOTHING about it. Not the query
attempt, not the
Victor Duchovni:
On Fri, Jan 22, 2010 at 02:13:17PM +0100, Ralf Hildebrandt wrote:
Is there something I can do to avoid these rejections (other than the
obvious -- get dba...@example2.com to fix his address book)?
Hm, you could try and alias soli...@example.com to
On Thu, Jan 21, 2010 at 2:43 PM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
This is a client IP not a sender, e. g. 'MAIL FROM: br...@example.com'
The IP should go into a file referenced by a check_client_access
restriction.
I think I still don't have a understanding at how to
Mikael Bak put forth on 1/22/2010 7:50 AM:
Stan Hoeppner wrote:
1. Spamhaus has banned Google Public DNS resolver queries.
Stan,
Do you have a good enough reason to not run your own name resolver on
your front MX machine?
IMO relying on third parties for DNS on an MX is bad design.
On Fri, Jan 22, 2010 at 08:34:35AM -0600, Stan Hoeppner wrote:
Mikael Bak put forth on 1/22/2010 7:50 AM:
Stan Hoeppner wrote:
1. Spamhaus has banned Google Public DNS resolver queries.
Stan,
Do you have a good enough reason to not run your own name resolver on
your front MX
On Fri, Jan 22, 2010 at 09:16:07AM -0500, Wietse Venema wrote:
The lookup keys and RHS values for virtual(5) are in rfc822 format.
A PCRE table can take care of this:
Virtual alias lookups are done in the unquoted form, while
canonical map lookups are in quoted form.
No, the cleanup(8)
Victor Duchovni:
On Fri, Jan 22, 2010 at 09:16:07AM -0500, Wietse Venema wrote:
The lookup keys and RHS values for virtual(5) are in rfc822 format.
A PCRE table can take care of this:
Virtual alias lookups are done in the unquoted form, while
canonical map lookups are in quoted
On Fri, Jan 22, 2010 at 10:33:58AM -0500, Wietse Venema wrote:
One could argue that the SMTP server should use the external form of the
recipient for these lookup, to match downstream behaviour in cleanup(8)...
Indeed. There was no address validation in the initial design and
On 1/22/2010 6:18 AM, Stan Hoeppner wrote:
1. Spamhaus has banned Google Public DNS resolver queries. I didn't know this
until today. If Postfix is using Google Public DNS resolvers, rbl queries to
zen.spamhaus.org fail but Postfix (Debian Lenny 2.5.5-1.1) logs NOTHING about
it. Not the
Kenneth Marshall put forth on 1/22/2010 8:39 AM:
pdns-recursor 3.1.7.2 is easy to configure/use and has a tuneable
resource footprint.
Got her installed, configured, up and running. Let's see if this improves this
spamhaus situation, and a handful a day of other dns related errors I've been
On Fri, Jan 22, 2010 at 10:40:03AM -0600, Stan Hoeppner wrote:
Kenneth Marshall put forth on 1/22/2010 8:39 AM:
pdns-recursor 3.1.7.2 is easy to configure/use and has a tuneable
resource footprint.
Got her installed, configured, up and running. Let's see if this improves
this
Noel Jones put forth on 1/22/2010 10:00 AM:
Nothing is logged because the DNS server gives an authoritive does not
exist answer. That's not an error, it is the expected response when a
client is not listed in an RBL.
Hi Noel,
I was not venting at Postfix, or Wietse, or any of the devs for
On 22/01/2010 16:58, Stan Hoeppner wrote:
My venting should be aimed at Spamhaus. What they've done here is the opposite
of transparency. In the case of Google DNS, Spamhaus has pulled something a bit
underhanded in my estimation. They don't want people using Google DNS to query
Spamhaus
On Fri, 22 Jan 2010, Stan Hoeppner wrote:
My venting should be aimed at Spamhaus. What they've done here is the opposite
of transparency. In the case of Google DNS, Spamhaus has pulled something a bit
underhanded in my estimation. They don't want people using Google DNS to query
Spamhaus
Mark Goodge put forth on 1/22/2010 11:07 AM:
It's not the fault of
Spamhaus, Google or Postfix if people don't RTFM.
I'll give you that. I'd been using zen for years, and sbl-xbl for years before
that. When I changed my resolvers to Google from my current provider's (for
performance reasons,
Hello
I have this puzzle that I can't figure out. I had my mailing list
working on openSuSE 11.2
with postfix and majordomo. I've been using majordomo on sendmailf or
years with no trouble.
I moved to postfix with no trouble and now, suddenly I'm getting nothing
through to my lists.
I know
On 1/22/2010 10:58 AM, Stan Hoeppner wrote:
Noel Jones put forth on 1/22/2010 10:00 AM:
Nothing is logged because the DNS server gives an authoritive does not
exist answer. That's not an error, it is the expected response when a
client is not listed in an RBL.
Hi Noel,
I was not venting at
On Fri, Jan 22, 2010 at 01:10:51PM -0500, Ruben Safir wrote:
Aliases look like this
majordomo: |/usr/lib/majordomo/wrapper majordomo
This script will run as nobody unless a non-root user owns the
aliases.db file from which this alias is read.
All tutorials on integrating list
On Fri, Jan 22, 2010 at 01:27:06PM -0500, Wietse Venema wrote:
Victor Duchovni:
On Fri, Jan 22, 2010 at 01:10:51PM -0500, Ruben Safir wrote:
Aliases look like this
majordomo: |/usr/lib/majordomo/wrapper majordomo
That's how I run majordomo on my machine.
If I
On Fri, Jan 22, 2010 at 01:18:10PM -0500, Victor Duchovni wrote:
On Fri, Jan 22, 2010 at 01:10:51PM -0500, Ruben Safir wrote:
Aliases look like this
majordomo: |/usr/lib/majordomo/wrapper majordomo
This script will run as nobody unless a non-root user owns the
aliases.db
On Fri, Jan 22, 2010 at 01:27:06PM -0500, Wietse Venema wrote:
If I recall correctly, the wrapper program needs to be installed
set-uid, and it needs to be configured at compile time with the
right uid/gid information.
Ruben Safir:
I made it SIUD and the wrapper config-test seems to believe
On 2010-01-21 8:23 PM, Stan Hoeppner wrote:
Thanks for the heads up. Yes, I'm using IMAP and TB3. So I'm sure
this is the same bug. Interestingly, like I said, the filter on
Sender works fine for newly arriving messages. It just doesn't work
on messages already in the inbox when running the
On 2010-01-22 5:36 PM, Charles Marcus wrote:
Here's the bug:
Sorry, meant to send that direct to Stan...
On 01/22/2010 05:22 PM, Wietse Venema wrote:
On Fri, Jan 22, 2010 at 01:27:06PM -0500, Wietse Venema wrote:
If I recall correctly, the wrapper program needs to be installed
set-uid, and it needs to be configured at compile time with the
right uid/gid information.
Ruben Safir:
I
On 01/22/2010 01:18 PM, Victor Duchovni wrote:
On Fri, Jan 22, 2010 at 01:10:51PM -0500, Ruben Safir wrote:
Aliases look like this
majordomo: |/usr/lib/majordomo/wrapper majordomo
This script will run as nobody unless a non-root user owns the
aliases.db file from
- Original Message
From: Ruben Safir ru...@mrbrklyn.com
To: Postfix users postfix-users@postfix.org
Sent: Sat, January 23, 2010 12:33:53 AM
Subject: Re: Postfix Majordomo problem
On 01/22/2010 05:22 PM, Wietse Venema wrote:
On Fri, Jan 22, 2010 at 01:27:06PM -0500, Wietse Venema
Ruben Safir:
[ Charset ISO-8859-1 unsupported, converting... ]
On 01/22/2010 05:22 PM, Wietse Venema wrote:
On Fri, Jan 22, 2010 at 01:27:06PM -0500, Wietse Venema wrote:
If I recall correctly, the wrapper program needs to be installed
set-uid, and it needs to be configured at compile
It would help if you posted the log messages you receive along with the
information provided here: http://www.postfix.org/DEBUG_README.html.
After you do that then we can try and help you.
Thanks,
Daniel
Thanks Daniel
The relevant log area says this:
an 22 17:49:47 www2
On 01/22/2010 07:58 PM, Wietse Venema wrote:
Majordomo is a Perl script, so you can debug it with all the standard
Perl debugging features.
This discussion is no longer appropriate for the Postfix mailing
list, so this is my last post.
Thanks for the help. What you've told me has been
41 matches
Mail list logo
