ord file.
The issue I am trying to overcome is not the lack of a From: header;
that one can be expected to always exist in my particular use case.
For me, the relevant issue is that when using the sendmail binary, the
envelope sender address defaults to no
matter the From: header's value. As
t
> which runs Postfix, and Bob sends the message like so:
>
> $ /usr/sbin/sendmail -t < ~/sample.eml
>
> This would typically result in an envelope sender address like
> , which may not be reachable from the outside.
> To force a different envelope sender address, Bob cou
Consider a pre-generated text file sample.eml like this one:
From: Bob
To: al...@example.org
Subject: foobar
The message body goes here...
Imagine further that Bob is logged in as user123 on host.example.net
which runs Postfix, and Bob sends the message like so:
$ /usr/sbin/sendmail
You don't say where the error message is reported or by what. Something
else is invoking Postfix's sendmail incorrectly.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Jason Hirsh via Postfix-users:
> I assume that this error wont interfere with with postfix other operations?
You are invoking a non-Postfix sendmail command.
That is where my support ends.
Wietse
___
Postfix-users mailing list -- postfix-us
d FreeBSD 14.1. When I first installed Postfix
>> I added the following to rc.conf
>>
>> sendmail_enable="NO"
>> sendmail_submit_enable="NO"
>> sendmail_outbound_enable="NO"
>> sendmail_msp_queue_enable="NO"
>> po
; sendmail_submit_enable="NO"
> sendmail_outbound_enable="NO"
> sendmail_msp_queue_enable="NO"
> postfix_enable="YES"
>
> This use to disable sendmail
>
> System seems to work fine accept for the error message. Why would postfix
> be calli
sendmail_msp_queue_enable="NO"
postfix_enable="YES"
This use to disable sendmail
System seems to work fine accept for the error message. Why would postfix be
calling sendmail??___
Postfix-users mailing list -- postfix-users@p
On Sun, Jun 23, 2024 at 06:06:40PM +, Дилян Палаузов wrote:
> «sendmail -v myself@domain» however hangs.
Of course it does, it is waiting to read the message headers and body
from standard input as expected.
> until I press Ctrl+C. This is Postfix 3.4.13. On Postfix 2.11 the
l_recipient_maps, virtual_mailbox_maps,
relay_recipient_maps).
Which is why just cargo-cult is difficult to specify without the full
picture of your entire setup, but that's too much work to take in unless
you hire a paid consultant. In your place, I'd have stuck with Sendmail
on FreeBSD,
On Mon, Mar 18, 2024 at 12:50:18AM -0700, Glenn Tenney via Postfix-users wrote:
> On Monday, March 18, 2024, Benny Pedersen via Postfix-users <
>
> > Victor gave a vierd config :)
> >
> > postfix must not return any result on non existsing users, so if this
> > gives no result user is unknown, with
On Monday, March 18, 2024, Benny Pedersen via Postfix-users <
postfix-users@postfix.org> wrote:
> catch all is badly advised, it makes recipient validation impososibe,
> don't do it
>
> define maps with what is wanted, not with what is not wanted, catch-all is
> unwanted
>
I know, but a couple of
Glenn Tenney via Postfix-users skrev den 2024-03-18 08:50:
Thanks. I’m hosting several domains: a couple need to accept any
user@ except some that specifically need to be rejected delivering
locally; some domains are more normal, just accept specific users &
deliver to some local user (sometimes
On Monday, March 18, 2024, Benny Pedersen via Postfix-users <
postfix-users@postfix.org> wrote:
> Glenn Tenney via Postfix-users skrev den 2024-03-18 03:52:
>
> My question in one, hopefully simple sentence, is:
>>
>> In Postfix, how do I configure Postfix such that all email to
>> "user@some.doma
Glenn Tenney via Postfix-users skrev den 2024-03-18 03:52:
My question in one, hopefully simple sentence, is:
In Postfix, how do I configure Postfix such that all email to
"user@some.domain" will return an error code (e.g. 550 user unknown)
to bounce that email
Victor gave a vierd config
On Sunday, March 17, 2024, Viktor Dukhovni via Postfix-users <
postfix-users@postfix.org> wrote:
> > > - You can reject SMTP recipients via various restriction checks
> > > that perform access(5) lookups against tables of your choice.
> >
> > How can I do it not based on the network or d
On Sun, Mar 17, 2024 at 09:52:10PM -0700, Glenn Tenney via Postfix-users wrote:
> > It is a reserved domain name, (one of many) that you can use internally,
> > without clashing with *real domains*.
>
> Wow. Once you KNOW it's there, you can find out about "local.invalid".
> BUT if you didn't kno
Monday, March 18, 2024, 3:01:11 PM, Glenn Tenney via Postfix-users wrote:
> On Sun, Mar 17, 2024 at 8:05 PM Phil Biggs via Postfix-users
> wrote:
>> Not sure about the rest of your requirements but perhaps
>>
>> smtpd_recipient_restrictions = reject_unverified_recipient
>> https://www.postfix.or
it automatic that every other email address
> > (not listed there) will be rejected?
>
> Only for virtual alias domains, for other domains, you may need
> a separate valid recipient table, see:
>
> https://www.postfix.org/ADDRESS_CLASS_README.html
> Because you're loo
On Sun, Mar 17, 2024 at 8:05 PM Phil Biggs via Postfix-users
wrote:
> Not sure about the rest of your requirements but perhaps
>
> smtpd_recipient_restrictions = reject_unverified_recipient
> https://www.postfix.org/ADDRESS_VERIFICATION_README.html
I don't think I can do that because I host a cou
mail addresses for a
> hosted domain, then is it automatic that every other email address
> (not listed there) will be rejected?
Only for virtual alias domains, for other domains, you may need
a separate valid recipient table, see:
https://www.postfix.org/ADDRESS_CLASS_README.html
On Mon, Mar 18, 2024 at 02:04:55PM +1100, Phil Biggs via Postfix-users wrote:
> Monday, March 18, 2024, 1:52:46 PM, Glenn Tenney via Postfix-users wrote:
> Not sure about the rest of your requirements but perhaps
>
> smtpd_recipient_restrictions = reject_unverified_recipient
>
> https://www.pos
Monday, March 18, 2024, 1:52:46 PM, Glenn Tenney via Postfix-users wrote:
> My question in one, hopefully simple sentence, is:
> In Postfix, how do I configure Postfix such that all email to
> "user@some.domain" will return an error code (e.g. 550 user unknown)
> to bounce that email
> Gl
On Sun, Mar 17, 2024 at 3:40 PM Viktor Dukhovni via Postfix-users
wrote:
> My general advice is to use aliases(5) very sparingly, just for lists
> that require an "owner-" or ":include:" lists. All other rewrites
> should be via virtual(5), and perhaps even keep $mydestination empty!
>
> Add "loc
o be specific, it's been some decades since
> many of us have looked at Sendmail. Much depends on what sort of
> mappings you're looking to emulate.
"most of what" is in the text I included below my questions. I thought
that would have been very clear. That's why I i
be specific, it's been some decades since
many of us have looked at Sendmail. Much depends on what sort of
mappings you're looking to emulate.
For 1-to-many recipient rewrites, the best vehicle is indeed virtual(5),
but if you also use local aliases(5), and $myorigin is listed in
$mydestinati
Now that I seem to have postfix running ok on my replacement server
(going from Linux/Sendmail to Freebsd/Postfix), I have to convert all
of my "virtusertable" entries over to postfix. I've read through
https://www.postfix.org/VIRTUAL_README.html &
https://www.postfix.org/post
hawky--- via Postfix-users:
> Is there a way to stop resolving a second time the alias table with the
> after-queue approach?
With "pickup -o receive_override_options=no_address_mappings...",
but that disables virtual_alias_maps lookup for all submissions
through the Postfix
Hi,
We've a SpamAssassin setup with the after-queue approach.
When re-submission a mail, that has been content filtered by
SpamAssassin, with sendmail we see that the mail is delivered twice to
the recipient, if the user has a forwarding email set.
From our understanding that is a resu
there is no $sendmail_relay_restrictions configuration
like what $smtpd_relay_restrictions does, so the $relay_domains is
useless for sendmail.
Relaying, by definition, occurs only when mail is coming in via SMTP and is
not delivered locally, but re-sent to another server.
When mail is generated
relay_restrictions configuration
> like what $smtpd_relay_restrictions does, so the $relay_domains is
> useless for sendmail.
Relaying, by definition, occurs only when mail is coming in via SMTP and is
not delivered locally, but re-sent to another server.
When mail is generated locally via sendmail a
what $smtpd_relay_restrictions does, so the $relay_domains is useless
for sendmail.
And there is no filter available for sendmail either
(https://www.postfix.org/FILTER_README.html).
How to reject the unwanted destination domains when users use the
sendmail command
Am Montag, dem 10.07.2023 um 09:39 -0400 schrieb Viktor Dukhovni via
Postfix-users:
> On Mon, Jul 10, 2023 at 03:24:54PM +0200, Robert Senger wrote:
>
> > Hey, that was me! My full given name *is* Robert'); DROP ...
> >
> > CONFDIR=/etc/postfix
> > POSTMAP=/usr/sbin/postmap
> > LOCAL_VIRTUAL_USER
On Mon, Jul 10, 2023 at 03:24:54PM +0200, Robert Senger wrote:
> Hey, that was me! My full given name *is* Robert'); DROP ...
>
> CONFDIR=/etc/postfix
> POSTMAP=/usr/sbin/postmap
> LOCAL_VIRTUAL_USERS=mysql:${CONFDIR}/virtual_mailboxes.mysql.cf
>
> recipient=$(printf '%s' "$2" | sed 's/[<>]//g')
Am Montag, dem 10.07.2023 um 08:52 -0400 schrieb Viktor Dukhovni via
Postfix-users:
> > On 10 Jul 2023, at 5:50 am, Matus UHLAR - fantomas via Postfix-
> > users wrote:
> >
> > > > #!/bin/bash
> > > > user=`echo "$2" | sed 's/[<>]//g'`
> > > > ret=`echo "select destination from virtual_aliases wh
> On 10 Jul 2023, at 5:50 am, Matus UHLAR - fantomas via Postfix-users
> wrote:
>
>>> #!/bin/bash
>>> user=`echo "$2" | sed 's/[<>]//g'`
>>> ret=`echo "select destination from virtual_aliases where
>>> source=\"$user\";" | /usr/bin/mysql -upostfix -psecretpassword
>>> mailserver | tail -n 1`
>>>
onnerstag, dem 29.06.2023 um 17:21 +0200 schrieb Robert Senger via
Postfix-users:
I am running Postfix 3.4.23 on Debian 10.13 Buster, with SpamAssassin
4.0.0 and spamass-milter 0.4.0-2 for spam detection.
This is my "sendmail -bv" substitute:
#!/bin/bash
user=`echo "$2" | sed &#x
tabases for every alias or evan wildcard address, which is not
> desired.
>
> Now, I've figured out that spamass-milter has an option to run
> "sendmail -bv" command, to expands aliases to the real username, and
> extract the expanded username from the output of that
On Thu, Jun 29, 2023 at 05:21:32PM +0200, Robert Senger via Postfix-users wrote:
Of course, I could write my own "sendmail" script which takes the
virtual_alias,
I was thinking about the same, just utilising postconf and postmap...
On 29.06.23 12:02, Viktor Dukhovni via Postfix-u
Robert Senger via Postfix-users skrev den 2023-06-29 17:21:
...
The point is that spamassassin needs to know the username when
processing an email, to update the correct bayes database. The username
given to spamassassin by spamass-milter is the email address of the
recipient. This is fine, as
name, and creates bayes
> databases for every alias or evan wildcard address, which is not
> desired.
>
> Now, I've figured out that spamass-milter has an option to run
> "sendmail -bv" command, to expands aliases to the real username, and
> extract the expanded user
On Thu, Jun 29, 2023 at 05:21:32PM +0200, Robert Senger via Postfix-users wrote:
> Of course, I could write my own "sendmail" script which takes the
> virtual_alias,
This is possible with care, but not ideal, better would be to find
some way to get the milter to make the
as an option to run
"sendmail -bv" command, to expands aliases to the real username, and
extract the expanded username from the output of that command. Cool ;)
But postfix' "sendmail -bv" command behaves different from the
original. It does not write its results to stdout
As always, very grateful for your clarifications.
El 8/6/23 a las 18:12, Wietse Venema via Postfix-users escribió:
Wietse Venema via Postfix-users:
Victor Rubiella Monfort via Postfix-users:
Hi,
I want to prevent that sendmail milter rejections generates bounces
messages. Reading sendmail
Wietse Venema via Postfix-users:
> Victor Rubiella Monfort via Postfix-users:
> > Hi,
> >
> > I want to prevent that sendmail milter rejections generates bounces
> > messages. Reading sendmail documentation I see "-N" option:
> >
> > echo
Victor Rubiella Monfort via Postfix-users:
> Hi,
>
> I want to prevent that sendmail milter rejections generates bounces
> messages. Reading sendmail documentation I see "-N" option:
>
> echo "HELLO" | sendmail -N 'never' t...@test.es; echo $?
Víctor Rubiella Monfort via Postfix-users skrev den 2023-06-08 14:06:
echo "HELLO" | sendmail -N 'never' t...@test.es; echo $?
-N parameter only controls DSN, it does not do REJECT or BOUNCES
sendmail -f t...@test.es -bv t...@test.es -N never
more funny results
hopef
Hi,
I want to prevent that sendmail milter rejections generates bounces
messages. Reading sendmail documentation I see "-N" option:
echo "HELLO" | sendmail -N 'never' t...@test.es; echo $?
0
Jun 8 13:51:30 server.test postfix/cleanup[597560]: 077616620F:
On 2023-01-01 19:54, Wietse Venema wrote:
Viktor Dukhovni:
On Sun, Jan 01, 2023 at 05:03:27PM +0100, Jesper Dybdal wrote:
...
(I seem to remember that there was a thread here about a similar subject
some time ago, but I can't find it now.)
Did you mean https://www.postfix.org/postconf.5.ht
On Sun, Jan 01, 2023 at 01:54:12PM -0500, Wietse Venema wrote:
> > > (I seem to remember that there was a thread here about a similar subject
> > > some time ago, but I can't find it now.)
>
> Did you mean https://www.postfix.org/postconf.5.html#local_login_sender_maps
> This is available in Pos
control which envelope sender addresses can be
> > used by which system user by calling sendmail(1)?
>
> No. Unlike the smtpd(8) service with its restriction classes and
> access(5) tables, the postdrop(1) local submission handler has very
> limited access control capabiliti
e
> used by which system user by calling sendmail(1)?
No. Unlike the smtpd(8) service with its restriction classes and
access(5) tables, the postdrop(1) local submission handler has very
limited access control capabilities (just authorized_submit_users, which
you're already using).
Note tha
I use reject_authenticated_sender_login_mismatch to control which
envelope sender addresses SASL clients can use. That works just fine.
Is there a similar way to control which envelope sender addresses can be
used by which system user by calling sendmail(1)?
(I seem to remember that there
On Thu, Aug 11, 2022 at 11:01:52AM +0200, witcher wrote:
> >As to popularity, I use "mutt", which already supports setting the
> >envelope sender based on the "From:" header, passing the desired
> >envelope sender to sendmail(1).
>
> Huh, I didn
There isn't.
Good to know.
As to popularity, I use "mutt", which already supports setting the
envelope sender based on the "From:" header, passing the desired
envelope sender to sendmail(1).
Huh, I didn't know it does that. I've only tried sending wi
On Wed, Aug 10, 2022 at 07:51:52PM +0200, witcher wrote:
> I'm wondering whether there is an option for sendmail to read the
> "From:" field from a mbox file to fill the envelope sender address
> (like you otherwise would with the `-f` command line flag).
There isn
I'm wondering whether there is an option for sendmail to read the
"From:" field from a mbox file to fill the envelope sender address (like
you otherwise would with the `-f` command line flag).
It doesn't seem to be documented (and thus probably not available) in
the man page
James Feeney:
> As described in the original post, setting the inet_interfaces
> parameter to "" results
> in postfix sendmail failing with "fatal: parameter inet_interfaces:
> no local interface found for "
> when postfix is running "inside" a network
James Feeney:
> inet_interfaces - "The network interface addresses that this mail system
> receives mail on."
> proxy_interfaces - "The network interface addresses that this mail system
> receives mail on by way of a proxy or network address translation unit."
It means to say:
inet_interfaces -
On Sat, Jun 18, 2022 at 06:44:55PM -0600, James Feeney wrote:
> Running postfix on Linux in a Network Namespace, and then running
> postfix sendmail from "outside" that Network Namespace, gives an
> error:
>
> postfix/sendmail[606899]: fatal: parameter inet_interfaces: n
On 17/05/21 10:37 pm, Jaroslaw Rafa wrote:
I would disagree that port 465 with TLS-wrapper around SMTP is better than
port 587 with STARTTLS. It's only your personal opinion. Port 587 with
mandatory STARTTLS is in no way less secure than TLS-wrapped port 465.
I used to make that argument (see b
Dnia 17.05.2021 o godz. 21:55:22 Peter pisze:
>
> Port 465 = submissions = best
> Port 587 with mandatory starttls = submission = acceptable
I would disagree that port 465 with TLS-wrapper around SMTP is better than
port 587 with STARTTLS. It's only your personal opinion. Port 587 with
mandatory
On 17/05/21 9:12 pm, Jaroslaw Rafa wrote:
Dnia 17.05.2021 o godz. 08:52:33 Chris Green pisze:
Most mail clients will use sendmail rather than SMTP on port 25 (or
another port) won't they? As I said my postfix works fine for sending
E-Mails from my MUA (mutt) which uses sendmail.
Dnia 17.05.2021 o godz. 08:52:33 Chris Green pisze:
> >
> > Ubuntu desktop should have Thunderbird preinstalled. Why not just try to
> > send mail using a regular mail client?
>
> Most mail clients will use sendmail rather than SMTP on port 25 (or
> another port
On Mon, May 17, 2021 at 09:03:25AM +0200, Jeroen Geilman wrote:
>It was not rejected by mail.gandi.net.
>
>If it was rejected by something beyond that, [1]ch...@zmbc.eu would get
>a bounce notification (DSN).
>
>Postfix is not involved in any way.
>
OK, thanks.
--
Chris Green
try to
> send mail using a regular mail client?
Most mail clients will use sendmail rather than SMTP on port 25 (or
another port) won't they? As I said my postfix works fine for sending
E-Mails from my MUA (mutt) which uses sendmail.
I must say that swaks looks handy though and it's av
Dnia 16.05.2021 o godz. 13:58:22 Bob Proulx pisze:
> Chris Green wrote:
> > I am trying to debug it by connecting directly to port 25 on localhost
> > using telnet and composing mail that way.
>
> I highly recommend "swaks" the Swiss Army Knife SMTP, the all-purpose
> SMTP transaction tester utili
Chris Green wrote:
> I am trying to debug it by connecting directly to port 25 on localhost
> using telnet and composing mail that way.
I highly recommend "swaks" the Swiss Army Knife SMTP, the all-purpose
SMTP transaction tester utility program for generating test emails
using SMTP transactions.
On 2021-05-16 at 12:10:59 UTC-0400 (Sun, 16 May 2021 17:10:59 +0100)
Chris Green
is rumored to have said:
I have postfix running on my xubuntu 21.10 desktop machine and it's
working fine for sending mail from mutt which uses the 'sendmail'
interface.
However I have a script wh
>
>
> I am trying to debug it by connecting directly to port 25 on localhost
> using telnet and composing mail that way. It appears to be sent
> according to the postfix mail.log but it just disappears.
>
It could be that it went to spam because you misused some headers while
sending mail manually
I have postfix running on my xubuntu 21.10 desktop machine and it's
working fine for sending mail from mutt which uses the 'sendmail'
interface.
However I have a script which attempts to send using localhost port 25
and that doesn't appear to work.
I am trying to debug it by
On Thu, Aug 06, 2020 at 03:32:11PM -0400, Bill Cole wrote:
> > A doable, but perhaps non-trivial, programming project would be to
> > start with Apple's Postfix sources, and port that functionality to
> > BSD and/or Linux.
>
> Not very doable, because the trigger was handled by launchd, Apple's
On 6 Aug 2020, at 14:38, Viktor Dukhovni wrote:
A doable, but perhaps non-trivial, programming project would be to
start
with Apple's Postfix sources, and port that functionality to BSD
and/or
Linux.
Not very doable, because the trigger was handled by launchd, Apple's
systemd-like facility.
On Thu, Aug 06, 2020 at 02:38:21PM -0400, Viktor Dukhovni wrote:
> Otherwise, provided max_idle is less than the wakeup timer for "pickup",
> the cost is modest. Postfix idles down to just 3 processes:
Correction, typo, max_idle should be *greater* than the wakeup timer for
pickup.
--
Vikto
On Thu, Aug 06, 2020 at 09:44:24AM +0300, Otto Kekäläinen wrote:
> Is it possible to send email using the Postfix provided
> /usr/sbin/sendmail command on a system where Postfix is installed, but
> not running permanently as a service?
Not the upstream Postfix version signed by Wiets
On Thu, Aug 06, 2020 at 09:44:24AM +0300, Otto Kekäläinen wrote:
> Is it possible to send email using the Postfix provided
> /usr/sbin/sendmail command on a system where Postfix is installed, but
> not running permanently as a service?
Sure, the sendmail command will just deposit the
On 2020-08-06 Otto Kekäläinen wrote:
> Is it possible to send email using the Postfix provided
> /usr/sbin/sendmail command on a system where Postfix is installed,
> but not running permanently as a service?
You could wrap the command in a script that starts and stops the Postfix
ser
YMMW, but I solved this using ssmtp to replace sendmail. According to Arch it
may be poor choice, since it is not maintained
https://wiki.archlinux.org/index.php/SSMTP
Just my 2 cents
Thu, 6 Aug 2020 09:44:24 +0300 skrev Otto Kekäläinen :
> Hello!
>
> Is it possible to send email
Hello!
Is it possible to send email using the Postfix provided
/usr/sbin/sendmail command on a system where Postfix is installed, but
not running permanently as a service?
Background:
I have a resource constrained system where I want to avoid running
excess processes, and it rarely sends email
> On Jul 27, 2020, at 1:18 PM, Viktor Dukhovni
> wrote:
>
>
>> make -f Makefile.init makefiles CCARGS='-DUSE_TLS -I/usr/local/ssl/include \
>> [...]
>> -DDEF_SENDMAIL_PATH=\"/usr/local/sbin\"\
>
> This is not correct, it lists the containing directory, rather than the
> full path to the exec
o CCARGS. Do I need both in the “make makefiles”
> command?
No, just a correct setting for sendmail_path, e.g.
sendmail_path=/usr/local/sbin/sendmail
is enough.
> make -f Makefile.init makefiles CCARGS='-DUSE_TLS -I/usr/local/ssl/include \
> [...]
> -DDEF_SENDMAIL_PATH=\&qu
> On Jul 27, 2020, at 11:05 AM, Larry Stone wrote:
>
> I’m trying to figure out how to tell make {install | upgrade} to install
> sendmail eleswhere? I tried sendmail_path=/usr/local/sbin as well as
> -DDEF_SENDMAIL_PATH and while that changes the default value of
> sendm
I’m trying to figure out how to tell make {install | upgrade} to install
sendmail eleswhere? I tried sendmail_path=/usr/local/sbin as well as
-DDEF_SENDMAIL_PATH and while that changes the default value of sendmail_path,
it still installs in /usr/sbin.
Background: last week, I finally
> No idea. One could equally-well argue for setting it to zero.
Noted.
It was changed here long-ago, guessing for a reason, but I've no current
metrics to convince me, or not, that there's a problem (anymore).
My inclination is to stick with Postfix's 'new(er)' default/standard == 998,
for no
On Mon, Dec 16, 2019, PGNet Dev wrote:
> The Sendmail 'Usenet'/Google Group is a bit of a sewer; cc'ing Claus to see
> if there's any newer comment/clarity as to why Sendmail's still not
> standards-compliant in this.
Please do NOT use my private e-mail addre
PGNet Dev:
> > The limit was still 990 in Sendmail 8.15.
>
> To deal with that in production, is setting value in Postfix to
> == 990 sufficient? recommended?
No idea. One could equally-well argue for setting it to zero.
Wietse
Wietse Venema:
> PGNet Dev:
> > > I don't see any mention of Sendmail in that text.
> >
> > As I said, 'ages ago'. Per a conversation,
> >
> >
> > https://mailing.postfix.users.narkive.com/nhbtm7Fg/smtp-line-length-limit-998
>
> The limit was still 990 in Sendmail 8.15.
To deal with that in production, is setting value in Postfix to == 990
sufficient? recommended?
Does a setting of == 990 (continue to) break any particular
service/functionality?
The Sendmail 'Usenet'/Google Group is a bit of a sewer;
PGNet Dev:
> > I don't see any mention of Sendmail in that text.
>
> As I said, 'ages ago'. Per a conversation,
>
>
> https://mailing.postfix.users.narkive.com/nhbtm7Fg/smtp-line-length-limit-998
>
> It apparently was an issue; I'm asking if it
> I don't see any mention of Sendmail in that text.
As I said, 'ages ago'. Per a conversation,
https://mailing.postfix.users.narkive.com/nhbtm7Fg/smtp-line-length-limit-998
It apparently was an issue; I'm asking if it still is.
of
each line.
Which is consistent with RFC 5321.
> Ages ago, Sendmail added an errant "!", causing overruns -- I think
> that's in part why the prior Postfix value == 990? to accommodate
> 'broken' Sendmail?
Postfix HISTORY says:
20020324
Cleanup
Current default for
http://www.postfix.org/postconf.5.html#smtp_line_length_limit
is == 998, per smtp std.
Ages ago, Sendmail added an errant "!", causing overruns -- I think that's in
part why the prior Postfix value == 990? to accommodate 'broken' Sendmail?
T
warding to an email address I don't host).
3. Postforward reinjects the email with sendmail, now with a return_path of
@srs.example.org.
4. All of this works up to this point, but what I want to do next is send
emails through to a dkim signing program, to sign emails from srs.example.org
s
It seems to work.
Thank you!
Gesendet: Freitag, 22. März 2019 um 16:15 Uhr
Von: "Viktor Dukhovni"
An: "Postfix users"
Betreff: Re: Add Header only if sent via sendmail
> On Mar 22, 2019, at 3:00 AM, lutz.niede...@gmx.net wrote:
>
> But how can I do this?
As n
> On Mar 22, 2019, at 3:00 AM, lutz.niede...@gmx.net wrote:
>
> But how can I do this?
As noted below.
> In master.cf I add a service eg called "mycleanup" with
> mycleanup unix ... cleanup -o header_checks=file
Well, not "=file" but "=pcre:file" or similar.
> Essentially a renamed copy of the
don't need to touch smtpd if I don't mind getting the IP address via client_restrictions, too.
Is that correct? Did I miss something?
-lutzn
Gesendet: Freitag, 22. März 2019 um 06:30 Uhr
Von: "Viktor Dukhovni"
An: "Postfix users"
Betreff: Re: Add Header only if
> On Mar 21, 2019, at 11:55 PM, lutz.niede...@gmx.net wrote:
>
> I am looking for a simple way to add a header if and only if mail is sent
> locally via sendmail (mail/mailx) command.
> We need to know who/what sent an email. We already get the client's IP
> address
Hello,
I am looking for a simple way to add a header if and only if mail is sent locally via sendmail (mail/mailx) command.
We need to know who/what sent an email. We already get the client's IP address if sent using smtp via smtpd_client_restrictions, but if it is not sent via smtp I
ent.
>
> As I scrolled through the docs - seems there is no config option to
> override this behaviour like "ignore loopback" - so it seems this check
> is hardcoded in the source.
>
> I also tried mini_sendmail - but as you have to override sendmail
> yourself - it
ems this check
is hardcoded in the source.
I also tried mini_sendmail - but as you have to override sendmail
yourself - it gets overridden by package update - but I guess this issue
can be said about just any package-based distribution.
Matt
Am 25.01.2019 um 01:05 schrieb Viktor Dukhovni:
1 - 100 of 515 matches
Mail list logo
