On 1/1/24 11:29 AM, Wietse Venema via Postfix-users wrote:
First, verify that your sender_dependent_default_transport_maps is not
pre-empted by a higher-precedence mechanism:
Thanks Wietse,
That was the clue I needed. I thought I had commented out gmail from the
transport file. Well I did,
I have a long time running Postfix server (version 2.10) where I need to send
from specific IP addresses for some virtual domains.
I have it working, sort of. If I send email from this server to another server
running postfix, it all seems to work. The sent email shows the transport
On 4/15/22 10:15 AM, Matus UHLAR - fantomas wrote:
On 14.04.22 08:26, Emmett Culley wrote:
I recently changed the host name of one of the servers from one domain I am
hosting to another of the domains the server is serving.
Upon verifying the server I noticed that the Received: headers
On 4/14/22 9:58 AM, Wietse Venema wrote:
Emmett Culley:
Is there anything I can do to specify that the Recieved: headers
have the "correct" domain name depending on what domain is sending
an email (From:)?
The Received: headers contain the value of the "myhostname&
On 4/14/22 8:38 AM, Shawn Heisey wrote:
On 4/14/22 09:26, Emmett Culley wrote:
I would include the output of postconf, but it is very large and I don't know how to narrow it down to what is needed to help resolve this issue.
Try "postconf -n". This should only sho
I run a couple of mail servers using postfix, currently at version 2.10.1.
They are set up to send and receive email for multiple virtual domains and have
been doing that beautifully for years.
I recently changed the host name of one of the servers from one domain I am
hosting to another of
On 2/24/21 12:40 PM, Dirk Stöcker wrote:
On Wed, 24 Feb 2021, Wietse Venema wrote:
Postfix version 3.6 deprecates terminology that implies white is
better than black. Instead, Postfix prefers 'allowlist', 'denylist',
and variations on those words.
We had a late start, but it seems Newspeak
On 04/15/2018 01:31 PM, Viktor Dukhovni wrote:
> On Sun, Apr 15, 2018 at 01:26:54PM -0700, Emmett Culley wrote:
>
>> smtpd_sasl_path = smptd
>>
>> -- listing of /etc/sasl2 --
>> -rw-rw-r--1 root root 49 Apr 15 07:10 smtpd.conf
>>
>> -- content of
I am not able to get postfix to authenticate on port 465 or 587 to allow account holders to relay via this server.
Everything else works. That is, we can use the account name and password to log into Cyrus IMAP, though I know it
isn't postfix that makes that connection, it does mean that SASL
On 12/14/2017 10:53 AM, Viktor Dukhovni wrote:
>
>
>> On Dec 14, 2017, at 1:44 PM, Emmett Culley <lst_man...@webengineer.com>
>> wrote:
>>
>> Recipient address rejected: unverified address: Address verification in
>> progress;
>
> http://
Sorry, I miss typed virtual_mailbox_domains
Should have been virtual_mailbox_domains =
mysql:/etc/postfix/mysql-mydestination.cf
Emmett
On 12/14/2017 10:44 AM, Emmett Culley wrote:
> Recently I've been working on upgrading to Postfix 3 and a rewrite of
> web-cyradm, and so have been st
Recently I've been working on upgrading to Postfix 3 and a rewrite of
web-cyradm, and so have been studying the Postfix docs. It seems to me that I
have been doing virtual mailboxes wrong, even though it has been working for
years.
For a long time I've been managing virtual domains using
I am seeing that some email appears in the the intended receivers mail box and
some don't.
The ones that don't get delivered to the remote mail server have log entries
like this:
Mar 18 03:15:02 aoakley postfix/smtp[1714]: 6835847611D:
to=ksome...@domain1.com,
On 12/10/2009 11:37 AM, Victor Duchovni wrote:
On Thu, Dec 10, 2009 at 11:12:36AM -0800, Emmett Culley wrote:
It seems like understanding where the delay=86457
and delays=86457/0/0.36/0.18 come from would probably help me to
understand the 24 delay.
Not really. The message took 1 day
On 11/30/2009 10:48 AM, Victor Duchovni wrote:
On Mon, Nov 30, 2009 at 10:35:02AM -0800, Emmett Culley wrote:
It seems like understanding where the delay=86457
and delays=86457/0/0.36/0.18 come from would probably help me to
understand the 24 delay.
Not really. The message took 1 day
On 11/29/2009 03:27 PM, Wietse Venema wrote:
Emmett Culley:
For some months I've been noticing on multiple servers that mail
from a cron job defined in the root's crontab takes 24 hours to
get to it's destination. It finally bugged me enough to have me
take a look for the reason
For some months I've been noticing on multiple servers that mail from a cron
job defined in the root's crontab takes 24 hours to get to it's destination.
It finally bugged me enough to have me take a look for the reason. This is
what I found in the maillog for each day:
Nov 29 03:15:58 den1
17 matches
Mail list logo
