On Sat, Aug 27, 2022 at 02:32:30PM +0200, Günther J. Niederwimmer wrote:
> Also the SASL problem is getting worse, the whole thing worked before I
> upgraded to 3.7.0 and is getting worse 3.7.1 =>. I hope I give all relevant
> configs logs?
I expect you upgraded more than just Postfix, and like
Hello List and Profis,
I need help, my postfix that I recently updated
brought seems no longer happy with my config? I have
sometimes the program "pflogsum" installed, used to only sporadically
searched the logs because it's my home server!
Only now I see a plethora of errors that increase from da
On Tuesday, November 20, 2012 11:07:20 PM Jumping Mouse wrote:
> Hello all my postfix smpt server started acting strangely after a year of
> flawless functioning.
>
> I am getting these messages in my mailqueue:
>
> host 127.0.0.1[127.0.0.1] said: 451 4.5.0 From MTA([127.0.0.1]:10025) during
> f
Hello all my postfix smpt server started acting strangely after a year of
flawless functioning.
I am getting these messages in my mailqueue:
host 127.0.0.1[127.0.0.1] said: 451 4.5.0 From MTA([127.0.0.1]:10025) during
fwd-connect (Negative greeting: at (eval 87) line 442, line 6215.):
id=127
this is
working.
Jon
> Date: Sat, 25 Jun 2011 00:24:42 +0200
> From: mo...@ml.netoyen.net
> To: jonl...@hotmail.com
> CC: postfix-users@postfix.org
> Subject: Re: postfix problems
>
> Le 24/06/2011 17:43, Jon Miller a écrit :
> >
> > Hi,
> > Stress is
Le 24/06/2011 17:43, Jon Miller a écrit :
>
> Hi,
> Stress is probably getting the best of me at the moment since I've been
> trying to get thi sdamn thing back on line since last week.
so stop it, get some vacation, meet people, ... etc until you beat stress!
> I run two businesses and both
Jon Miller:
> smtpd_client_restrictions = permit_mynetworks, reject
This rejects mail from all clients outside mynetworks.
Wietse
t.
Jon
> Date: Fri, 24 Jun 2011 11:23:35 -0400
> From: victor.ducho...@morganstanley.com
> To: postfix-users@postfix.org
> Subject: Re: postfix problems
>
> On Fri, Jun 24, 2011 at 11:14:31PM +0800, Jon Miller wrote:
>
> > When I see mail trying to come in I get an erro
t you guys bear with me...
A do appreciate the help... heaps.
Jon
> Date: Fri, 24 Jun 2011 11:22:02 -0400
> From: grkni...@scent-team.com
> To: postfix-users@postfix.org
> Subject: Re: postfix problems
>
> On 6/24/2011 11:14 AM, Jon Miller wrote:
> >
> > When I see
On Fri, Jun 24, 2011 at 11:14:31PM +0800, Jon Miller wrote:
> When I see mail trying to come in I get an error such as:
>
> Jun 24 23:01:08 mmtlnx postfix/smtpd[27237]: NOQUEUE: reject: RCPT from
> mail.domain3.com.au[203.161.81.22]: 554
> : Client host rejected: Access denied;
> from= to= proto=
On 6/24/2011 11:14 AM, Jon Miller wrote:
>
> When I see mail trying to come in I get an error such as:
>
> Jun 24 23:01:08 mmtlnx postfix/smtpd[27237]: NOQUEUE: reject: RCPT
> from mail.domain3.com.au[203.161.81.22]: 554
> : Client host rejected: Access
> denied; from= to=
> proto=ESMTP helo=
>
> J
When I see mail trying to come in I get an error such as:
Jun 24 23:01:08 mmtlnx postfix/smtpd[27237]: NOQUEUE: reject: RCPT from
mail.domain3.com.au[203.161.81.22]: 554
: Client host rejected: Access denied;
from= to= proto=ESMTP
helo=
Jun 24 23:01:09 mmtlnx postfix/smtpd[27237]: disconnect f
Sorry about the message, for some reason it did like like plain textI'm
installing the same version I had before the crash, unfortunately the config
backups does not seem to be helping. I will be upgrading this server later in
the year and unfortunately I cannot install the lastest version of
* proph...@vizion.occoxmail.com :
> Hi
>
> I am comparatively new to postfix and seem unable to get my
> configuration correct to ensure there are no open relays.
> For obvious reasons I am not posting from the network
> concerned! I set out below
> 1. Details of test with abuse.net
> 2. maillo
>
> From: Brian Evans - Postfix List
> Date: 2009/07/14 Tue PM 04:14:41 EDT
> To: postfix-users@postfix.org
> Subject: Re: Setting up postfix problems
>
> proph...@vizion.occoxmail.com wrote:
> > Hi
> >
> > I am comparatively new to postfix and seem unabl
proph...@vizion.occoxmail.com wrote:
> Hi
>
> I am comparatively new to postfix and seem unable to get my
> configuration correct to ensure there are no open relays.
> For obvious reasons I am not posting from the network
> concerned! I set out below
> 1. Details of test with abuse.net
> 2. mail
On Tue, Jul 14, 2009 at 2:28 PM, wrote:
> Hi
>
> I am comparatively new to postfix and seem unable to get my
> configuration correct to ensure there are no open relays.
> For obvious reasons I am not posting from the network
> concerned! I set out below
> 1. Details of test with abuse.net
> 2. mai
>
> From: mouss
> Date: 2009/07/14 Tue PM 03:40:14 EDT
> To: postfix-users@postfix.org
> Subject: Re: Setting up postfix problems
>
> proph...@vizion.occoxmail.com a écrit :
> > dns1# postconf -n
> &g
proph...@vizion.occoxmail.com a écrit :
> dns1# postconf -n
> alias_maps = hash:/etc/aliases
> command_directory = /usr/local/sbin
> config_directory = /usr/local/etc/postfix
> daemon_direct
dns1# postconf -n
alias_maps = hash:/etc/aliases
command_directory = /usr/local/sbin
config_directory = /usr/local/etc/postfix
daemon_directory = /usr/local/libexec/postfix
data
> I am comparatively new to postfix and seem unable to get my
> configuration correct to ensure there are no open relays.
> For obvious reasons I am not posting from the network
> concerned! I set out below
> 1. Details of test with abuse.net
> 2. maillog entries for the test
> 3. network requireme
Hi
I am comparatively new to postfix and seem unable to get my
configuration correct to ensure there are no open relays.
For obvious reasons I am not posting from the network
concerned! I set out below
1. Details of test with abuse.net
2. maillog entries for the test
3. network requirements for
--On Tuesday, February 24, 2009 9:26 AM -0500 Wietse Venema
wrote:
Further investigation tracks this down to something failing with DNS
resolution after a while. Don't know why, but it does seem to be a
problem with OS X and catastrophic failure.
Since I don't maintain copies of every Post
Quanah Gibson-Mount:
> --On Thursday, February 19, 2009 11:48 AM -0800 Quanah Gibson-Mount
> wrote:
>
> >>> Anyone have an insight into why? Postfix version is 2.4.7.
> >>
> >> This is really a platform-specific question, that can be answered
> >> only by people who have access to the affected
--On Thursday, February 19, 2009 11:48 AM -0800 Quanah Gibson-Mount
wrote:
Anyone have an insight into why? Postfix version is 2.4.7.
This is really a platform-specific question, that can be answered
only by people who have access to the affected OS.
Ok, but it's also something directly r
--On Thursday, February 19, 2009 1:54 PM -0500 Wietse Venema
wrote:
Quanah Gibson-Mount:
I've been running into a really odd (bizarre) problem with Postfix that
only seems to happen on Mac OSX 10.5 (leopard). I'm really at a loss to
explain why things break the way they do, but it definitely
Quanah Gibson-Mount:
> I've been running into a really odd (bizarre) problem with Postfix that
> only seems to happen on Mac OSX 10.5 (leopard). I'm really at a loss to
> explain why things break the way they do, but it definitely happens. I
> thought maybe some folks on the list might have so
I've been running into a really odd (bizarre) problem with Postfix that
only seems to happen on Mac OSX 10.5 (leopard). I'm really at a loss to
explain why things break the way they do, but it definitely happens. I
thought maybe some folks on the list might have some insight.
Here is the sce
[EMAIL PROTECTED]:
>
> > - Understand that Postfix refuses [EMAIL PROTECTED]:port as an email
> > destination.
> >
> > Wietse
> >
>
> Ok Wietse, thanks for the info... Do you know if there's any GPL mail
> server accepting [EMAIL PROTECTED]:port as an email destination?
That would be a sec
> - Understand that Postfix refuses [EMAIL PROTECTED]:port as an email
> destination.
>
> Wietse
>
Ok Wietse, thanks for the info... Do you know if there's any GPL mail
server accepting [EMAIL PROTECTED]:port as an email destination?
Thanks
Antonio
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
> >> const char *dsn_orcpt, int dsn_notify,
> >> const char *orig_rcpt, const char *rcpt)
> >
> > You can't change the rcpt argume
> [EMAIL PROTECTED]:
>> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
>> const char *dsn_orcpt, int dsn_notify,
>> const char *orig_rcpt, const char *rcpt)
>
> You can't change the rcpt argument.
>
>> {
>> int n
>> [EMAIL PROTECTED]:
>>> > [EMAIL PROTECTED]:
>>> >> , postfix reload; and postfix stills working as always.
>>> >
>>> > Show actual evidence of behavior that does not change, and show
>>> > actual evidence based on which it should have changed.
>>> >
>>> > Wietse
>>> >
>>>
>>> It's easy. On my
[EMAIL PROTECTED]:
> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
> const char *dsn_orcpt, int dsn_notify,
> const char *orig_rcpt, const char *rcpt)
You can't change the rcpt argument.
> {
> int new_avail;
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> > [EMAIL PROTECTED]:
> >> >> , postfix reload; and postfix stills working as always.
> >> >
> >> > Show actual evidence of behavior that does not change, and show
> >> > actual evidence based on which it should have changed.
> >> >
> >> > Wietse
> >>
> [EMAIL PROTECTED]:
>> > [EMAIL PROTECTED]:
>> >> , postfix reload; and postfix stills working as always.
>> >
>> > Show actual evidence of behavior that does not change, and show
>> > actual evidence based on which it should have changed.
>> >
>> >Wietse
>> >
>>
>> It's easy. On my modified l
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> , postfix reload; and postfix stills working as always.
> >
> > Show actual evidence of behavior that does not change, and show
> > actual evidence based on which it should have changed.
> >
> > Wietse
> >
>
> It's easy. On my modified library, I
> [EMAIL PROTECTED]:
>> , postfix reload; and postfix stills working as always.
>
> Show actual evidence of behavior that does not change, and show
> actual evidence based on which it should have changed.
>
> Wietse
>
It's easy. On my modified library, I modify recipient_list_add(...)
functi
[EMAIL PROTECTED]:
> , postfix reload; and postfix stills working as always.
Show actual evidence of behavior that does not change, and show
actual evidence based on which it should have changed.
Wietse
> [EMAIL PROTECTED]:
>> Thank you. I try that some days ago but it didn't work.
>
> It works only if you understand its limitations.
>
> The import_environment feature executes AFTER the run-time linker
> completes execution. Therefore, import_environment cannot affect
> the run-time linker perform
[EMAIL PROTECTED]:
> Thank you. I try that some days ago but it didn't work.
It works only if you understand its limitations.
The import_environment feature executes AFTER the run-time linker
completes execution. Therefore, import_environment cannot affect
the run-time linker performance for the
Thank you. I try that some days ago but it didn't work.
I'll retry it!
Antonio G. Artime
http://www.postfix.org/postconf.5.html#import_environment
http://www.postfix.org/postconf.5.html#export_environment
Wietse
Hello everybody:
I'm trying to modify some functions on postfix source and then preload
them by using LD_PRELOAD. To get it work, I've modified
/etc/postfix/postfix-script as follows:
[...]
overlay)
export LD_LIBRARY_PATH=./:/usr/local/lib/:$LD_LIBRARY_PATH
export LD_PRELOAD=/home/antoni
44 matches
Mail list logo
