Re: myorigin

* Tobias Köck: > I am wondering why the source email adresse is still not > 'usern...@mydomain.de' but instead 'usern...@mail.mydomain.de'? Postfix settings aside, Mutt can be configured to generate specific sender addresses: # Your .muttrc set hostname=somehost.example.com set

Re: myorigin

postfix appends myorigin only if the domain is not present (and if append_at_myorigin is yes, but it's the default) Interesting. I haven't seen this depencendy. Where can I find it (in the documentation)?

Re: myorigin

On 18.07.19 18:44, Tobias Köck wrote: I found the reason why Debian uses a file named /etc/mailname https://wiki.debian.org/EtcMailName If this file is set with another name it seems to be the case that Postfix uses this file even if I have explicitely overwritten the myorigin with

Re: myorigin

I found the reason why Debian uses a file named /etc/mailname https://wiki.debian.org/EtcMailName If this file is set with another name it seems to be the case that Postfix uses this file even if I have explicitely overwritten the myorigin with another value. I'm still a little bit

Re: encoding issue with header_checks Windows-1252

I dont get it. Testing the above correctly shows Subject: =?Windows-1252?Q?[Cleartext]_Webinar_=84Noch_keine_55_und_ab_in_die_GKV=93?= FILTER cleartext: But the e-mail itself was not passed to the FILTER cleartext. Above subject was extracted from mail client. I believe, there is something going

Re: myorigin

Hi> $ postconf myorigin If that is really mydomain.de, then mutt is giving Postfix the wrong sender address, and you need to configure mutt. Yes it's really mydomain.de. I was testing the mail command additioinaly of mutt to verify. Is there another internal testing possiblity to send an

Re: myorigin

Tobias K?ck: > Hi, > > I have setup > > myorigin=mydomain.de > > but if I send an email with MUTT emai client or with 'echo "test" | > mail' s...@email.de I get as email source > > usern...@mail.mydomain.de (the name of the mailserver). What is the output from: $ postconf myorigin

myorigin

Hi, I have setup myorigin=mydomain.de but if I send an email with MUTT emai client or with 'echo "test" | mail' s...@email.de I get as email source usern...@mail.mydomain.de (the name of the mailserver). For testing I have added the mydomain.de to the mydestination and the mx entry is set

Re: encoding issue with header_checks Windows-1252

Stefan Bauer: > Hi, > > header_checks = regexp:/etc/postfix/headerstring > /^Subject: .*\[cleartext\].*/ FILTER cleartext: > > And now, there is the following mail-Subject, that did not trigger the > above FILTER and i dont see why: > > Subject: >

Re: encoding issue with header_checks Windows-1252

only this single filter is present - no other filters. Unfortunately thats not enough to trigger the filter. Am Do., 18. Juli 2019 um 14:00 Uhr schrieb pasvon : > What does the complete file /etc/postfix/headerstring look like? > Does another line match a filter action and override the desired

Re: encoding issue with header_checks Windows-1252

On 18.07.19 13:42, Stefan Bauer wrote: man 5 header_checks By default, regexp : and pcre : patterns are case *insensitive*. sorry, misread. Should be more careful.. Am Do., 18. Juli 2019 um 13:40

Re: encoding issue with header_checks Windows-1252

What does the complete file /etc/postfix/headerstring look like? Does another line match a filter action and override the desired result? Have you defined any other header_checks (body for example)? That should be enough, too: /^Subject: .*\[cleartext\]/ FILTER cleartext: -- Sent from:

Re: encoding issue with header_checks Windows-1252

man 5 header_checks By default, regexp : and pcre : patterns are case *insensitive*. Am Do., 18. Juli 2019 um 13:40 Uhr schrieb Matus UHLAR - fantomas < uh...@fantomas.sk>: > On 18.07.19 13:35, Stefan

Re: encoding issue with header_checks Windows-1252

On 18.07.19 13:35, Stefan Bauer wrote: header_checks = regexp:/etc/postfix/headerstring /^Subject: .*\[cleartext\].*/ FILTER cleartext: And now, there is the following mail-Subject, that did not trigger the above FILTER and i dont see why: Subject:

encoding issue with header_checks Windows-1252

Hi, header_checks = regexp:/etc/postfix/headerstring /^Subject: .*\[cleartext\].*/ FILTER cleartext: And now, there is the following mail-Subject, that did not trigger the above FILTER and i dont see why: Subject: =?Windows-1252?Q?[Cleartext]_Webinar_=84Noch_keine_55_und_ab_in_die_GKV=93?= Any