Octavio:
[ Charset UTF-8 unsupported, converting... ]
> Hi
>
> my server have some public IPs and I want to use one that is not
> the primary (eth0:0) but when I send email always use the one in
> eth0 despite the postfix is have as interface just the one in
> eth0:0 and lo
See:
http://www.postf
Hi
my server have some public IPs and I want to use one that is not the primary
(eth0:0) but when I send email always use the one in eth0 despite the postfix
is have as interface just the one in eth0:0 and lo
Thanks
Octavio
___
On 11/11/2008 4:49 PM, Charles Marcus wrote:
>> Common administrative practices include submission on 587 for
>> trusted clients only and should not be permitted on the internet.
>> This port should be firewalled outside of your network.
> Excuse me?!?!? Thats ridiculous... in fact, just the OPPO
On 11/11/2008 4:35 PM, Brian Evans - Postfix List wrote:
> Linux Addict wrote:
>> While I read through this, I understand that to use domain keys, the
>> client has to send mails through submission port 587. Does that sound
>> right? Just to use domainkeys, all clients to has to send mails to
>> po
Linux Addict wrote:
>
> While I read through this, I understand that to use domain keys, the
> client has to send mails through submission port 587. Does that sound
> right? Just to use domainkeys, all clients to has to send mails to
> port 587 instead of port 25? Please clarify. Thank you
The subm
On Mon, Nov 10, 2008 at 5:19 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> Linux Addict wrote:
>
>> Hi, Please excuse me if it is not relevant on this forum.
>>
>> I am planning to use domain keys and dkim for our domain just to send
>> mails outside.
>>
>> Is DKIMproxy good enough to cover both old
Watashi:
>
> >> >What is the error message?
> >>
> >> The error is those messages on console about no memory from kernel ( a lot
> >> of
> >> process dumps on screen). All applications stops to work and I have to
> >> ctrl +
> >> atl + prt src + s + b to reboot the servers.
>
> > I will not ask
On November 11, 2008 02:30:11 pm Brian Evans - Postfix List wrote:
> James Grant wrote:
> > So, in postfix's main.cf I have:
> >
> > #VIRTUAL/MYSQL
> > virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-domains.cf
> > virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
>
James Grant wrote:
> So, in postfix's main.cf I have:
>
> #VIRTUAL/MYSQL
> virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-domains.cf
> virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
> virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
>
> Both a
>> >What is the error message?
>>
>> The error is those messages on console about no memory from kernel ( a lot of
>> process dumps on screen). All applications stops to work and I have to ctrl +
>> atl + prt src + s + b to reboot the servers.
> I will not ask the same question again.
> Wietse
Hi, I've got postfix setup with MySQL / Virtual, and am in the process of
migrating from an old qmail (*shudder*) system. Some of my users have
entries in their .qmail files that do things like:
.qmail
Maildir/
&[EMAIL PROTECTED]
aka, save it on the server in their Maildir/ an
Watashi:
> Hi Wietse and Reinaldo de Carvalho,
>
>
> >> Each 30 days I have to reboot both servers because the memory is all used.
>
> >What is the error message?
>
> The error is those messages on console about no memory from kernel ( a lot of
> process dumps on screen). All applications stops
Hi Wietse and Reinaldo de Carvalho,
>> Each 30 days I have to reboot both servers because the memory is all used.
>What is the error message?
The error is those messages on console about no memory from kernel ( a lot of
process dumps on screen). All applications stops to work and I have to ctrl
On Tuesday 11 November 2008 12:01, Noel Jones wrote:
> Kevin P. Knox wrote:
> > On Tuesday 11 November 2008 11:29, Noel Jones wrote:
> >> Kevin P. Knox wrote:
> >>> If you all would be so kind, I need a "pointer" in the general
> >>> direction. I think I'm on the right track, but here's the situati
On Tue, Nov 11, 2008 at 05:36:51PM +0100, Lars Ebeling wrote:
> >The code dies before entering main(). The _start() function is the
> >entry point of the executable, it arranges for loading of dynamic
> >libraries and initialization of the C runtime. THe _init() function
> >initializes the state o
On Tue, Nov 11, 2008 at 05:44:56PM +0100, Lars Ebeling wrote:
> > # gdb /usr/libexec/postfix/smtp -S
> > # gdb /usr/libexec/postfix/smtp -u -S
> # /opt/csw/bin/gdb /usr/libexec/postfix/smtp -S
> /opt/csw/bin/gdb: unrecognized option `-S'
# gdb /usr/libexec/postfix/smtp
gdb) r
mail01:/var/log# grep 6F38E5F4595 mail.info
Nov 11 07:02:29 mail01 postfix/qmgr[26195]: 6F38E5F4595:
from=<[EMAIL PROTECTED]>, size=2091, nrcpt=9 (queue active)
Nov 11 07:02:32 mail01 postfix/smtp[19552]: 6F38E5F4595: host
mx2.comcast.net[76.96.30.116] refused to talk to me: 554
IMTA18.emeryville.c
Kevin P. Knox wrote:
On Tuesday 11 November 2008 11:29, Noel Jones wrote:
Kevin P. Knox wrote:
If you all would be so kind, I need a "pointer" in the general direction.
I think I'm on the right track, but here's the situation.
I have a Postfix server that performs SMTP relay services ONLY. I
Kevin P. Knox:
> My Postfix server is running 2.2.10, so I don't "think" I can use CIDRs, but
> can possibly list the internal servers as 32 bit addresses?
CDIR table lookups were introduced with Postfix 2.1.
Wietse
On Tuesday 11 November 2008 12:01, Noel Jones wrote:
> Kevin P. Knox wrote:
> > On Tuesday 11 November 2008 11:29, Noel Jones wrote:
> >> Kevin P. Knox wrote:
> >>> If you all would be so kind, I need a "pointer" in the general
> >>> direction. I think I'm on the right track, but here's the situati
Lars Ebeling:
> warning: process /usr/libexec/postfix/smtp pid 17858 killed by signal 11
Wietse:
> > To debug by hand, try:
> ># gdb /usr/libexec/postfix/smtp -S
> ># gdb /usr/libexec/postfix/smtp -u -S
Lars Ebeling:
> # /opt/csw/bin/gdb /usr/libexec/postfix/smtp -S
> /opt/csw/bin/gdb
Original Message
From: "Wietse Venema" <[EMAIL PROTECTED]>
To: "Postfix users"
Sent: Tuesday, November 11, 2008 3:58 PM
Subject: Re: Problems with running postfix
Lars Ebeling:
warning: process /usr/libexec/postfix/smtp pid 17858 killed by
signal 11
You seem to have DLL hell.
On Tue, Nov 11, 2008 at 11:47:34AM -0500, Carlos Williams wrote:
> On Mon, Nov 10, 2008 at 9:20 PM, Victor Duchovni
> <[EMAIL PROTECTED]> wrote:
> >> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> >> > If your existing verisign certificate is a "server" type certificate w
On Tuesday 11 November 2008 11:29, Noel Jones wrote:
> Kevin P. Knox wrote:
> > If you all would be so kind, I need a "pointer" in the general direction.
> > I think I'm on the right track, but here's the situation.
> >
> > I have a Postfix server that performs SMTP relay services ONLY. It
> > re
On Mon, Nov 10, 2008 at 9:20 PM, Victor Duchovni
<[EMAIL PROTECTED]> wrote:
>> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
>> > If your existing verisign certificate is a "server" type certificate with
>> > the right FQDN, you should be able to use it with postfix.
I bel
What is the output of:
grep 6F38E5F4595 /the/maillog/file
grep D8AFD5F4526 /the/maillog/file
One is before Amavis, one is after Amavis.
Wietse
Original Message
From: "Victor Duchovni" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, November 11, 2008 3:59 PM
Subject: Re: Problems with running postfix
The code dies before entering main(). The _start() function is the
entry point of the executable, it arranges for loading of dynami
Kevin P. Knox wrote:
If you all would be so kind, I need a "pointer" in the general direction. I
think I'm on the right track, but here's the situation.
I have a Postfix server that performs SMTP relay services ONLY. It relays for
about six domain names. Final delivery of these six domains
On 11/11/2008 11:07 AM, Jaap Westerbeek wrote:
> Digging into the logfiles, I could not find the spammer (64.129.70.219) had
> used SASL
So if he didn't get in through sasl_auth, obviously he must have gotten
in through a hole in your
check_recipient_access hash:/etc/postfix/access_recipient,
Digging into the logfiles, I could not find the spammer (64.129.70.219) had
used SASL
All SASL authentications seemed legitimate (coming from an ISP in the same
country), or from within my_networks.
It would have given me something like this right ?
client=unknown[64.129.70.219], sasl_method
If you all would be so kind, I need a "pointer" in the general direction. I
think I'm on the right track, but here's the situation.
I have a Postfix server that performs SMTP relay services ONLY. It relays for
about six domain names. Final delivery of these six domains is handled by
three SM
Jaap Westerbeek:
> Supposing it IS a hacked SASL account, is there any way to stop that
> rewriting process ? Or to know which account was being abused ?
> Forcing all users to do a password change is not really an option with so
> many accounts.
Postfix logs the SASL user name to the maillog file
On Tue, Nov 11, 2008 at 10:07 AM, Watashi <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Each 30 days I have to reboot both servers because the memory is all used.
> There's no cache memory, buffers or something else. I already tried echo 3 >
> .../drop_caches
>
Linux use memory to cache all read f
That's very possible, and was my fisrt though too.
There are a few thousand accounts in the DB, and I've only introduced strong
passwords when I started working here ( like 1 year ago)
For completeness, let me post some entries from my access_recipient table ,
which is made up of some servers in
Lars Ebeling:
> warning: process /usr/libexec/postfix/smtp pid 17858 killed by signal 11
You seem to have DLL hell.
To debug by hand, try:
# gdb /usr/libexec/postfix/smtp -S
# gdb /usr/libexec/postfix/smtp -u -S
This will hopefully expose the problem before things get messed up.
Norma
mouss wrote:
Roderick A. Anderson wrote:
[snip]
If your problem is that From: equals To:, then Postfix can help
only with an external content filter.
If your problem is that MAIL FROM equals RCPT TO, then Postfix can
help only with an external policy daemon or external content filter.
In the
On Tue, Nov 11, 2008 at 03:40:33PM +0100, Lars Ebeling wrote:
> Nov 11 14:22:23 leopg2.no-ip.org postfix/master[17846]: warning:
> process /usr/libexec/postfix/smtp pid 17858 killed by signal 11
> Nov 11 14:22:23 leopg2.no-ip.org postfix/master[17846]: warning:
> /usr/libexec/postfix/s
I am installing Postfix on Solaris. My problem is that I have to relay via
my ISP's mailserver. And login with TLS. I have a workin mailserver on
HP-UX, but want a backup. I have copied the configuration files from HP-UX
to Solaris.
When I tray to send a mail I get this in logfile:
Nov 11 14:
On Tue, Nov 11, 2008 at 11:31:38AM -0300, Jaap Westerbeek wrote:
> I changed the order.
>
Note, my money is on "permit_sasl_authenticated" and weak credentials
(like user "test" password "test", ...) or stolen credentials (users
victims of phishing). In which case you really should address that.
I changed the order.
Thanks Wietse, I'll keep you posted :)
-Original Message-
From: Wietse Venema [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 11:09 AM
To: Jaap Westerbeek
Cc: postfix-users@postfix.org
Subject: Re: Spammers abusing my postfix box
Jaap Westerbeek:
> smtpd_
Terry Carmen schrieb:
> Robert Schetterer wrote:
>> thx mouss for your qualified info, but this appeared just this morning,
>> and i hadnt include
>> their error because they have plenty of servers which give different
>> error codes ( which make no sense at all )
>> at all they give no usefull inf
Robert Schetterer wrote:
thx mouss for your qualified info, but this appeared just this morning,
and i hadnt include
their error because they have plenty of servers which give different
error codes ( which make no sense at all )
at all they give no usefull information, i checked the log on one
of
Jaap Westerbeek:
> smtpd_recipient_restrictions =
> permit_sasl_authenticated,
> check_recipient_access hash:/etc/postfix/access_recipient,
There is your open relay. Put it below
> reject_unauth_destination,
Wietse
Robert Schetterer schrieb:
> Marco Tchi Hong schrieb:
>> Hello,
>> I've got the same problem too since this morning...
>> I even tried to send mail to Yahoo with a test server with an IP address I
>> never used for a mail server, and I also get the 451 error message...
>>
>> Marco
>>
>> -Messag
Jaap Westerbeek wrote:
Ok the (or some) spammer came back.
For some reason everything seems to originate from localhost, which isn't
telling me much.
Where to look , what to do ?
its NOT orginitating from localhost, thats just the last step from you
amavis...
This is the amavis tags...
I had noticed his sending IP.
Now, how do I prevent him from abusing my server ? How is it possible he can
send from my server when he's not in my_networks ?
Can I prevent him from spoofing the sender mailaddress ?
I'm posting a bit from my main.cf , maybe I've got it wrong :
Some pointers would
Watashi:
> Hello all,
>
> I have a trouble with my two mail servers where the users's maildir are. I use
> Courier Authdaemon with PAM_LDAP authenticating against a M$ Active Directory
> to serve imap, pop3 and maildrop. More than 8.000 accounts. The MTA is Postfix
> looking up for users in M$ AD
Marco Tchi Hong schrieb:
> Hello,
> I've got the same problem too since this morning...
> I even tried to send mail to Yahoo with a test server with an IP address I
> never used for a mail server, and I also get the 451 error message...
>
> Marco
>
> -Message d'origine-
> De : [EMAIL PROT
tôba schrieb:
> On Tue, 11 Nov 2008 13:20:36 +0100
> Robert Schetterer <[EMAIL PROTECTED]> wrote:
>
>> mouss schrieb:
>>> Robert Schetterer wrote:
Gerard schrieb:
> On Tue, 11 Nov 2008 12:09:16 +0100
> Robert Schetterer <[EMAIL PROTECTED]> wrote:
>
>> double checked this on di
Hello,
I've got the same problem too since this morning...
I even tried to send mail to Yahoo with a test server with an IP address I
never used for a mail server, and I also get the 451 error message...
Marco
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part
Hello all,
I have a trouble with my two mail servers where the users's maildir are. I use
Courier Authdaemon with PAM_LDAP authenticating against a M$ Active Directory
to serve imap, pop3 and maildrop. More than 8.000 accounts. The MTA is Postfix
looking up for users in M$ AD directly.
Each 30 da
Jaap Westerbeek:
> Received: from User (unknown [64.129.70.219])
> by mail01.cq-link.sr (Postfix) with ESMTP id D8AFD5F4526;
> Fri, 7 Nov 2008 18:55:47 -0300 (SRT)
There's your spammer.
Wietse
On Tue, 11 Nov 2008 13:20:36 +0100
Robert Schetterer <[EMAIL PROTECTED]> wrote:
> mouss schrieb:
> > Robert Schetterer wrote:
> >> Gerard schrieb:
> >>> On Tue, 11 Nov 2008 12:09:16 +0100
> >>> Robert Schetterer <[EMAIL PROTECTED]> wrote:
> >>>
> double checked this on different mailservers
>
Zitat von Robert Schetterer <[EMAIL PROTECTED]>:
Hi @ll,
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
anyone else notices same problems?
Yes, always. Yahoo never had reliable mailservice at all so i never be
worried if ya
On Tue, 11 Nov 2008 09:39:32 -0300
"Jaap Westerbeek" <[EMAIL PROTECTED]> wrote:
> Ok the (or some) spammer came back.
>
> For some reason everything seems to originate from localhost, which isn't
> telling me much.
> Where to look , what to do ?
>
[snip]
You need the log entries for the email BE
Ok the (or some) spammer came back.
For some reason everything seems to originate from localhost, which isn't
telling me much.
Where to look , what to do ?
Postcat gives me this :
*** ENVELOPE RECORDS deferred/6/6F38E5F4595 ***
message_size:20911231 9
0
messa
Mark Goodge schrieb:
>
>
> Robert Schetterer wrote:
>> Gerard schrieb:
>>> On Tue, 11 Nov 2008 12:09:16 +0100
>>> Robert Schetterer <[EMAIL PROTECTED]> wrote:
>>>
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
any
mouss schrieb:
> Robert Schetterer wrote:
>> Gerard schrieb:
>>> On Tue, 11 Nov 2008 12:09:16 +0100
>>> Robert Schetterer <[EMAIL PROTECTED]> wrote:
>>>
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
anyone else not
Robert Schetterer wrote:
Gerard schrieb:
On Tue, 11 Nov 2008 12:09:16 +0100
Robert Schetterer <[EMAIL PROTECTED]> wrote:
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
anyone else notices same problems?
Lacking a functioni
Robert Schetterer wrote:
Gerard schrieb:
On Tue, 11 Nov 2008 12:09:16 +0100
Robert Schetterer <[EMAIL PROTECTED]> wrote:
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
anyone else notices same problems?
Lacking a functioning
Gerard schrieb:
> On Tue, 11 Nov 2008 12:09:16 +0100
> Robert Schetterer <[EMAIL PROTECTED]> wrote:
>
>> double checked this on different mailservers
>> on different nets , at current i cant deliver out mail to yahoo.de/com
>> anyone else notices same problems?
>
> Lacking a functioning crystal b
Roderick A. Anderson wrote:
[snip]
If your problem is that From: equals To:, then Postfix can help
only with an external content filter.
If your problem is that MAIL FROM equals RCPT TO, then Postfix can
help only with an external policy daemon or external content filter.
In the case of the a
On Tue, 11 Nov 2008 12:09:16 +0100
Robert Schetterer <[EMAIL PROTECTED]> wrote:
>double checked this on different mailservers
>on different nets , at current i cant deliver out mail to yahoo.de/com
>anyone else notices same problems?
Lacking a functioning crystal ball, debugging your problem sans
Hi @ll,
double checked this on different mailservers
on different nets , at current i cant deliver out mail to yahoo.de/com
anyone else notices same problems?
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Hi Brian.
On Mon, Nov 10, 2008 at 12:14, Brian Evans - Postfix List
<[EMAIL PROTECTED]> wrote:
> Notice you put permit_mynetworks first. This wins over the
> check_recipient_access if any client is within mynetworks..
> Also, recommend putting reject_unauth_destination right below
> permit_sasl_a
65 matches
Mail list logo