[OFF]: DKIM broken by certain email clients

I've just set up DKIM on my mail system (via Astaro Security Gateway). If I send an email to [EMAIL PROTECTED] to comes back saying: DKIM check details: Result: fail (signature doesn't verify) The same thing happens sending from my iPhone. But it works fine sending from the same computer

Re: [OFF]: DKIM broken by certain email clients

On 24/09/2008, at 12:00 PM, Victor Duchovni wrote: On Wed, Sep 24, 2008 at 11:05:21AM +1000, James Brown wrote: I've just set up DKIM on my mail system (via Astaro Security Gateway). If I send an email to [EMAIL PROTECTED] to comes back saying: DKIM check details: Result: fail (signature

Re: [OFF]: DKIM broken by certain email clients

On 24/09/2008, at 1:54 PM, Benny Pedersen wrote: On Wed, September 24, 2008 03:05, James Brown wrote: I've just set up DKIM on my mail system (via Astaro Security Gateway). X-Amavis-Alert: BAD HEADER SECTION Duplicate header field: MIME-Version Thanks Benny. I'll send my reply using

Re: [OFF]: DKIM broken by certain email clients

+MRpo+qGiOfv0 fJtqDvR1TwbjuvSuRTHgQVCc1+AY3T4iDEQ5f4EGJ0NPR56rPqrKGDi1AwCGjvVD sieq86AnRWfredZLTHzXvzq5neSGOE= Message-Id: [EMAIL PROTECTED] From: James Brown [EMAIL PROTECTED] To: postfix-users@postfix.org In-Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Subject: Re: [OFF]: DKIM broken

Re: [OFF]: DKIM broken by certain email clients

Would anyone who checks DKIM sigs on incoming mails mind if I send them an email directly? That way I can make sure it is not just the DKIM reflector that's giving false results somehow. Thanks, James. smime.p7s Description: S/MIME cryptographic signature

Re: [OFF]: DKIM broken by certain email clients

On 25/09/2008, at 12:01 AM, Wietse Venema wrote: James Brown: The flow of my email is: Mail.app - ASSP - Postfix - amavisd-new - Postfix - Astarto Gateway - Internet I think :-) Your mail is modified AFTER the DKIM signature is computed. Therefore, the source of the message not breaking

Re: [OFF]: DKIM broken by certain email clients

Robert Schetterer wrote: James Brown schrieb: Would anyone who checks DKIM sigs on incoming mails mind if I send them an email directly? That way I can make sure it is not just the DKIM reflector that's giving false results somehow. Thanks, James. have you allready tried Sender Auth

Re: [OFF]: DKIM broken by certain email clients

On 25/09/2008, at 11:03 PM, Mark Martinec wrote: James, I'll have to work out how to turn off going through amavisd-new next. amavisd-new is DKIM-clean, it will not break a signature. Something else is modifying your Mime-Version header field. Mark Yes, I thought it must be DKIM-clean,

Re: Best anti-spam

On 22/10/2008, at 9:29 AM, Jim Balo wrote: Hi, I am currently using Postfix w/ Amavis-new, Pyzor, DCC and Clam. I have trained the Bayesian Classifier with over 2,000 ham and 2,000 spam, but I am still getting quite a bit of spam. I am about to install a new mail server and I wonder if there

Re: Make install or upgrade for new install location

On 01/05/2013, at 3:02 AM, Larry Stone lston...@stonejongleux.com wrote: I have been running Postfix under Mac OS X for a number of years (now on OS X 10.7.latest (Lion)). I am working on moving away from the Apple provided and customized Postfix to real Postfix built from sources. I've

Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

I’ve tried to upgrade my installation of Postfix from 2.10 to 2.11 (and to 2.11.1), but get this error: Undefined symbols for architecture x86_64: _pcre_free_study, referenced from: _dict_pcre_open in libutil.a(dict_pcre.o) _dict_pcre_close in libutil.a(dict_pcre.o) ld: symbol(s) not

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

Thanks Viktor. On 16 Jul 2014, at 4:23 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Wed, Jul 16, 2014 at 04:04:27PM +1000, James Brown wrote: I've tried to upgrade my installation of Postfix from 2.10 to 2.11 (and to 2.11.1), but get this error: Undefined symbols

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

On 16 Jul 2014, at 5:10 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Wed, Jul 16, 2014 at 04:49:49PM +1000, James Brown wrote: So change to: AUXLIBS=?-L/usr/local/lib -llber -lresolv -L/usr/lib ? ? Something like that. Since you're using headers from /usr/local/include

Compile errors on Mac: Undefined symbols for architecture x86_64: _FIPS_md_ctx_create

When compiling on Mac OS 10.7.5 using: make -f Makefile.init makefiles \ CCARGS='-arch x86_64 -DUSE_TLS -DUSE_SASL_AUTH \ -DDEF_SERVER_SASL_TYPE=\dovecot\ \ -DDEF_COMMAND_DIR=\/usr/local/sbin\ \ -DDEF_CONFIG_DIR=\/usr/local/etc/postfix\ \ -DDEF_DAEMON_DIR=\/usr/local/libexec/postfix\ \

Re: Compile errors on Mac: Undefined symbols for architecture x86_64: _FIPS_md_ctx_create

On 17 Jul 2014, at 1:14 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: This is silly, the placement of -L options is irrelevant, only their relative order matters. To not get confused, list all -L options before all -lsomelib options, no point in listing anything twice.

Re: Compile errors on Mac: Undefined symbols for architecture x86_64: _FIPS_md_ctx_create

On 17 Jul 2014, at 1:54 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Thu, Jul 17, 2014 at 01:38:39PM +1000, James Brown wrote: make command is now: make -f Makefile.init makefiles \ CCARGS='-arch x86_64 -DUSE_TLS -DUSE_SASL_AUTH \ -DDEF_SERVER_SASL_TYPE=\dovecot

Re: Compile errors on Mac: Undefined symbols for architecture x86_64: _FIPS_md_ctx_create

On 17 Jul 2014, at 3:37 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Thu, Jul 17, 2014 at 03:22:28PM +1000, James Brown wrote: $ locate lib/libssl /usr/lib/libssl.0.9.7.dylib /usr/lib/libssl.0.9.8.dylib /usr/lib/libssl.1.0.0.dylib /usr/lib/libssl.a /usr/lib/libssl.dylib

Re: Compile errors on Mac: Undefined symbols for architecture x86_64: _FIPS_md_ctx_create

./Configure --prefix=/usr/local shared darwin64-x86_64-cc Configured OpenSSL using this, then was able to use: make -f Makefile.init makefiles \ CCARGS='-arch x86_64 -DUSE_TLS -DUSE_SASL_AUTH \ -DDEF_SERVER_SASL_TYPE=\dovecot\ \ -DDEF_COMMAND_DIR=\/usr/local/sbin\ \

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

On 17 Jul 2014, at 11:41 am, James Brown jlbr...@bordo.com.au wrote: On 16 Jul 2014, at 5:10 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Wed, Jul 16, 2014 at 04:49:49PM +1000, James Brown wrote: So change to: AUXLIBS=?-L/usr/local/lib -llber -lresolv -L/usr/lib

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

On 14 Oct 2014, at 4:13 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Tue, Oct 14, 2014 at 03:16:17PM +1100, James Brown wrote: Victor, changing the order so that it is: make -f Makefile.init makefiles \ CCARGS='-arch x86_64 -DUSE_TLS -DUSE_SASL_AUTH

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

On 14 Oct 2014, at 5:26 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Tue, Oct 14, 2014 at 05:19:34PM +1100, James Brown wrote: Thanks for your help Victor. make -f Makefile.init makefiles \ CCARGS='-arch x86_64 -DUSE_TLS -DUSE_SASL_AUTH \ -DDEF_SERVER_SASL_TYPE=\dovecot

Re: Compile errors on Mac Undefined symbols for architecture x86_64: _pcre_free_study

On 15 Oct 2014, at 4:19 am, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Tue, Oct 14, 2014 at 09:13:41PM +1100, James Brown wrote: What version of MacOSX are you running? (Post the output of uname -sr.) The Postfix makedefs script has: # Darwin 12.x (MacOS X 10.8.x

Re: Postfix stable release 2.11.3 and legacy releases 2.10.5, 2.9.11, and 2.8.19

On 20 Oct 2014, at 3:12 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Mon, Oct 20, 2014 at 03:00:01PM +1100, James Brown wrote: * Portability fix for MacOS X 10.7.x (Darwin 11.x) build procedure. Doesn't seem to work for me. :-( Don't blame the messenger I’m definitely

Re: Postfix stable release 2.11.3 and legacy releases 2.10.5, 2.9.11, and 2.8.19

On 20 Oct 2014, at 11:04 am, Wietse Venema wie...@porcupine.org wrote: Portability fix for Postfix 2.11: * Portability fix for MacOS X 10.7.x (Darwin 11.x) build procedure. Doesn’t seem to work for me. :-( $ cd postfix-2.11.3 $ make -f Makefile.init makefiles \ CCARGS='-arch x86_64

Re: Postfix stable release 2.11.3 and legacy releases 2.10.5, 2.9.11, and 2.8.19

On 20 Oct 2014, at 3:22 pm, Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Mon, Oct 20, 2014 at 04:12:00AM +, Viktor Dukhovni wrote: You'll find that 2.11.2 also no longer compiles. Nothing between 2.11.2 and 2.11.3 changed in this regard. Did you upgrade your OS (to

Re: HowTo AntiSpam for "Beginners"

I use ASSP, which is incredibly comprehensive as an anti-malware solution for mail servers. It integrates with clamav - make sure you get the third party signatures like SaneSecurity, as that will stop heaps more. It’s under active development. It has heaps of configuration options, so might

Re: macOS X, Operation not permitted - rename sendmail

On 2 Nov 2018, at 4:11 pm, Viktor Dukhovni mailto:postfix-us...@dukhovni.org>> wrote: > > On Fri, Nov 02, 2018 at 03:09:02PM +1100, James Brown wrote: > >> I run make with: >> >> $ make -f Makefile.init makefiles CCARGS='-DUSE_TLS -DUSE_SASL_AUTH \ &g

Re: macOS X, Operation not permitted - rename sendmail

> On 1 Oct 2018, at 6:13 pm, Viktor Dukhovni <mailto:postfix-us...@dukhovni.org>> wrote: > > On Mon, Oct 01, 2018 at 05:56:57PM +1000, James Brown wrote: > >> I’ve just tired to install Postfix 3.3.1 on macOS X 10.13.6 High Sierra. >> >> Sudo make inst

Re: Compiler error on 3.3.1. Mac Mojave

On 8 Nov 2018, at 8:20 pm, Robert Chalmers wrote: > > > It’s almost through the build but failing on this. > > Undefined symbols for architecture x86_64: > "_db_create", referenced from: > import-atom in libpostfix-util.dylib > "_db_env_create", referenced from: > import-atom in

Re: How do I turn on logging for postfix on mac

I’ve been having the same issue. Apple changed their logging system a few releases ago (Sierra?) to use the Unified Logging System, which logs to RAM rather than disk files. I can create the file at /var/log/mail.log, give it correct permissions, etc, but it remains at 0 bytes. I have managed

macOS X, Operation not permitted - rename sendmail

I’ve just tired to install Postfix 3.3.1 on macOS X 10.13.6 High Sierra. Sudo make install finishes with: Updating /usr/sbin/sendmail... mv: rename /Users/jlbrown/Downloads/postfix-3.3.1/junk to /usr/sbin/sendmail: Operation not permitted make: *** [install] Error 1 My make command was: make

Re: Postfix logging without syslogd

On 22 Jan 2019, at 5:22 pm, James Brown mailto:jlbr...@bordo.com.au>> wrote: > > On 22 Jan 2019, at 5:18 pm, Larry Stone <mailto:lston...@stonejongleux.com>> wrote: >> >> On Jan 21, 2019, at 6:04 PM, Wietse Venema > <mailto:wie...@porcupine.org>>

Re: Postfix logging without syslogd

On 22 Jan 2019, at 11:04 am, Wietse Venema mailto:wie...@porcupine.org>> wrote: > > postfix-3.4-20190121-nonprod-logger has lightly-tested code for > logging to file without using syslogd. > > This solves a usability problem in MacOS, may help to work around > a logging bottleneck with systemd,

Re: Postfix logging without syslogd

Mojave system and so far, all looks good. > One test email sent out (my Postfix is outgoing only) was properly logged. > Have not tested anything yet involving log rotation. Unlike James Brown and > his Unsupported Berkeley DB version, I do not have Berkeley DB on my system > (unle

Master.cf Transport type - piping to Perl. How can I specify path to Perl?

I have Postfix Admin’s Vacation setup and would like to use the Perl at /usr/local/bin/perl rather than /usr/bin/perl. I have: vacationunix- n n - - pipe flags=DRhu user=_vacation argv="/usr/local/bin/perl /var/spool/vacation/vacation.pl" -f

Re: Master.cf Transport type - piping to Perl. How can I specify path to Perl?

On 21 Jan 2019, at 3:59 pm, James Brown wrote: > > I have Postfix Admin’s Vacation setup and would like to use the Perl at > /usr/local/bin/perl rather than /usr/bin/perl. > > I have: > > vacationunix- n n - - pipe >f

Compile error on Mojave (Postfix 3.3.2): 'openssl/opensslv.h' file not found

I have installed OpenSSL v1.1.1 via Homebrew. I’m trying to install Postfix 3.3.2 but it always ends with: cc -I. -I../../include -DUSE_TLS -DUSE_SASL_AUTH -DDEF_SERVER_SASL_TYPE=\"dovecot\" -DDEF_COMMAND_DIR=\"/usr/local/sbin\" -DDEF_CONFIG_DIR=\"/usr/local/etc/postfix\"

Re: Compile error on Mojave (Postfix 3.3.2): 'openssl/opensslv.h' file not found

> On 28 Nov 2018, at 11:20 pm, Herbert J. Skuhra wrote: > > On Wed, Nov 28, 2018 at 11:00:33PM +1100, James Brown wrote: >> >> On Wed, Nov 28, 2018 at 09:55:02PM +1100, James Brown wrote: >>> ... >>> My Make script is: >>> >>

New install - Temporary lookup failures when trying to send

I’m trying to set up a new mail server on macOS Mojave and it almost works. Dovecot for IMAP is working. But when I try to send a message I get: Escape character is '^]'. 220 mail.bordo.com.au ESMTP Postfix HELO me.bordo.com.au 250

Re: New install - Temporary lookup failures when trying to send

> On 7 Dec 2018, at 1:23 am, Matus UHLAR - fantomas wrote: > > Anyway, sorry for the noise. > > however, my questions weren't responded and still apply: > > Are those cf files properly configured? Can postfix connect to the > database? > What's in the logs? > > and also the

Re: Compile error on Mojave (Postfix 3.3.2): 'openssl/opensslv.h' file not found

> On 28 Nov 2018, at 10:38 pm, Herbert J. Skuhra <mailto:herb...@gojira.at>> wrote: > > On Wed, Nov 28, 2018 at 09:55:02PM +1100, James Brown wrote: >> I have installed OpenSSL v1.1.1 via Homebrew. I’m trying to install Postfix >> 3.3.2 but it always ends with:

Re: Upgraded to 3.4 today. All logging has Stopped?

> On 30 Nov 2018, at 4:07 am, Viktor Dukhovni > wrote: > > >> On Nov 29, 2018, at 9:15 AM, Robert Chalmers wrote: >> >> I upgraded to and installed 3.4 today. It appears to be running, but all >> logging has stopped. The last entry in the log file was at the exact time I >> started the

Re: Upgraded to 3.4 today. All logging has Stopped?

> On 10 Jan 2019, at 2:01 pm, Larry Stone <mailto:lston...@stonejongleux.com>> wrote: > > On Jan 9, 2019, at 19:01, James Brown <mailto:jlbr...@bordo.com.au>> wrote: >> >> Thanks Viktor. It would be great if Postfix would log to disk on newer >&g

Re: Upgraded to 3.4 today. All logging has Stopped?

On 11 Jan 2019, at 4:08 am, Wietse Venema wrote: > > Larry Stone: >>> # Log file to use for error messages. "syslog" logs to syslog, >>> # /dev/stderr logs to stderr. >>> #log_path = syslog >>> log_path = /var/log/mail.log >>> >>> So I?ve had to change this so that it writes directly to the

Authentication attempts for x...@com.au addresses

Not sure if this is a Dovecot or Postfix issue we use Dovecot for authentication for Postfix. Mailboxes are stored in MySQL. Have noticed this today: auth-worker(42777): Info: sql(cont...@com.au,127.0.0.1): unknown user (given password: someone123) Also i...@com.au etc. They are coming

Re: Authentication attempts for x...@com.au addresses

> On 3 Apr 2019, at 9:45 am, Curtis Maurand > wrote: > > > > On 4/2/19 5:39 PM, @lbutlr wrote: >> On 2 Apr 2019, at 14:30, Esteban L > > wrote: >>> The times are in seconds, so you'll need to calculate those times. >> a month is

Change 451 Temp Lookup code to permanent 550 code for unknown local recipients

Postfix 3.4.0, using Dovecot for SASL authentication and MySQL. I have set: unknown_local_recipient_reject_code = 550 But when an email comes through to an unknown user, a 451 Temporary Lookup Failure code is given, not a 550: 2019-03-04 15:52:00.949864+1100 localhost smtpd[25337]: connect

Re: Change 451 Temp Lookup code to permanent 550 code for unknown local recipients

> On 4 Mar 2019, at 4:40 pm, Viktor Dukhovni wrote: > > [ Just this once, I'm going to make an exception and send HTML email. It's > only >new content is colour added to two snippets of the original text. ] > >> On Mar 4, 2019, at 12:29 AM, James Brown wrote:

Re: Is it possible to run postfix in a container (e.g. docker, red-hot)?

> On 7 Aug 2019, at 5:32 pm, Gerben Wierda wrote: > > Simple question: > > Is it possible to run postfix in a container (e.g. docker, red-hot)? > > I’m looking into a new platform for my postfix as my current platform (macOS > High Sierra + Server with Apple-provided postfix) is end-of-life.

Re: Suggestions for less spam

> On 23 Sep 2019, at 1:59 am, Dominic Raferd wrote: > > On Sun, 22 Sep 2019 at 14:36, Paul van der Vlis wrote: >> >> Hello, >> >> I would like some suggestions on how to get less spam, I will paste my >> configuration at the end of the mail. >> >> Maybe somebody with a nice setup could post

Re: Issues creating makefile - lines commented out

> On 25 Feb 2023, at 12:09 pm, Wietse Venema wrote: > > James Brown: >> Now it just has one error: >> >> dict_mysql.c:171:10: fatal error: 'mysql.h' file not found >> #include >> ^ >> 1 error generated. >> make: *** [

Re: Issues creating makefile - lines commented out

> On 25 Feb 2023, at 4:10 pm, Viktor Dukhovni > wrote: > > On Sat, Feb 25, 2023 at 03:54:05PM +1100, James Brown wrote: > >> % make -f Makefile.init makefiles CCARGS="-DUSE_TLS -DUSE_SASL_AUTH \ >> -DDEF_SERVER_SASL_TYPE="dovecot"

Issues creating makefile - lines commented out

Sorry if this is a bit of a basic question, but I’m trying to compile from source on macOS 13.21.1 but the makefile has lines commented out. I’m trying: make -f Makefile.init makefiles \ CCARGS='-DUSE_TLS -DUSE_SASL_AUTH \ -DDEF_SERVER_SASL_TYPE=\"dovecot\" \

Re: Issues creating makefile - lines commented out

> On 25 Feb 2023, at 2:41 am, Wietse Venema wrote: > > Wietse Venema: >> James Brown: >>>> On 24 Feb 2023, at 11:57 pm, Wietse Venema wrote: >>>> >>>> James Brown: >>>>> Sorry if this is a bit of a basic question, but I?m tryi