2010/2/21 James R. Marcus :
> Hi,
> In regards to having honest headers, is it bad to have localhost.localdomain
> in the an email header?
>
> Received: from localhost (localhost.localdomain [127.0.0.1])
> by relay1.edhance.com (Postfix) with ESMTP id 18D231A7517
> for ; Sat, 20 Feb
Hi,
In regards to having honest headers, is it bad to have localhost.localdomain in
the an email header?
Received: from localhost (localhost.localdomain [127.0.0.1])
by relay1.edhance.com (Postfix) with ESMTP id 18D231A7517
for ; Sat, 20 Feb 2010 23:08:19 -0500 (EST)
James
* El Sat, Feb 20, 2010 at 10:04:59AM -0500, escribiste:
> > > > >> WIthout changes to the existing configuration of 2.6.5 I get this
> > > > >> error
> > > > >> using procmail as my mailbox_command:
> > > > >> Feb 19 18:34:29 adrianvb postfix/local[14290]: BD85F7006D:
> > > > >> to=, orig_to=, re
>
> The solution:
>
> 1) Do not enable SASL authentication on port 25. This is
> used for mail from the Internet.
>
> 2) Enable SASL authentication on the submission port. This is
> used for user mail clients. An example submission service is
> commented out in the default master.cf file.
>
>
Jonathan Tripathy a écrit :
> Hi Everyone,
>
> I'm using tumgreyspf. I need to add the following line to my main.cf to
> make it work:
>
> check_policy_service unix:private/tumgreyspf
>
> Some servers arn't being greylisted. For example, the following appeared
> in my log on the backup mx:
>
>
Victor Duchovni:
> On Sat, Feb 20, 2010 at 03:43:25PM +0530, ram wrote:
>
> > One of our clients sends contract notes to their customers and they
> > require to store all logs of deliveries/bounces by some law.
> >
> > They have requirements like
> >
> > * The log should contain the full date
Hi Everyone,
I'm using tumgreyspf. I need to add the following line to my main.cf to
make it work:
check_policy_service unix:private/tumgreyspf
Some servers arn't being greylisted. For example, the following appeared
in my log on the backup mx:
Feb 20 19:26:09 usa1 postfix/smtpd[7951]: con
On Sat, Feb 20, 2010 at 03:43:25PM +0530, ram wrote:
> One of our clients sends contract notes to their customers and they
> require to store all logs of deliveries/bounces by some law.
>
> They have requirements like
>
> * The log should contain the full date including year
> * The log line s
On 2010-02-19 David Koski wrote:
> On Monday 15 February 2010, Ansgar Wiechers wrote:
>> On 2010-02-14 David Koski wrote:
>>> How about something more simple: test for From: is the same as To:
>>> and is from MAILER-DAEMON:
>>>
>>> grep "^From:.*" "$test" \
>>> && grep "Return-Path:.*" "$test" \
>>
Geert Lorang a écrit :
> On 19/02/2010 15:49, Barney Desmond wrote:
>> On 20 February 2010 01:40, Geert Lorang wrote:
>>
>>> glorang:~# cat /etc/postfix/generic
>>> @mydomain.be accep...@relayhost.other.domain
>>>
>>> Now try to lookup someth...@mydomain.be:
>>>
>>> glorang:~# postmap -q somet
mouss a écrit :
> /dev/rob0 a écrit :
>> On Fri, Feb 19, 2010 at 06:20:27PM -0700, LuKreme wrote:
>>> On 19-Feb-2010, at 12:51, brian moore wrote:
so they [Barracuda] have a name and reputation to protect.
>>> Heh. Sorry, but this make me laugh.
>> Ha, yes, indeed they have a sordid past, but
On 19/02/2010 15:49, Barney Desmond wrote:
On 20 February 2010 01:40, Geert Lorang wrote:
glorang:~# cat /etc/postfix/generic
@mydomain.be accep...@relayhost.other.domain
Now try to lookup someth...@mydomain.be:
glorang:~# postmap -q someth...@mydomain.be /etc/postfix/generic
glorang:~#
> > > >> WIthout changes to the existing configuration of 2.6.5 I get this error
> > > >> using procmail as my mailbox_command:
> > > >> Feb 19 18:34:29 adrianvb postfix/local[14290]: BD85F7006D:
> > > >> to=, orig_to=, relay=local,
> > > >> delay=0.03, delays=0.02/0/0/0.01, dsn=5.3.0, status=bou
zhong ming wu:
> Dear List
>
> Last time I have configured postfix was many years ago with version
> 2.3. Now I wish to upgrade to 2.7 and also change
> configuration by adding dovecot sasl authentication. It is working
> as expected. Public can deliver mail to my domain
> without authenticati
Adrian P. van Bloois:
> * El Sat, Feb 20, 2010 at 02:17:05PM +0100, escribiste:
> > Adrian P. van Bloois a ?crit :
> > > * El Fri, Feb 19, 2010 at 06:56:38PM +0100, escribiste:
> > >> Hi,
> > >> I just installed postfix 2.7.0.
> > >> WIthout changes to the existing configuration of 2.6.5 I get this
Dear List
Last time I have configured postfix was many years ago with version
2.3. Now I wish to upgrade to 2.7 and also change
configuration by adding dovecot sasl authentication. It is working
as expected. Public can deliver mail to my domain
without authentication. authenticated users can
* El Sat, Feb 20, 2010 at 02:17:05PM +0100, escribiste:
> Adrian P. van Bloois a écrit :
> > * El Fri, Feb 19, 2010 at 06:56:38PM +0100, escribiste:
> >> Hi,
> >> I just installed postfix 2.7.0.
> >> WIthout changes to the existing configuration of 2.6.5 I get this error
> >> using procmail as my m
Patrick Ben Koetter a écrit :
> * Неворотин Вадим :
>> How can I deny SASL authentication not from local (192.168.0.0/16) IP? Now I
>> have restrictions in smtpd_recipient_restrictions and other parameters,
>> which allow send mails to relayhost only from local IPs and only after
>> authentication.
Adrian P. van Bloois a écrit :
> * El Fri, Feb 19, 2010 at 06:56:38PM +0100, escribiste:
>> Hi,
>> I just installed postfix 2.7.0.
>> WIthout changes to the existing configuration of 2.6.5 I get this error
>> using procmail as my mailbox_command:
>> Feb 19 18:34:29 adrianvb postfix/local[14290]: BD
Emre Yazici a écrit :
> /dev/rob0 yazm?s,:
>> On Fri, Feb 19, 2010 at 07:32:27PM +0100, mouss wrote:
>>
>>> Wietse Venema a écrit :
>>>
Emre Yazici:
> I want to is to dynamically set corresponding user so that Postfix
> can invoke maildrop with that user's permissions
* El Fri, Feb 19, 2010 at 06:56:38PM +0100, escribiste:
> Hi,
> I just installed postfix 2.7.0.
> WIthout changes to the existing configuration of 2.6.5 I get this error
> using procmail as my mailbox_command:
> Feb 19 18:34:29 adrianvb postfix/local[14290]: BD85F7006D:
> to=, orig_to=, relay=loca
/dev/rob0 yazm?s,:
On Fri, Feb 19, 2010 at 07:32:27PM +0100, mouss wrote:
Wietse Venema a écrit :
Emre Yazici:
I want to is to dynamically set corresponding user so that
Postfix can invoke maildrop with that user's permissions and
mail delivery be made with the correct user rig
Stan Hoeppner a écrit :
> dar...@chaosreigns.com put forth on 2/19/2010 11:26 PM:
>> I want to collect all spam delivered to my server to an invalid user /
>> domain. luser_relay seems to be doing part of the job, but how do I get it
>> around or through spamassassin which is set up as a pre-queue
/dev/rob0 a écrit :
> On Fri, Feb 19, 2010 at 07:32:27PM +0100, mouss wrote:
>> Wietse Venema a écrit :
>>> Emre Yazici:
I want to is to dynamically set corresponding user so that
Postfix can invoke maildrop with that user's permissions and
mail delivery be made with the correct us
/dev/rob0 a écrit :
> On Fri, Feb 19, 2010 at 06:20:27PM -0700, LuKreme wrote:
>> On 19-Feb-2010, at 12:51, brian moore wrote:
>>> so they [Barracuda] have a name and reputation to protect.
>> Heh. Sorry, but this make me laugh.
>
> Ha, yes, indeed they have a sordid past, but I think they're doin
One of our clients sends contract notes to their customers and they
require to store all logs of deliveries/bounces by some law.
They have requirements like
* The log should contain the full date including year
* The log line should indicate full info -->
sender,rcpt,datetime,size,status
I ha
On Fri, 2010-02-19 at 23:39 -0800, David Koski wrote:
> On Monday 15 February 2010, Ansgar Wiechers wrote:
> > On 2010-02-14 David Koski wrote:
> > > On Tuesday 19 January 2010, Ansgar Wiechers wrote:
> > >> On 2010-01-18 David Koski wrote:
> > >>> My mail server has been getting a fair amount of s
27 matches
Mail list logo
