Thank You for Your time and answer, Sahil:
Show relevant logging. If it is indeed amavisd-new where the mail is
rejected (or quarantined for having spammy qualities), then you probably need
to route mail from 1.2.3.4 through a separate 'policy bank' within
amavisd-new where spam checks are
--- In postfix-us...@yahoogroups.com, Pascal Volk user+postfix-us...@...
wrote:
On 06/05/2009 02:25 AM Peter Smith wrote:
If I telnet to my mail server, anyth...@... is accepted. If I
turn up the logging verbosity, I see:
How do you telnet to your server?
`telnet localhost 25`?
Actually
On Friday 05 June 2009 09:24:54 Peter Smith wrote:
virtual_mailbox_domains = $transport_maps
Whats this for?
Are the problem domains listed in /etc/postfix/transport for some reason.
I have an entry in transport:
mydomain.commaildrop:
Is this the problem?
Rob Tanner:
Hi,
I?ve got the front-end of a policy engine in place and connected to postfix
on a test server. All it?s really doing is logging what postfix sends and
returning an ?OK?. What I notice is that when I?ve sent emails through that
server with multiple recipients, rather than
I built and install 2.6.x today:
% make makefile
% make
% make install
on a pristine machine and tried the
multi-instance support. I did this (fresh from my shell, no edits):
r...@hanni:/etc/postfix# postmulti -l -a
- - y /etc/postfix
r...@hanni:/etc/postfix#
All solved now - thanks for your help guys! The changes I made were:
virtual_mailbox_domains = $transport_maps
to:
virtual_mailbox_domains = mydomain.com
Added:
virtual_transport = maildrop
virtual_mailbox_maps = hash:/etc/postfix/virtual
Peter Smith wrote:
On Friday 05 June 2009 09:24:54 Peter Smith wrote:
virtual_mailbox_domains = $transport_maps
Whats this for?
Are the problem domains listed in /etc/postfix/transport for some reason.
I have an entry in transport:
mydomain.commaildrop:
Is this
I'm trying to run two instances, I'm injection on localhost port 10025
into postfix-ram, which has the queue in RAM:
Jun 5 15:35:17 hanni postfix-ram/cleanup[24403]: 45F4A2E369:
message-id=20090605133514.45f4a2e...@nanni.state-of-mind.de
Jun 5 15:35:17 hanni postfix-ram/qmgr[24345]:
Ralf Hildebrandt:
Jun 5 15:35:18 hanni postfix-ram/smtp[24385]: warning: smtp_fallback_relay
configuration problem
smtp_fallback_relay = [194.126.158.237]
I don't think you can set smtp_fallback_relay to the local SMTP port.
Wietse
* Wietse Venema wie...@porcupine.org:
Ralf Hildebrandt:
Jun 5 15:35:18 hanni postfix-ram/smtp[24385]: warning: smtp_fallback_relay
configuration problem
smtp_fallback_relay = [194.126.158.237]
I don't think you can set smtp_fallback_relay to the local SMTP port.
Grmbl. Neither
Wietse Venema:
Ralf Hildebrandt:
Jun 5 15:35:18 hanni postfix-ram/smtp[24385]: warning: smtp_fallback_relay
configuration problem
smtp_fallback_relay = [194.126.158.237]
I don't think you can set smtp_fallback_relay to the local SMTP port.
Unless of course you update the postfix-ram's
Ralf Hildebrandt:
* Wietse Venema wie...@porcupine.org:
Ralf Hildebrandt:
Jun 5 15:35:18 hanni postfix-ram/smtp[24385]: warning:
smtp_fallback_relay configuration problem
smtp_fallback_relay = [194.126.158.237]
I don't think you can set smtp_fallback_relay to the local SMTP
Ralf Hildebrandt:
/usr/libexec/postfix/postfix-script: 346: /bin/env: not found
Replace /bin/env find by `which find`.
Wietse
* Wietse Venema wie...@porcupine.org:
The Postfix SMTP client will never send mail to the SMTP port on
any IP address that is listed in $inet_interfaces. This is part of
the basic loop elimination algorithm that also keeps Postfix from
sending mail to equal-preference MX hosts.
Yes, I
On Fri, Jun 05, 2009 at 10:05:16AM -0400, Wietse Venema wrote:
Ralf Hildebrandt:
/usr/libexec/postfix/postfix-script: 346: /bin/env: not found
Replace /bin/env find by `which find`.
Perhaps /usr/bin/env, will be more portable? It seems that /usr/bin/env
is more correct than /bin/env for
On Fri, 5 Jun 2009 12:51:54 -0400
Victor Duchovni victor.ducho...@morganstanley.com wrote:
Perhaps /usr/bin/env, will be more portable? It seems that /usr/bin/env
is more correct than /bin/env for both Linux and Solaris, does it
also work on *BSD systems? Also find is /usr/bin/find on both.
Victor Duchovni:
On Fri, Jun 05, 2009 at 10:05:16AM -0400, Wietse Venema wrote:
Ralf Hildebrandt:
/usr/libexec/postfix/postfix-script: 346: /bin/env: not found
Replace /bin/env find by `which find`.
Perhaps /usr/bin/env, will be more portable? It seems that /usr/bin/env
is more
On Fri, 5 Jun 2009, Wietse Venema wrote:
Victor Duchovni:
On Fri, Jun 05, 2009 at 10:05:16AM -0400, Wietse Venema wrote:
Ralf Hildebrandt:
/usr/libexec/postfix/postfix-script: 346: /bin/env: not found
Replace /bin/env find by `which find`.
Perhaps /usr/bin/env, will be more portable? It
On Fri, Jun 05, 2009 at 03:30:55PM -0400, Rob Foehl wrote:
Surprisingly enough, which isn't a standard utility -- and it's not
installed by default in the minimal package sets on several platforms,
mostly Linux variants. (Yes, this is annoying.)
/usr/bin/env is probably the safest bet
Noel Jones wrote:
At 03:24 PM 2/7/2007, Dick Middleton wrote:
Is it possible to manually bounce a message in the deferred queue
so preempting the normal retry/timeout period?
I've got a message sitting in the queue trying to connect to a
non-existent server. The sooner it gets bounced back
Jon wrote:
Noel Jones wrote:
At 03:24 PM 2/7/2007, Dick Middleton wrote:
Is it possible to manually bounce a message in the deferred queue
so preempting the normal retry/timeout period?
I've got a message sitting in the queue trying to connect to a
non-existent server. The sooner it gets
Noel Jones wrote:
At 03:24 PM 2/7/2007, Dick Middleton wrote:
Is it possible to manually bounce a message in the deferred queue
so preempting the normal retry/timeout period?
I've got a message sitting in the queue trying to connect to a
non-existent server. The sooner it gets bounced
| type is a built-in in POSIX shells, and even the pre-historic SunOS
| /bin/sh has a type built-in, be it a bare-bones version that does not
| support the -p switch, that is sufficient. So another possibility is:
|
| set -- `type find`
| shift `expr $# - 1`
| # Now, $1 is the full
23 matches
Mail list logo
