And finally I think I've stumbled on to something that may be the culprit.
DNS.
Again be gentle with me here because I'm in unchartered waters here.
I own two domains
hagensieker.com (GoDaddy)
hagensieker.org (NameCheap)
My computer hostname is set to mail.hagensieker.com (Is this a
On 08/12/2014 08:08 AM, hagensieker wrote:
Terribly confused at this point?
Yes. I recommend that you get the excellent The Postfix book[1] by
Ralf and Patrick before getting in the world of e-mail and Postfix. Once
you read it cover to cover and understand the concepts, everything will
become
Ok I am learning. Here is what i did. I changed my hostname and /etc/hosts
file to reflect hagensieker.org
Then I changed all the appropriate entries in main.cf.
Then changed the host relayhost to the NameCheap relay host. Then restarted
postfix
Then went to Thunderbird on my Linux box and
On Tue, Aug 12, 2014 at 1:44 AM, Bill Cole
postfixlists-070...@billmail.scconsult.com wrote:
On 11 Aug 2014, at 10:22, li...@rhsoft.net wrote:
http://serverfault.com/questions/619537/use-postfix-
and-spamassassin-packages-on-centos-6-to-reject-spam-without-custo
Also worth noting:
Hello again,
On Tue, Aug 12, 2014 at 9:34 AM, Alexander Farber
alexander.far...@gmail.com wrote:
On 11 Aug 2014, at 10:22, li...@rhsoft.net wrote:
http://serverfault.com/questions/619537/use-postfix-
and-spamassassin-packages-on-centos-6-to-reject-spam-without-custo
the point of my
Am 12.08.2014 um 08:08 schrieb hagensieker:
And finally I think I've stumbled on to something that may be
the culprit. DNS.
surely, the outside world needs to deliver to your machine
your MX pints to secureserver.net
Again be gentle with me here because I'm in unchartered waters here.
I
i am trying to use this feature in postfix 2.11:
http://www.postfix.org/postconf.5.html#milter_header_checks
I have created a milter which adds a Header: X-Body: bla and i'd like
to filter mails, unfortunately the cleanup process doesn't support pcre
for milter_header_checks, if i use the same
Am 12.08.2014 um 13:59 schrieb Matthias Schneider:
i am trying to use this feature in postfix 2.11:
http://www.postfix.org/postconf.5.html#milter_header_checks
I have created a milter which adds a Header: X-Body: bla and i'd like to
filter mails, unfortunately the cleanup
process doesn't
please note that pcre is working fine with normal header_checks, the
problem is just with milter_header_checks :
# postconf -m
btree
cidr
environ
fail
hash
internal
memcache
nis
pcre
proxy
regexp
sdbm
socketmap
sqlite
static
tcp
texthash
unix
what does postconf -m list - most likely not pcre
BTW, the point of Bill Cole's post (I almost posted something
similar) was that you put the GTUBE string right here in a public
mailing list. Most people who use SpamAssassin thus would not get
your post: it was flagged as spam, of course. That's the idea; the
GTUBE string is to test
On 08/11/2014 10:17 PM, hagensieker wrote:
And here is dovecot.conf
How about /sbin/iptbles -vnL | egrep '((DROP)|(REJECT)) ?
Or, if you are running a mostly-closed firewall configuration, the
output of /sbin/iptables -vnL | egrep '((:25)|(:143)|(:587)) ?
i searched the code what returns the error, hope this will help.
if you have any suggestions or experimantal code changes i'll compile
and test them
with my addheader milter.
Best regards
Matthias Schneider
cleanup_milter.c:
381 static int cleanup_milter_header_checks(CLEANUP_STATE *state,
I found a solution, turning off chroot for cleanup in master.cf
cleanup unix n - n - 0 cleanup
this should be added to the documention:
http://www.postfix.org/postconf.5.html#milter_header_checks
On Tue, Aug 12, 2014 at 04:04:46PM +0200, Matthias Schneider wrote:
I found a solution, turning off chroot for cleanup in master.cf
cleanup unix n - n - 0 cleanup
this should be added to the documention:
Am 12.08.2014 um 16:04 schrieb Matthias Schneider:
I found a solution, turning off chroot for cleanup in master.cf
cleanup unix n - n - 0 cleanup
this should be added to the documention:
http://www.postfix.org/postconf.5.html#milter_header_checks
no -
On 12 Aug 2014, at 8:38, /dev/rob0 wrote:
BTW, the point of Bill Cole's post (I almost posted something
similar) was that you put the GTUBE string right here in a public
mailing list. Most people who use SpamAssassin thus would not get
your post: it was flagged as spam, of course. That's the
Hi there,
I know this is a common error but I swear I checked everything, yet still get
that error trying to setup Postfix with Cyrus SASL on Debian wheezy.
Here’s my confgs:
/etc/postfix/sasl/smtp.comf:
pwcheck_method: saslauthd
mech_list: PLAIN LOGIN
saslauthd_path: /var/run/saslauthd/mux
El 2014-08-12 22:29, pavel degtiarev escribió:
Hi there,
I know this is a common error but I swear I checked everything, yet
still get that error trying to setup Postfix with Cyrus SASL on Debian
wheezy.
Here’s my confgs:
/etc/postfix/sasl/smtp.comf:
Be careful with the extension.
Sorry, typo: /etc/postfix/sasl/smtpd.conf - that’s what I have.
On Aug 12, 2014, at 6:13 PM, nico...@devels.es wrote:
El 2014-08-12 22:29, pavel degtiarev escribió:
Hi there,
I know this is a common error but I swear I checked everything, yet
still get that error trying to setup Postfix with
* nico...@devels.es nico...@devels.es:
El 2014-08-12 22:29, pavel degtiarev escribió:
Hi there,
I know this is a common error but I swear I checked everything, yet
still get that error trying to setup Postfix with Cyrus SASL on Debian
wheezy.
Here’s my confgs:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
It does not look like postfix is chrooted, 1831 is postfix pid.
The entry in master.cf also points to non chrooted install:
smtps inet n - - - - smtpd
* pavel degtiarev paul.d...@gmail.com:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
It does not look like postfix is chrooted, 1831 is postfix pid.
The entry in master.cf also points to non chrooted install:
smtps inet
Am 13.08.2014 um 01:52 schrieb Patrick Ben Koetter:
* pavel degtiarev paul.d...@gmail.com:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
It does not look like postfix is chrooted, 1831 is postfix pid.
The entry in master.cf also
* li...@rhsoft.net li...@rhsoft.net:
Am 13.08.2014 um 01:52 schrieb Patrick Ben Koetter:
* pavel degtiarev paul.d...@gmail.com:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
It does not look like postfix is chrooted,
On Wed, Aug 13, 2014 at 01:56:41AM +0200, li...@rhsoft.net wrote:
Am 13.08.2014 um 01:52 schrieb Patrick Ben Koetter:
* pavel degtiarev paul.d...@gmail.com:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
It does not look like
Am 13.08.2014 um 02:07 schrieb Patrick Ben Koetter:
* li...@rhsoft.net li...@rhsoft.net:
Am 13.08.2014 um 01:52 schrieb Patrick Ben Koetter:
* pavel degtiarev paul.d...@gmail.com:
I checked that as well:
ls -ld /proc/1831/root
lrwxrwxrwx 1 root root 0 Aug 12 17:14 /proc/1831/root - /
On Wed, Aug 13, 2014 at 02:42:47AM +0200, li...@rhsoft.net wrote:
what i meant is if it is not recommended why - means yes
The recommended *configuration* is an explicit chroot=no, the
default behaviour of the software is to be more secure when no
explicit setting is specified.
This is not
I changed Postfix to non chroot, plus some manipulation on saslauthd path
permissions, and it worked. I must say that testsaslauthd thing is really
confusing, it makes it look like it’s all postfix fault. :-)
Thanks a lot guys!
On Aug 12, 2014, at 9:17 PM, Viktor Dukhovni
Hi,
I only see information on smtpd_tls_wrapper_mode in TLS_README. Am I
missing it?
That's the one. http://www.postfix.org/TLS_README.html#server_enable
follow the instructions as written.
Okay, I believe I have it working properly, but wanted to be sure, and also
that my understanding
On Tue, Aug 12, 2014 at 11:49:05PM -0400, Alex wrote:
I've enabled debug for my test host, and after restart postfix, I've tested
it with the following openssl command:
# openssl s_client -connect mail.example.com:465
You've not specified a CAfile or CApath. See s_client(1).
It connects,
30 matches
Mail list logo
