at
copies all mail received to a local account before relaying and let them sort
through duplicates, but this is not ideal.
--
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.
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
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
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
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:
> > > &g
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:
> >>>
> >
using standard configuration
or if I'd have to roll my own relay service for this.
--
Melvyn Sopacua
can ssh into the machine, and enter:
echo test|mail -s'test' u...@example.com
If this goes through without problems, the php script does 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
This sounds more like something for a policy server. Take a look at postgrey
for example, it defers mail based on criteria postfix does not care about.
All information is available to a policy server to enforce the delay policy
you're describing.
--
Melvyn Sopacua
that fall outside of the
realm of the mailserver.
Delaying mail is one of those policies, as the nature of a mailserver is to
deliver mail as fast as possible.
--
Melvyn Sopacua
esults,
> sending them off to mail() or whatever one at a time.
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
d so
do not know whether rpm can run replace commands on sources.
[1] sed -i.bak -e 's/sendmail\.1/sendmail.postfix.1/' -e
's/aliases.5/aliases.postfix.5/' conf/postfix-files
--
Melvyn Sopacua
sses will appreciate the
perty graphs.
Other points adequately addressed by Victor.
[1] http://www.lyris.com/solutions/lyris-hq/
--
Melvyn Sopacua
When sending from Gmail for instance I get the following error:
>
> *'501 5.1.3 Bad recipient address syntax' *
Let me guess, option1 contains either '<' or '>':
RCPT TO: text=|12...@localhost
501 5.1.3 Bad recipient address syntax
RCPT TO: |12...@localhost>
501 5.1.3 Bad recipient address syntax
--
Melvyn Sopacua
t;
> this would be a server which i would like to recieve mail from !
>
> i grep'd throu the log:
Instead grep for 'reject:'.
--
Melvyn Sopacua
; Can someone say me how can i do my job more confortable 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
d
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:
> > > Also, any technical objections against moving shared files into an nfs
> > > mounted directory
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
> >
ons=permit_mynetworks,reject
-o mynetworks=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
the mail 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
even grok), which matches those log
lines and then generates status messages to be delivered through procmail or
anything that's not using postfix (otherwise you'll loop yourself).
--
Melvyn Sopacua
plication generates these forwards -
configure it to send with some form of SMTP authentication so that the MAIL
FROM does not matter.
--
Melvyn Sopacua
On Friday 22 May 2009 08:50:28 Dr.Pesko wrote:
> Melvyn Sopacua wrote:
> > On Wednesday 20 May 2009 21:14:39 Dr.Pesko wrote:
> >> On 5/20/2009 1:03 AM, mouss wrote:
> >>> Dr.Pesko a écrit :
> >>>> Hello everyone,
> >>>>
> >>>
ve to use human grepping to make
the relation between these two mails. Or maybe grepping for
tcampb...@server.us will shed some light.
--
Melvyn Sopacua
ferent logic:
"Rewrite all domains and rewrite again for specific usernames".
--
Melvyn Sopacua
en you 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
- To evaluate the amount of false positives
- To collect and seed a Bayesian spam filter before deploying
--
Melvyn Sopacua
28 matches
Mail list logo
