On 14/8/08 11:25 PM, "Wietse Venema" <[EMAIL PROTECTED]> wrote:
> Robert Cohen:
>> So if a filter botches handling one message, postfix gives on sending it
>> anything for up to 15 minutes?
>> That doesn't seem like a particularly graceful way of handling filter
>> failure.
>
> When a destinatio
2008/8/14 Voytek Eymont <[EMAIL PROTECTED]>:
> I then built and installed a Postfix rpm using Simon Mudd's srpm as:
> postfix-2.5.2-1.pcre.mysql.sasl2.rhel5.i386.rpm
I know zero about this particular SRPM, but it's doing things
differently to what's expected (Centos' wouldn't ship with an SElinux
sharad kanekar:
> Dear All,
> I configured Postfix 2.3.3-2 on CentOS 5.2. But I am unable
> to send receive mails. I want to use ISP as relay host
To send mail using the ISP as relay host, use the main.cf:relayhost
parameter. http://www.postfix.org/postconf.5.html#relayhost
To rece
Dear All,
I configured Postfix 2.3.3-2 on CentOS 5.2. But I am unable
to send receive mails. I want to use ISP as relay host
[EMAIL PROTECTED] ~]# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/post
Ronald F. Guilmette:
>
> Pretend I'm an idiot. (For most people who know me this won't be hard.)
>
> Could somebody please explain to me... in a way that takes into account
> my idiocy... what this "strict_mime_encoding_domain" option actually does,
> i.e. if you turn it on?
It stops some malfo
John Heim wrote:
- Original Message - From: "Noel Jones" <[EMAIL PROTECTED]>
In setting up the pre-queue spam filter, I followed the instructions
here:
http://www.postfix.org/SMTPD_PROXY_README.html
What are you using as your smtpd_proxy_filter? Seems it could do
better...
Spampd
Ralf Hildebrandt wrote:
* David K. Means <[EMAIL PROTECTED]>:
I have been unable to track down any useful suggestions on how to solve
this problem:
I have Postfix 2.4.5 installed on a Fedora 7 system; it sends and
receives most email properly.
I can originate mail from this server (using
Pretend I'm an idiot. (For most people who know me this won't be hard.)
Could somebody please explain to me... in a way that takes into account
my idiocy... what this "strict_mime_encoding_domain" option actually does,
i.e. if you turn it on?
What exactly constitutes "invalid Content-Transfer-E
- Original Message -
From: "Noel Jones" <[EMAIL PROTECTED]>
In setting up the pre-queue spam filter, I followed the instructions
here:
http://www.postfix.org/SMTPD_PROXY_README.html
What are you using as your smtpd_proxy_filter? Seems it could do better...
Spampd and spamassassin.
John Heim wrote:
- Original Message - From: "Jorey Bump" <[EMAIL PROTECTED]>
Don't rely solely on SpamAssassin. There are other techniques that are
less expensive and can eliminate obvious spam with virtually no false
positives (and others that may have an acceptable level of false
David K. Means:
> I can originate mail from this server (using "mail [EMAIL PROTECTED]")
> which is accepted and delivered properly; this works
> both as a normal user, and as root.
>
> When I attempt a similar operation from within a PHP script (running
> under Apache httpd), the mail is no
ok, modified it to
server_host = 127.0.0.1
server_port = 389
search_base = ou=people,dc=smb,dc=internal
#query_filter = (&(objectClass=gosaMailAccount)(mail=%s))
query_filter = mail=%s
result_attribute = uid,gosaMailForwardingAddress
version = 3
bind = no
postmap -q now returns mytest, still no c
John Heim wrote, at 08/14/2008 02:09 PM:
postconf on the mta:
smtpd_recipient_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_dom
ain, permit_mynetworks, reject_unauth_destination, check_sender_access
hash:/etc
/postfix/access, permit
Try this:
smtpd_recipient_restrictions =
* David K. Means <[EMAIL PROTECTED]>:
> I have been unable to track down any useful suggestions on how to solve
> this problem:
> I have Postfix 2.4.5 installed on a Fedora 7 system; it sends and
> receives most email properly.
> I can originate mail from this server (using "mail [EMAIL PROTE
I have been unable to track down any useful suggestions on how to solve
this problem:
I have Postfix 2.4.5 installed on a Fedora 7 system; it sends and
receives most email properly.
I can originate mail from this server (using "mail [EMAIL PROTECTED]")
which is accepted and delivered properly;
- Original Message -
From: "Jorey Bump" <[EMAIL PROTECTED]>
Don't rely solely on SpamAssassin. There are other techniques that are
less expensive and can eliminate obvious spam with virtually no false
positives (and others that may have an acceptable level of false
positives, though
- Original Message -
From: "Charles Marcus" <[EMAIL PROTECTED]>
To: "John Heim" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, August 14, 2008 12:17 PM
Subject: Re: mail aliases & spam
On 8/14/2008, John Heim ([EMAIL PROTECTED]) wrote:
Exactly! Except that the reason our anti-spam measure
John Heim wrote, at 08/14/2008 12:43 PM:
Exactly! Except that the reason our anti-spam measures are ineffective
is that the addresses are aliased. We have 2 MTAs running postfix with
pre-queue spam filters and then a delivery machine running postfix,
spamassassin, & dovecot. The pre-queue spa
On 8/14/2008, John Heim ([EMAIL PROTECTED]) wrote:
> Exactly! Except that the reason our anti-spam measures are
> ineffective is that the addresses are aliased.
?? What difference does an alias make? Either a recipient is valid or not...
> We have 2 MTAs running postfix with pre-queue spam filter
- Original Message -
From: "Charles Marcus" <[EMAIL PROTECTED]>
To: "John Heim" <[EMAIL PROTECTED]>
Cc: "Postfix users"
Sent: Thursday, August 14, 2008 11:06 AM
Subject: Re: mail aliases & spam
On 8/14/2008 11:54 AM, John Heim wrote:
Get it? Somebody tries to spam [EMAIL PROTECTED]
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 16:07 + on 08/14/2008, Duane Hill wrote:
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 15:42 + on 08/14/2008, Duane Hill wrote:
2.5.1 is there.
Here's what I've got:
ares-root# ls -ld /usr/ports/mail/postfix*
drwxr-xr-x 3 root wheel
John Heim wrote:
I'm running a system with about 300 users. I run pflogsumm every night
to generate mail log stats. The bounce detail lists 300 - 400 servers
rejecting mail because the user is unknown. The vast majority of servers
has 1 or 2 such rejections. This puzzles me. My users can't
** At 16:07 + on 08/14/2008, Duane Hill wrote:
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 15:42 + on 08/14/2008, Duane Hill wrote:
2.5.1 is there.
Here's what I've got:
ares-root# ls -ld /usr/ports/mail/postfix*
drwxr-xr-x 3 root wheel 512 Aug 14 10:56 /usr/ports/mail/postfix
Vince Sabio:
> ** At 11:00 -0400 on 08/14/2008, Wietse Venema wrote:
> >Vince Sabio:
> >> I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
> >> be running fine *except* for postfix. When I start postfix, I get:
> >>
> >> ares-root# postfix start
> >> postfix/postfix-script: w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wietse Venema wrote:
> Summary: Solaris and Linux file system behavior has changed over
> time, breaking one of the assumptions in Postfix. See below for a
> description of the behavior and how it disagrees with standards.
>
> Postfix is not affected
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 15:42 + on 08/14/2008, Duane Hill wrote:
On Thu, 14 Aug 2008, Vince Sabio wrote:
Okay, I've upgraded to v2.4, which seems to be the most current version in
FreeBSD ports (not v2.5 ... not sure why). Now I just need to figure out
what to do wi
On 8/14/2008 11:54 AM, John Heim wrote:
> Get it? Somebody tries to spam [EMAIL PROTECTED] and user12 has his
> mail forwarded to his gmail account. Gmail detects the spam, rejects the
> message and my mta then generates a bounce back to the original forged
> from address.
>
> I don't see anything
** At 11:51 -0400 on 08/14/2008, Vince Sabio wrote:
** At 15:42 + on 08/14/2008, Duane Hill wrote:
On Thu, 14 Aug 2008, Vince Sabio wrote:
Okay, I've upgraded to v2.4, which seems to be the most current
version in FreeBSD ports (not v2.5 ... not sure why). Now I just
need to figure out wh
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 15:42 + on 08/14/2008, Duane Hill wrote:
2.5.1 is there.
Here's what I've got:
ares-root# ls -ld /usr/ports/mail/postfix*
grep PORTVERSION /usr/ports/mail/postfix*/Makefile
I'm running a system with about 300 users. I run pflogsumm every night to
generate mail log stats. The bounce detail lists 300 - 400 servers rejecting
mail because the user is unknown. The vast majority of servers has 1 or 2
such rejections. This puzzles me. My users can't possibly be sendin
** At 15:42 + on 08/14/2008, Duane Hill wrote:
On Thu, 14 Aug 2008, Vince Sabio wrote:
Okay, I've upgraded to v2.4, which seems to be the most current
version in FreeBSD ports (not v2.5 ... not sure why). Now I just
need to figure out what to do with that damaged message.
When was the la
On Thu, 14 Aug 2008, Vince Sabio wrote:
** At 11:00 -0400 on 08/14/2008, Wietse Venema wrote:
Vince Sabio:
I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
be running fine *except* for postfix. When I start postfix, I get:
ares-root# postfix start
postfix/postfix-script
** At 11:00 -0400 on 08/14/2008, Wietse Venema wrote:
Vince Sabio:
I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
be running fine *except* for postfix. When I start postfix, I get:
ares-root# postfix start
postfix/postfix-script: warning: damaged message: corrupt/AE0AB4
On Thu, 14 Aug 2008, Wietse Venema wrote:
Vince Sabio:
I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
be running fine *except* for postfix. When I start postfix, I get:
ares-root# postfix start
postfix/postfix-script: warning: damaged message: corrupt/AE0AB49AF76
postfix/p
Vince Sabio:
> I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
> be running fine *except* for postfix. When I start postfix, I get:
>
> ares-root# postfix start
> postfix/postfix-script: warning: damaged message: corrupt/AE0AB49AF76
> postfix/postfix-script: starting the Postf
Patrick Ben Koetter wrote, at 08/14/2008 08:22 AM:
The order in which mechanisms are listed in $mech_list or in which they are
announced as SMTP capability is irrelevant. The client chooses the "best"
mechanism by it's own logic.
Note that this has become a blessing from a support point of vie
On Thu, Aug 14, 2008 at 12:25 AM, Ismail OZATAY <[EMAIL PROTECTED]> wrote:
> I am just trying cp command to copy them or can you give me some advice
> about this action, please?
Where are you copying them to? Actual paths, please. How are you
creating the new Maildir? Are the permissions correc
I upgraded my FreeBSD server to v7.0-RELEASE -- everything seems to
be running fine *except* for postfix. When I start postfix, I get:
ares-root# postfix start
postfix/postfix-script: warning: damaged message: corrupt/AE0AB49AF76
postfix/postfix-script: starting the Postfix mail system
postfix
smtp and cleanup shoudn't use chroot in master.cf when usinf ssl+ldap.
Jakjr
On Thu, Aug 14, 2008 at 4:03 AM, Patrick Ben Koetter <[EMAIL PROTECTED]>wrote:
> * Alejandro Facultad <[EMAIL PROTECTED]>:
> >>> apt-get install sasl2-bin libsasl2-modules
> >>>
> >>> /etc/default/saslauthd:
> >>> START
Hallo Robert,
Op maandag 04 augustus 2008 schreef [EMAIL PROTECTED] aan
postfix-users:
RS>> reject_unknown_reverse_client_hostname
RS>> helps a lot here
lpu> Thanks. I've put that in and will wait and see what happens.
It took a few days, becaus it doen'st happen every day. But this
solution
* Michael De Groote <[EMAIL PROTECTED]>:
> hi all
>
> I've setup ldap so local users and their corresponding samba parts are
> stored in it (well, the samba part still needs to be done, but that is on of
> the objectives, and i have that part already working on another machine), as
> well as mail
hi all
I've setup ldap so local users and their corresponding samba parts are
stored in it (well, the samba part still needs to be done, but that is on of
the objectives, and i have that part already working on another machine), as
well as mail information.
mail info is stored in the ldap attribu
Robert Cohen:
> So if a filter botches handling one message, postfix gives on sending it
> anything for up to 15 minutes?
> That doesn't seem like a particularly graceful way of handling filter
> failure.
When a destination suffers from a PERSISTENT FAILURE (i.e. your
content filter is dropping c
Noel Jones,
Thank you very much!!!
__
Marcus
Noel Jones <[EMAIL PROTECTED]>
Enviado Por: [EMAIL PROTECTED]
13/08/2008 18:58
Favor responder a postfix users list
Para: postfix-users@postfix.org
cc:
Assunto:Re: Recipient whitelist
[EMAIL PROTECTED] wro
* punit jain <[EMAIL PROTECTED]>:
> Hi All,
>
> I have a query on SASL mechanism.
>
> I have enabled 3 mechanisms and that can be seen as : -
>
> ehlo localhost
> 250-proxy.test.com
> 250-PIPELINING
> 250-SIZE 1024
> 250-VRFY
> 250-ETRN
> 250-STARTTLS
> 250-AUTH LOGIN CRAM-MD5 PLAIN
> 250-AU
Hi All,
I have a query on SASL mechanism.
I have enabled 3 mechanisms and that can be seen as : -
ehlo localhost
250-proxy.test.com
250-PIPELINING
250-SIZE 1024
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN CRAM-MD5 PLAIN
250-AUTH=LOGIN CRAM-MD5 PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250
On Thursday 14 August 2008 12:46:26 sharad kanekar wrote:
> Thanks a lot for your reply,
> When I try to telnet on 110 port the error is as follows:
>
> [EMAIL PROTECTED] postfix]# telnet localhost 110
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^
Summary: Solaris and Linux file system behavior has changed over
time, breaking one of the assumptions in Postfix. See below for a
description of the behavior and how it disagrees with standards.
Postfix is not affected on systems with standard (POSIX, X/Open)
file system behavior, i.e. *BSD, AIX,
Now I am able to telnet on 110 port but unable to telnet on port 25
The error is as shown below. Please help me to overcome this problem.
Thanks in advance.
Sharad
telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
Connection closed b
Thanks a lot for your reply,
When I try to telnet on 110 port the error is as follows:
[EMAIL PROTECTED] postfix]# telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
+OK Dovecot ready.
USER sharad
+OK
PASS sharad
-ERR Authentication f
sharad kanekar wrote:
Dear All,
I am not able to telnet my mailserver on 110 and 25 port. My
postconf -n is as follows,
Please help me to rectify the problem of my server I am configuring
Postfix 2.3.3-2 on CentOS 5.2
Thanks.
[EMAIL PROTECTED] postfix]# postconf -n
alias_databa
Dear All,
I am not able to telnet my mailserver on 110 and 25 port. My
postconf -n is as follows,
Please help me to rectify the problem of my server I am configuring Postfix
2.3.3-2 on CentOS 5.2
Thanks.
[EMAIL PROTECTED] postfix]# postconf -n
alias_database = hash:/etc/aliases
alias_
* sharad kanekar <[EMAIL PROTECTED]>:
> I configured Postfix on CentOS 5.2 and try to download mails using fetchmail
> but facing problems .Please help me to rectify the problem. Thanks in
> advance.
Postfix is a SMTP server. It transports mail to mailboxes and remote servers,
but it does not deli
I configured Postfix on CentOS 5.2 and try to download mails using fetchmail
but facing problems .Please help me to rectify the problem. Thanks in
advance.
fetchmail -vvv
fetchmail: 6.3.6 querying mail.xxx.in (protocol POP3) at Wed 13 Aug 2008
11:24:25 PM IST: poll started
Trying to connect to xxx
* Alejandro Facultad <[EMAIL PROTECTED]>:
>>> apt-get install sasl2-bin libsasl2-modules
>>>
>>> /etc/default/saslauthd:
>>> START=yes
>>> MECHANISMS="ldap"
>>> MECH_OPTIONS=""
>>> THREADS=5
>>> OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd"
>>>
>>> /etc/saslauthd.conf:
>>> ldap_servers: ldap
55 matches
Mail list logo
