On 22/05/22 17:42, Jeremy Hansen wrote:
So what am I breaking by not having localhost defined in mynetworks.
I tested typical mail and it still delivers…. Hmm.
Hi Jeremy.
Removing localhost from mynetworks means that if any local process sent
emails through this MTA using SMTP to 127.x.x.x,
Took out localhost references from mynetworks on the ciphermail host and now
it’s doing what I think I originally expected:
May 21 22:38:17 cmx01.la1.blah.com postfix/smtpd[322660]: NOQUEUE: reject: RCPT
from localhost[127.0.0.1]: 554 5.7.1
: Relay access denied;
from= to=
proto=ESMTP helo=
> On May 21, 2022, at 10:06 PM, Nick Tait wrote:
>
> On 21/05/22 19:09, Jeremy Hansen wrote:
>> Two MTAs, one is running Ciphermail. The ciphermail host relays mail to the
>> “permanent home” MTA where mail gets delivered to users and dovecot runs for
>> retrieval of mail. The hosts are int
> On May 21, 2022, at 4:26 PM, Wietse Venema wrote:
>
> Yes, you ave a mailer loop.
>
> mx1 Receive 7B34152BBDB (2326 bytes) from macbook
> mx1 Deliver 7B34152BBDB to content filter, receive as B8C5452BBDF (4004
> bytes).
> mx1 Deliver B8C5452BBDF to cmx01 as 4L4tdt0Fk8z2SSLv
>
> cmx01 Recei
> On May 21, 2022, at 10:34 AM, Fred Morris wrote:
>
> On Sat, 21 May 2022, Viktor Dukhovni wrote:
>> You don't have to accept such mail [...]
>>
>> Don't forward mail that for which the input MTA is expected to be the
>> final destination.
>
> Maybe I'm misunderstanding, but my interpretatio
> On May 21, 2022, at 8:03 AM, Viktor Dukhovni
> wrote:
>
> On Sat, May 21, 2022 at 12:09:37AM -0700, Jeremy Hansen wrote:
>
>> What I experience when the port forward is enabled is suddenly
>> “things” out there are attempting to just email random addresses at
>> the AWS instance hostname.
>
On 21/05/22 19:09, Jeremy Hansen wrote:
Two MTAs, one is running Ciphermail. The ciphermail host relays mail
to the “permanent home” MTA where mail gets delivered to users and
dovecot runs for retrieval of mail. The hosts are internal only
hosts. SSH port forwarding is being used to basicall
Yes, you ave a mailer loop.
mx1 Receive 7B34152BBDB (2326 bytes) from macbook
mx1 Deliver 7B34152BBDB to content filter, receive as B8C5452BBDF (4004 bytes).
mx1 Deliver B8C5452BBDF to cmx01 as 4L4tdt0Fk8z2SSLv
cmx01 Receive 4L4tdt0Fk8z2SSLv (4998 bytes) from localhost which was sent to
8.10.12.
post...@ptld.com:
> The problem is dovecot does case-sensitive matching of recipient user to
> folder name.
> user+foo...@example.com would be sorted into the folder "foobar" by LMTP.
> But user+foo...@example.com would report folder "FOOBAR" not found.
>
The SMTP/LMTP client already implements
On Sat, 21 May 2022, Viktor Dukhovni wrote:
You don't have to accept such mail [...]
Don't forward mail that for which the input MTA is expected to be the
final destination.
Maybe I'm misunderstanding, but my interpretation is that the question is
"why are you accepting that mail?" and saying
> On 05-21-2022 11:46 am, Benny Pedersen wrote:
> On 2022-05-21 17:23, post...@ptld.com wrote:
>>> On 05-21-2022 10:30 am, Wietse Venema wrote:
>>> Doesn't mysql support case-insensitive lookup?
>>
>> Yes, and I am not experiencing an issue with postfix lookups.
>>
>> My goal is to have postfix del
On 2022-05-21 17:23, post...@ptld.com wrote:
On 05-21-2022 10:30 am, Wietse Venema wrote:
Doesn't mysql support case-insensitive lookup?
Yes, and I am not experiencing an issue with postfix lookups.
My goal is to have postfix deliver to LMTP lowercase recipient
addresses to overcome a dovecot
>
> On 21 May 2022, at 11:23 am, post...@ptld.com wrote:
>
> My goal is to have postfix deliver to LMTP lowercase recipient addresses to
> overcome a dovecot shortcoming (delimited forwarding to special folders) that
> dovecot doesn't appear interested in fixing.
For each affected recipient no
> On 05-21-2022 10:30 am, Wietse Venema wrote:
> Doesn't mysql support case-insensitive lookup?
Yes, and I am not experiencing an issue with postfix lookups.
My goal is to have postfix deliver to LMTP lowercase recipient addresses to
overcome a dovecot shortcoming (delimited forwarding to specia
On Sat, May 21, 2022 at 12:09:37AM -0700, Jeremy Hansen wrote:
> What I experience when the port forward is enabled is suddenly
> “things” out there are attempting to just email random addresses at
> the AWS instance hostname.
You don't have to accept such mail, or if you, you don't have to forwa
On Sat, May 21, 2022 at 10:07:57AM -0400, post...@ptld.com wrote:
> What is the best option for changing the recipient address case such
> as forcing all to be lowercase?
>
> > All you need is a case folding regexp before your real virtual table.
> >
> > /etc/postfix/main.cf:
> > virtual_maps =
On 2022-05-21 at 03:09:37 UTC-0400 (Sat, 21 May 2022 00:09:37 -0700)
Jeremy Hansen
is rumored to have said:
> Please let me know what other information is useful and I appreciate the
> help. Thank you!
See http://www.postfix.org/DEBUG_README.html#mail
Output of postconf without the "-n" flag i
On 2022-05-21 16:30, Wietse Venema wrote:
Doesn't mysql support case-insensitive lookup?
Search engine query: "mysql case insensitive".
same reason that dovecot have %Lu ?
what if using sqlite3 ?, what if postgresql ?, or other postfix
supported database engines
on the postfix side imho it
On 2022-05-21 16:07, post...@ptld.com wrote:
What is the best option for changing the recipient address case such
as forcing all to be lowercase?
All you need is a case folding regexp before your real virtual table.
/etc/postfix/main.cf:
virtual_maps =
regexp:/etc/postfix/virtual_regexp
mysql:
On 21.05.22 10:07, post...@ptld.com wrote:
What is the best option for changing the recipient address case such as
forcing all to be lowercase?
I think this can be done when receiving mail by postfix by using
canonical_maps, sender_canonical_maps and recipient_canonical_maps.
if you want to
post...@ptld.com:
> What is the best option for changing the recipient address case such as
> forcing all to be lowercase?
>
> > All you need is a case folding regexp before your real virtual table.
> >
> > /etc/postfix/main.cf:
> > virtual_maps =
> > regexp:/etc/postfix/virtual_regexp
> > mysql
What is the best option for changing the recipient address case such as forcing
all to be lowercase?
> All you need is a case folding regexp before your real virtual table.
>
> /etc/postfix/main.cf:
> virtual_maps =
> regexp:/etc/postfix/virtual_regexp
> mysql:/etc/postfix/mysql-virtual.cf
>
>
On Fri, May 20, 2022 at 03:54:36PM -0500, Bryan K. Walton wrote:
> We are trying to do some header checks that block on both the From and
> Return Path header, but that also block some addresses with
> international characters in them. Characters like:
The "Return-Path" header is added during fi
On 2022-05-21 09:09, Jeremy Hansen wrote:
I realize I need to provide better context and information. I’ll
do my best.
thats a good start
The mail configuration is like this, and again, this is just something
that’s already in place and unfortunately it’s not within my
control to make a ton
I realize I need to provide better context and information. I’ll do my best.
The mail configuration is like this, and again, this is just something that’s
already in place and unfortunately it’s not within my control to make a ton of
changes. I don’t think what I’m asking for is impossible and I
25 matches
Mail list logo
