mysql write support patch updated to 3.4.5

I have updated Stefan Jakobs' patch (see https://marc.info/?l=postfix-users&m=128714800025241 ) to apply to postfix 3.4.5. https://wiki.jessen.ch/index/Postfix_with_mysql_write_support -- Per Jessen, Zürich (17.5°C)

Re: looks like smtpd_recipient_restrictions check_client_access is being ignored ?

Wietse Venema wrote: > Per Jessen: >> I have just built 2.11.1 from source, but otherwise retained >> my old config. >> >> For outgoing mail via port 587, I have the following: >> >> smtpd_recipient_restrictions=permit_mynetwork

looks like smtpd_recipient_restrictions check_client_access is being ignored ?

dress RESTRICTIONS <<< Should there not be a trace entry after "permit_sasl_authenticated status=0" that checks my pop-before-smtp table? What am I over looking? -- Per Jessen, Zürich (24.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

Re: address_verify_map

Per Jessen wrote: > Stefan Jakobs wrote: > >> Daniel L. Miller: >>> Can a SQL database be used for the recipient verification storage? >> >> The following link has a patch which enables Postfix to write to a >> MySQL Database. With that you can keep your v

Re: address_verify_map

own risk. > > https://api.opensuse.org/public/source/home:rusjako/postfix/postfix-mysql- > write-support.patch?rev=4f09d0df08b2763b6196cb24478b3e94& > > Regards > Stefan Hi Stefan I presume the table has to be created beforehand - do you have a template? thanks, Per -- Per Jessen, Zürich (19.8°C)

STARTTLS and mailservers who choke on it

bit of a hassle, so I was wondering how others handle it? thanks Per -- Per Jessen, Zürich (7.9°C)

Re: send copy of incoming mail to another user

Jon Miller wrote: > Like to know how do I send a copy of incoming mail to another user, > both the user and management requires the same mail > For all mail, see 'always_bcc' - for copies of one individuals mails, aliasing? /Per Jessen, Zürich

Re: Forcing postfix to check the MX entry

d" and an "outbound" instance. /Per Jessen, Zürich

Re: selective behaviour for reject_sender_login_mismatch ?

Victor Duchovni wrote: > On Tue, Dec 14, 2010 at 02:01:31PM +0100, Per Jessen wrote: > >> > The problem is that the SASL user name may well contain >> > white-space, and postmap(1) cannot create indexed tables with keys >> > that contain white-space. You c

Re: selective behaviour for reject_sender_login_mismatch ?

d Berkeley DB, but not with traditional "dbm" files, since you > can't atomically rename two files. Wouldn't this also be the case for smtpd_sender_login_maps ? /Per Jessen, Zürich

selective behaviour for reject_sender_login_mismatch ?

creating two restrictions classes: soft = warn_if_reject,reject_sender_login_mismatch hard = reject_sender_login_mismatch but I can't find an access table that is indexed by sasl userid. Is there a way to do this without a policy server? /Per Jessen, Zürich

Re: postfix bounce access table

Victor Duchovni wrote: > On Thu, Dec 09, 2010 at 10:51:18AM +0100, Per Jessen wrote: > >> I guess this is intended behaviour - there is no sender address, >> so the destination hostname is looked up instead, but shouldn't there >> also be a lookup with sender='

Re: bounce address in smtp_sasl_password_maps

Wietse Venema wrote: > Per Jessen: >> Perhaps I could have expanded "didnt seem to work" to "despite <> >> being present in my smtp_sasl_password_maps table, when a bounce is >> sent, no suitable userid+password is chosen for sasl authentication&qu

Re: postfix bounce access table

Per Jessen wrote: > This produces an ndr, which is also rejected due to lack of authentication, > as '<>' doesn't seem to be found in smtp_sasl_password_maps. Extract from a test with debug enabled: (suitably snipped & obscured) Dec 9 10:40:56 neon postfix

Re: bounce address in smtp_sasl_password_maps

Sahil Tandon wrote: > On Wed, 2010-12-08 at 10:09:42 +0100, Per Jessen wrote: > >> Is there a way of specifying the bounce/null address in an >> smtp_sasl_password_maps table ? I've tried using '<>', but that >> didn't seem to work. > >

Re: postfix bounce access table

Ralf Hildebrandt wrote: > * Per Jessen : >> Is there a way of specifying the bounce/null address in an >> smtp_sasl_password_maps table ? I've tried using '<>', but that >> didn't seem to work. > > Usually the smtpd_null_access_lookup

bounce address in smtp_sasl_password_maps

(resending with appropriate subject) Is there a way of specifying the bounce/null address in an smtp_sasl_password_maps table ? I've tried using '<>', but that didn't seem to work. thanks Per Jessen, Zürich

postfix bounce acces table

Is there a way of specifying the bounce/null address in an smtp_sasl_password_maps table ? I've tried using '<>', but that didn't seem to work. thanks Per Jessen, Zürich

Re: smtpd_tls_security_level encrypt or may ?

Jeroen Geilman wrote: > On 11/12/2010 10:36 AM, Per Jessen wrote: >> Jeroen Geilman wrote: >> >> >>> On 11/12/2010 09:05 AM, Per Jessen wrote: >>> >>>> I'm trying to setup an SMTP service on port 587, TLS required, >>

Re: Rewriting the envelope_sender

{2} > > However, this does not seem to get matched in any way. > > Anyone have any ideas? /^\"From:(.*)\"@(.*)/REPLACEFrom: $...@${2} /Per Jessen, Zürich

Re: smtpd_tls_security_level encrypt or may ?

Jeroen Geilman wrote: > On 11/12/2010 09:05 AM, Per Jessen wrote: >> I'm trying to setup an SMTP service on port 587, TLS required, >> authentication in plaintext allowed. >> >> What I can't understand is the following: >> >> with smtpd_tls_secur

smtpd_tls_security_level encrypt or may ?

250-AUTH PLAIN LOGIN DIGEST-MD5 CRAM-MD5 I also have smtpd_sasl_security_options=noanonymous. This is with postfix 2.6.2+cyrus. /Per Jessen, Zürich

Re: IDN domain name support

Per Jessen wrote: >> So, I think the IDN domain name support is not complete nowadays, >> neither by mail servers nor by mail clients. So it's not convenient >> the IDN mail implementation in this bad situation. >> >> What do you think about this matter

Re: IDN domain name support

plete nowadays, > neither by mail servers nor by mail clients. So it's not convenient > the IDN mail implementation in this bad situation. > > What do you think about this matter ??? I think you're wrong - my thunderbird and my postfix does fine with mails to and from @ënidan.ch (a test domain I set about two years ago). /Per Jessen, Zürich

Re: is there any way of distinguishing the bcc copy from the original?

Chris Babcock wrote: > On Sat, 08 Aug 2009 11:24:55 +0200 > Per Jessen wrote: > >> I'd like to treat the original and the bcc copy slightly different >> based on their content. Basically: >> >> a) original: if headerX matches condition1, override trans

is there any way of distinguishing the bcc copy from the original?

tches condition2 will also match condition1, but not vice versa. I was hoping there was e.g. a way of making an if-style header_check to apply different conditions to each copy. (I've already looked at running multiple cleanup daemons etc., but that gets very ugly very quickly). /Per Jessen, Zürich

Re: Question about log messages and connection caching

> > Wietse One more question then - by default the smtp client uses caching - do I need to explicitly enable caching for differently named transports that also use the smtp client? I.e. if I had a transport named 'klop', do I need klop_connection_cache_on_demand = yes ? /Per Jessen, Zürich

Re: Question about log messages and connection caching

k means that the type of tracking Ralf and I tried to do won't work. /Per Jessen, Zürich

Re: Question about log messages and connection caching

5:06:24 conn_use=7, Aug 30 15:06:46 delay=1.6, Aug 30 15:06:52 delay=3, Aug 30 15:08:05 delay=3.1, Aug 30 15:08:21 delay=3.9, Aug 30 15:08:29 conn_use=2, Whilst on the subject of connection caching, I assume postfix will (have to) do a RSET between each reuse of a connection? (just a sanity check on my part). /Per Jessen, Zürich

Re: Question about log messages and connection caching

Ralf Hildebrandt wrote: > * Per Jessen <[EMAIL PROTECTED]>: >> I'm using postfix 2.5.4. >> >> When I read the following in the log: >> >> postfix1/smtp[18518]: 4AD0517085: to=<[EMAIL PROTECTED]>, >> relay=myserver[myipaddr]:25, conn_use=4,

Question about log messages and connection caching

here should have been four 250 OK responses? Or am I just completely and utterly confused? /Per Jessen, Zürich

Re: [OT] Replacing Postfix servers

blems you're having? That many clients do not respect the round-robining? /Per Jessen, Zürich