before deploying
--
Melvyn Sopacua
should have no problems and postfix
does not care what is on the other end of the socket as long as it can write
to it.
--
Melvyn Sopacua
and then sends it elsewhere. But where did you read about
this? Terms are usedinconsistently. Even pine uses Bounce for Forward
without alteration of body and existing headers.
--
Melvyn Sopacua
you'll loop yourself).
--
Melvyn Sopacua
=127.0.0.1/32
-o smtpd_authorized_xforward_hosts=127.0.0.1/32
dspam.conf:
ServerDomainSocketPath /var/run/dspam.sock
DeliveryHost127.0.0.1
DeliveryPort10026
DeliveryIdent dspam.example.com
DeliveryProto SMTP
--
Melvyn Sopacua
and only do one
time.
Instead of a local file, use LDAP or SQL (with replicated database).
If other then performance, why replicated?
Also, any technical objections against moving shared files into an nfs mounted
directory and adjusting main.cf to look there?
--
Melvyn Sopacua
On Friday 17 April 2009 14:01:07 Wietse Venema wrote:
Wietse Venema:
Melvyn Sopacua:
On Friday 17 April 2009 01:23:20 Wietse Venema wrote:
snip replication
Also, any technical objections against moving shared files into an nfs
mounted directory and adjusting main.cf to look
On Friday 17 April 2009 18:16:01 Victor Duchovni wrote:
On Fri, Apr 17, 2009 at 06:11:24PM +0200, Melvyn Sopacua wrote:
Mailbox files, on the other hand, are usually overwritten, and they
are updated in place. This almost works reliably, especially if
you use dotlock files and turn off
be a server which i would like to recieve mail from !
i grep'd throu the log:
snip irrelevant anvil statistics
Instead grep for 'reject:'.
--
Melvyn Sopacua
/aliases.5/aliases.postfix.5/' conf/postfix-files
--
Melvyn Sopacua
adequately addressed by Victor.
[1] http://www.lyris.com/solutions/lyris-hq/
--
Melvyn Sopacua
the following error:
*'501 5.1.3 Bad recipient address syntax' *
Let me guess, option1 contains either '' or '':
RCPT TO: text=html|12...@localhost
501 5.1.3 Bad recipient address syntax
RCPT TO: text=html|12...@localhost
501 5.1.3 Bad recipient address syntax
--
Melvyn Sopacua
.
Delaying mail is one of those policies, as the nature of a mailserver is to
deliver mail as fast as possible.
--
Melvyn Sopacua
.
At the risk of going too much off-topic, this is a valid solution if the app
stores the data it's going to mail and you can get support for the feature
upstream or it's you own app. Otherwise it's going to be a administrative
nightmare.
--
Melvyn Sopacua
something weird
(I'd check php.ini to start). If your problem persists, then you also have
your transaction log. 2 for 1 debugging.
--
Melvyn Sopacua
Hi Victor,
On Friday 30 January 2009 21:12:30 Victor Duchovni wrote:
On Fri, Jan 30, 2009 at 08:42:22PM -0900, Melvyn Sopacua wrote:
1) Accept mail for example.com as primary MX (yes, possible)
2) Relay to mx2.example.com (yes, possible)
3) If mx2.example.com gives fatal error, reduce
On Saturday 31 January 2009 06:49:28 Terry Carmen wrote:
Melvyn Sopacua wrote:
The reason is that a client has unsolved ongoing configuration issues
with their Exchange server and can no longer afford to loose mail because
of it. The Exchange server is not my problem(tm).
. . .
4
On Saturday 31 January 2009 08:21:56 Sahil Tandon wrote:
On Sat, 31 Jan 2009, Melvyn Sopacua wrote:
@example.comlocalmailbox, |logthis, relay:[mx2.example.com]
Hm, and where is this access map syntax documented?
No where, it's pseudo code to explain what my 'backup' service would do
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
Melvyn Sopacua:
The problem is that postfix will see success initially:
- client sends
- postfix receives
- postfix relays, gets OK
postfix deletes queued message
- exchange checks quota, decides mailbox is full
On Saturday 31 January 2009 09:45:16 Wietse Venema wrote:
Melvyn Sopacua:
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
Melvyn Sopacua:
The problem is that postfix will see success initially:
- client sends
- postfix receives
- postfix relays, gets OK
On Saturday 31 January 2009 09:22:28 Terry Carmen wrote:
Melvyn Sopacua wrote:
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
Melvyn Sopacua:
The problem is that postfix will see success initially:
- client sends
- postfix receives
- postfix relays, gets OK
postfix
configuration
or if I'd have to roll my own relay service for this.
--
Melvyn Sopacua
all mail received to a local account before relaying and let them sort
through duplicates, but this is not ideal.
--
Melvyn Sopacua
23 matches
Mail list logo
