On 28.02.24 21:31, Scott Techlist via Postfix-users wrote:
As I understand from your explanation, if I keep my
parent_domain_matches_subdomains = smtpd_access_maps
Then the preceding dot format is moot/not needed. Only
outbound.protection.outlook.com OK
I recommend keeping pare
Noel:
As I understand from your explanation, if I keep my
parent_domain_matches_subdomains = smtpd_access_maps
Then the preceding dot format is moot/not needed. Only
outbound.protection.outlook.com OK
Check.
>The reason it doesn't work is you're confusing sender and client.
In
>>Depending on whether omain is client or sender or ...
>>
>>...
>>reject_unauth_destination
>>...
>>check_client_access hash:/pathname
>>reject_rbl_client example.com
>>...
>>
>>Or
>>
>>...
>>reject_unauth_destination
>>...
>>check_sender_access hash:/pathna
>> check_sender_access hash:/etc/postfix/sender_checks,
>
>That directive checks the email address which is used in the SMTP MAIL
>FROM command.
>
>I believe you need to use check_client_access to check the verified
>client hostname instead of check_sender_access.
>
>
Bill & Noel, thank you both f
>Scott Techlist via Postfix-users:
>> I need to allow a domain to bypass my RBL checks. I'm doing something
>> wrong, or I'm
>misunderstanding what I'm checking from my logs. I'd be grateful for an
>assist to remedy.
>>
>
>Depending on whether omain is client or sender or ...
>
>...
>re
>I can tell you there is significant spam from that Microsoft IP space. That
>spamcop doesn't have false positives, but rather due to >the sharing of IP
>space, senders that aren't spammers get tarred with the same brush as the
>spammers. I did a grep on the maillog >files and that is a firehos
I can tell you there is significant spam from that Microsoft IP space. That
spamcop doesn't have false positives, but rather due to the sharing of IP
space, senders that aren't spammers get tarred with the same brush as the
spammers. I did a grep on the maillog files and that is a firehose of s
nd.protection.outlook.com'
hash:/etc/postfix/sender_checks
(does not match)
postmap -q 'outbound.protection.outlook.com'
hash:/etc/postfix/sender_checks
OK #(matches)
As documented, postmap is a simple test tool and does not do any
automatic parent or
directive checks the email address which is used in the SMTP MAIL
FROM command.
I believe you need to use check_client_access to check the verified
client hostname instead of check_sender_access.
I need to let mail from outbound.protection.outlook.com, and bypass my
RBL checks.
That subdomain
Scott Techlist via Postfix-users:
> I need to allow a domain to bypass my RBL checks. I'm doing something wrong,
> or I'm misunderstanding what I'm checking from my logs. I'd be grateful for
> an assist to remedy.
>
Depending on whether omain is client or sender or ...
...
reject_una
I need to allow a domain to bypass my RBL checks. I'm doing something wrong,
or I'm misunderstanding what I'm checking from my logs. I'd be grateful for an
assist to remedy.
This box is an old postfix install Postfix version 2.2.10. (I know, working on
migrating)
main.cf: (full postcon
On Sun, Apr 30, 2023 at 01:33:13AM +0100, Allen Coates via Postfix-users wrote:
> Any ideas on the opposite - i.e. WITHOUT a domain?
>
> I sometimes receive messages from "u...@co.uk"...
With eTLD (effective TLD) domains that have neither address nor MX
records the
reject_unknown_sender_dom
On 28/04/2023 14:59, Gerd Hoerst via Postfix-users wrote:
> Hi !
>
> question 1st : is it a good idea to reject any email which is not sent from a
> domain (means sen...@domain.tld) any
> other like sen...@sub.domain.tld or sub.sub.domain.tld is rejected ?
Any ideas on the opposite - i.e. WITH
On Fri, Apr 28, 2023 at 06:38:04PM +0200, Jaroslaw Rafa via Postfix-users wrote:
> Also take into account that many countries use two-level domain registration
> scheme ...
In Japan, 3rd-level public suffixes are quite common, taking the form:
...jp.
For example:
hospital.hekinan.aichi.jp.
April 29, 2023 at 12:38 AM, "Jaroslaw Rafa via Postfix-users"
wrote:
>
> Dnia 28.04.2023 o godz. 15:59:53 Gerd Hoerst via Postfix-users pisze:
>
> >
> > question 1st : is it a good idea to reject any email which is not
> > sent from a domain (means sen...@domain.tld) any other like
> > se
Dnia 28.04.2023 o godz. 15:59:53 Gerd Hoerst via Postfix-users pisze:
>
> question 1st : is it a good idea to reject any email which is not
> sent from a domain (means sen...@domain.tld) any other like
> sen...@sub.domain.tld or sub.sub.domain.tld is rejected ?
As others have said, it's a total
On 2023-04-28 at 09:59:53 UTC-0400 (Fri, 28 Apr 2023 15:59:53 +0200)
Gerd Hoerst via Postfix-users
is rumored to have said:
Hi !
question 1st : is it a good idea to reject any email which is not sent
from a domain (means sen...@domain.tld) any other like
sen...@sub.domain.tld or sub.sub.dom
> question 1st : is it a good idea to reject any email which is not sent from a
> domain (means sen...@domain.tld) any other like sen...@sub.domain.tld or
> sub.sub.domain.tld is rejected ?
Generally, no, because you will reject legitimate domains
that just look like subdomains, e.g. *.co.uk, *
Gerd Hoerst:
> question 1st : is it a good idea to reject any email which is not sent from a
> domain (means sen...@domain.tld) any other like sen...@sub.domain.tld or
> sub.sub.domain.tld is rejected ?
>
> at least i tried with header checks in pcre
>
> /^From:\.*@.*\.*\.*/ DISCARD NO SUBD
INFO to log what matches, then if you're happy
with the results and feeling particularly reckless, move to REJECT.
i have several anti spam feature enabled but i get still some
messages which are coming from subdomains or sub sub domains
I've seen no evidence that the presence of a
Hi !
question 1st : is it a good idea to reject any email which is not sent
from a domain (means sen...@domain.tld) any other like
sen...@sub.domain.tld or sub.sub.domain.tld is rejected ?
at least i tried with header checks in pcre
/^From:\.*@.*\.*\.*/ DISCARD NO SUBDOMAINS
but this se
Em 30/09/2021 11:46, Markus Schönhaber escreveu:
30.09.21, 16:29 +0200, Marcio Merlone:
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
30.09.21, 16:29 +0200, Marcio Merlone:
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
on f...@sub.example.tld (my on-premise mail serve
Hi,
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
on f...@sub.example.tld (my on-premise mail server) using some bcc trick.
rel
okup key is
the full address including the localpart. So the correct
PCRE pattern for a single ldh-label subdomain is:
/@[a-z\d](?:[-]+[a-z\d]+)*\.example\.com$/ transport:nexthop
--
Viktor.
On 3/23/2021 8:35 AM, Marc Risse wrote:
Hello everyone,
will ".domain.com" match "b...@sub2.sub1.domain.com" or only
"b...@sub1.domain.com" in transport maps?
"parent_domain_matches_subdomains" is not set and I don't want it to
match all subdomains on all levels.
Best
Marc
To control
t; With an indexed table (for example, hash: or btree:), .domain.com
> > will not match any email address, and it will match every subdomain.
> >
> > If you want finer control, use pcre maps. There, the query
> > string is always the complete email address.
> >
> >
ail address, and it will match every subdomain.
If you want finer control, use pcre maps. There, the query
string is always the complete email address.
Wietse
Hello Wietse,
thank you for your reply. To be clear: .domain.com matches
sub2.sub1.domain.com on hashed transport maps?
Thanks
Marc
Marc Risse:
> Hello everyone,
>
> will ".domain.com" match "b...@sub2.sub1.domain.com" or only
> "b...@sub1.domain.com" in transport maps?
With an indexed table (for example, hash: or btree:), .domain.com
will not match any email address, and it will
Hello everyone,
will ".domain.com" match "b...@sub2.sub1.domain.com" or only
"b...@sub1.domain.com" in transport maps?
"parent_domain_matches_subdomains" is not set and I don't want it to
match all subdomains on all levels.
Best
Marc
Hello everyone,
will ".domain.com" match "b...@sub2.sub1.domain.com" or only
"b...@sub1.domain.com" in transport maps?
"parent_domain_matches_subdomains" is not set and I don't want it to
match all subdomains on all levels.
Best
Marc
smime.p7s
Description: S/MIME Cryptographic Signature
I'm setting up a new server with the goal of using letsencrypt versus my self
signed cert. (I'm also going to try those SpamAssassin alternatives that
require less RAM.) So I will run two VPS for a period as I debug the new server.
That said, is there any way to implement email going to both ex
On Tuesday, March 29, 2016, Wietse Venema wrote:
> Michael Fischer:
> > On Tue, Mar 29, 2016 at 9:40 AM, Viktor Dukhovni
> > > wrote:
> >
> > > There are a few features for which the semantics of p_d_m_s are
> > > explained in more detail, for example:
> >
> > > http://www.postfix.org/access.5.h
Michael Fischer:
> On Tue, Mar 29, 2016 at 9:40 AM, Viktor Dukhovni
> wrote:
>
> > There are a few features for which the semantics of p_d_m_s are
> > explained in more detail, for example:
>
> > http://www.postfix.org/access.5.html
> > http://www.postfix.org/transport.5.html
>
> OK, thanks. I
On Tue, Mar 29, 2016 at 9:46 AM, Michael Fischer wrote:
> On Tue, Mar 29, 2016 at 9:40 AM, Viktor Dukhovni
> wrote:
>
>> There are a few features for which the semantics of p_d_m_s are
>> explained in more detail, for example:
>
>> http://www.postfix.org/access.5.html
>> http://www.postfix.org/tr
On Tue, Mar 29, 2016 at 9:40 AM, Viktor Dukhovni
wrote:
> There are a few features for which the semantics of p_d_m_s are
> explained in more detail, for example:
> http://www.postfix.org/access.5.html
> http://www.postfix.org/transport.5.html
OK, thanks. It'd be useful, I think, to link the e
only documentation I know of is
> postconf.5.html#parent_domain_matches_subdomains and
> postconf.5.html#relay_domains :
>
> relay_domains (default: $mydestination)
>
> What destination domains (and subdomains thereof) this system
> will rel
tconf.5.html#parent_domain_matches_subdomains and
postconf.5.html#relay_domains :
relay_domains (default: $mydestination)
What destination domains (and subdomains thereof) this system
will relay mail to. Subdomain matching is controlled with the
parent_domain_matches_subdomains parameter.
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tue, Mar 29, 2016 at 8:36 AM, /dev/rob0 wrote:
>> According to my reading of the documentation, if $relay_domains
>> includes ".example.com", it should relay mail for "sub.example.com",
>> regardless of whether or not "relay_domains" is included in
>> $parent_domain_matches_subdomains.
>
> Thi
standing is that inclusion of (for example) "relay_domains"
> in $parent_domain_matches_subdomains would treat "example.com" as
> ".example.com" for matching purposes, but would otherwise be a
> no-op if the subdomain is already dot-prefixed.
Nope. If you
r "sub.example.com",
regardless of whether or not "relay_domains" is included in
$parent_domain_matches_subdomains.
My understanding is that inclusion of (for example) "relay_domains" in
$parent_domain_matches_subdomains would treat "example.com" as
".example
ead of requiring ".domain.name"
for subdomain matches). Planning for future backwards
compatibility :-) File: global/match_parent_style.c.
Since 2001, the default has been:
/*
* Backwards compatibility: foo.com matches itself and names below foo.com
In Postfix 2.10, the default value of
$parent_domain_matches_subdomains changed from:
parent_domain_matches_subdomains =
debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_authorized_clients,smtpd_access_maps
To:
parent_domain_matches_subdomains =
debug_peer_list,fast_
In message <20160201080958.9bede332...@english-breakfast.cloud9.net>
Curtis Villamizar writes:
> > Aliasing root on null-clients is explained in:
> >
> >http://www.postfix.org/MULTI_INSTANCE_README.html#split
>
> OK. This
Oops.
Was going to write "This doesn't help".
The reason is that
In message <2a0d3251-10a1-4903-8689-2d190e144...@dukhovni.org>
Viktor Dukhovni writes:
> > On Jan 30, 2016, at 8:03 PM, Curtis Villamizar
> > wrote:
> >
> > I'm asking a little advice.
> >
> > On most of my hosts mail is generated for root and then canonicaled to
> > root@fqdn and is relayed
> On Jan 30, 2016, at 8:03 PM, Curtis Villamizar
> wrote:
>
> I'm asking a little advice.
>
> On most of my hosts mail is generated for root and then canonicaled to
> root@fqdn and is relayed to the MSA on another host. This is by
> design.
>
> relayhost = msa-fqdn
>
> There is an alias on
I'm asking a little advice.
On most of my hosts mail is generated for root and then canonicaled to
root@fqdn and is relayed to the MSA on another host. This is by
design.
relayhost = msa-fqdn
There is an alias on the originating host for root but it doesn't seem
to expand there. If that coul
On 4/1/15 11:40 AM, Noel Jones wrote:
On 4/1/2015 6:43 AM, Hank Beatty wrote:
Thank you.
I implemented this and mail sourced externally comes in, postfix
tries to relay and loops back on itself. Mail sourced from the
server seems to be routing correctly. I've tried updating /etc/hosts
and chang
On 4/1/2015 6:43 AM, Hank Beatty wrote:
> Thank you.
>
> I implemented this and mail sourced externally comes in, postfix
> tries to relay and loops back on itself. Mail sourced from the
> server seems to be routing correctly. I've tried updating /etc/hosts
> and changing the /etc/postfix/transpor
Thank you.
I implemented this and mail sourced externally comes in, postfix tries
to relay and loops back on itself. Mail sourced from the server seems to
be routing correctly. I've tried updating /etc/hosts and changing the
/etc/postfix/transport to an IP. The issue still persists.
Any idea
On 3/31/2015 5:25 PM, Hank Beatty wrote:
> Hello,
>
> I'm new to postfix and I inherited a server that was already
> configured with the below. I need to relay subdomain.ni.example.com
> to another server. I looked at the documentation and it seemed
> pretty straight forward
Yes, add the domain
Hello,
I'm new to postfix and I inherited a server that was already configured
with the below. I need to relay subdomain.ni.example.com to another
server. I looked at the documentation and it seemed pretty straight
forward until I ran into the fact that the ni.example.com was already
being re
Not since you pointed it out.
Thanks Viktor works fine now.
On 04/06/2014, at 12:17 PM, Viktor Dukhovni wrote:
On Wed, Jun 04, 2014 at 12:16:08PM +1000, Andrew Stuart wrote:
transport file contains:
* smtp:mail.power.com
And you're surprised why everything is going via smtp to
On Wed, Jun 04, 2014 at 12:16:08PM +1000, Andrew Stuart wrote:
> transport file contains:
>
> * smtp:mail.power.com
And you're surprised why everything is going via smtp to mail.power.com?
--
Viktor.
transport file contains:
* smtp:mail.power.com
On 04/06/2014, at 11:59 AM, Viktor Dukhovni wrote:
On Wed, Jun 04, 2014 at 11:52:59AM +1000, Andrew Stuart wrote:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
home_mailbox = Maildir/
Only applicable with local(
On Wed, Jun 04, 2014 at 11:52:59AM +1000, Andrew Stuart wrote:
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> home_mailbox = Maildir/
Only applicable with local(8) delivery, but you have
local_transport = virtual, so unless you have explicit
transport entries selecting "l
postconf -n output
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
home_mailbox = Maildir/
inet_interfaces = all
local_recipient_maps = $virtual_mailbox_maps
local_transport = virtual
mailbox_size_limit = 0
messa
On Wed, Jun 04, 2014 at 11:39:56AM +1000, Andrew Stuart wrote:
> I want mail to example.org to be delivered to the local virtual mailboxes. I
> want mail to in.example.org to be relayed to mail.power.com.
>
> The configuration below is relaying all mail to mail.power.com.
Try "postconf -n" instea
I want mail to example.org to be delivered to the local virtual
mailboxes. I want mail to in.example.org to be relayed to
mail.power.com.
The configuration below is relaying all mail to mail.power.com.
Can someone please suggest what I need to do to fix?
thanks
# See /usr/share/postf
Am 25.05.2012 21:08, schrieb Carlos R Laguna:
> Hello everyone i am facing a big mess here i had my MTA whith my own
> user but this server is also a relay server for several subdomain the problem
> is that my own politic are been
> aplied to user that arent my, any clue why this
On 5/25/2012 2:08 PM, Carlos R Laguna wrote:
> Hello everyone i am facing a big mess here i had my MTA whith my own
> user but this server is also a relay server for several subdomain
> the problem is that my own politic are been aplied to user that
> arent my, any clue why this
Hello everyone i am facing a big mess here i had my MTA whith my own
user but this server is also a relay server for several subdomain the
problem is that my own politic are been aplied to user that arent my,
any clue why this is happening . Regards
On Tue, Jul 19, 2011 at 06:45:46PM -0500, Jay G. Scott wrote:
> Management wants email to
> user@ .arlut.utexas.edu
> will be treated as though it had been addressed to
> u...@arlut.utexas.edu
Regardless of the MTA, this requires at the very least a wild-card MX
record, do you have t
like management wants.
I think you'll need to set
# main.cf
mydomain = arlut.utexas.edu
so that append_dot_mydomain can add the right parent to unqualified
addresses.
and probably also:
local_header_rewrite_clients = static:all
unless all the clients are already listed in mynetworks.
Then,
Thanks to all who have tried to help me so far.
I'm sorry to be such a pest. I've tried a number of things and still
can't get it.
Management wants email to
user@ .arlut.utexas.edu
will be treated as though it had been addressed to
u...@arlut.utexas.edu
(sendmail can do this.)
Hi All,
I would like have suggestion for changing subdomain (belongs to ISP) to own
domain, the scenario as below.
Presently we have subdomain from ISP ( @xxx.isp.net)
email id : ram...@xxx.isp.net
ISP charges huge amount,thou others ISP charges less. so we have planned to
migrate to our own
Thanks Jeroen and Noel for suggestions.
I will go through postfix url, will update you.
Thanks,
Ramesh.
--- On Wed, 30/6/10, Jeroen Geilman wrote:
From: Jeroen Geilman
Subject: Re: Subdomain
To: postfix-users@postfix.org
Date: Wednesday, 30 June, 2010, 2:58 AM
On 29-6-2010 16:28, Noel
On 29-6-2010 16:28, Noel Jones wrote:
On 6/29/2010 2:47 AM, ramesh wrote:
Hi,
I would like to have suggestion, presently we have internet service&
subdomain from ISP.
Ex: Domain: @providerdomain.com
Subdomain: @mydomain.providerdomain.com
Email I
On 6/29/2010 2:47 AM, ramesh wrote:
Hi,
I would like to have suggestion, presently we have internet service& subdomain
from ISP.
Ex: Domain: @providerdomain.com
Subdomain: @mydomain.providerdomain.com
Email Id: m...@mydomain.providerdomain.com
This ISP charging more inte
Hi,
I would like to have suggestion, presently we have internet service & subdomain
from ISP.
Ex: Domain: @providerdomain.com
Subdomain: @mydomain.providerdomain.com
Email Id: m...@mydomain.providerdomain.com
This ISP charging more internet charges comparing to other ISP
On Wednesday, October 21, 2009 at 02:06 CEST,
Norman Noah wrote:
> > Do you want to change the header addresses or just the envelope? In
> > the former case use canonical rewriting, and in the latter case use
> > virtual rewriting. See ADDRESS_REWRIIING_README.
> >
> > You probably don't nee
>
> Do you want to change the header addresses or just the envelope? In the
> former case use canonical rewriting, and in the latter case use virtual
> rewriting. See ADDRESS_REWRIIING_README.
>
> You probably don't need to use the transport table, but it depends on
> your setup.
>
What about /etc
On Tuesday, October 20, 2009 at 21:53 CEST,
Daniel L'Hommedieu wrote:
> I've been trying to understand the ADDRESS_REWRITING_README and
> haven't ever figured it out. Part of the problem is that I don't
> understand the terminology that is in use (e.g., "header address" and
> "envelope addr
On Oct 20, 2009, at 15:45, Magnus Bäck wrote:
On Tuesday, October 20, 2009 at 11:32 CEST,
Norman Noah wrote:
I'm quite new to Postfix. Can anybody show me an example how to
rewrite recepient address ?
Old email server u...@abc.company.com
new email server u...@xyz.company.com
Where shoul
On Tuesday, October 20, 2009 at 11:32 CEST,
Norman Noah wrote:
> I'm quite new to Postfix. Can anybody show me an example how to
> rewrite recepient address ?
>
> Old email server u...@abc.company.com
> new email server u...@xyz.company.com
>
> Where should i change in transport_maps, virt
I think you should just view
/etc/postfix/generic
-Original Message-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Norman Noah
Sent: Tuesday, October 20, 2009 6:32 PM
To: postfix-users@postfix.org
Subject: Rewriting Recepient Subdomain Email
Hi to all,
I'm quite new to Postfix. Can anybody show me an example how to
rewrite recepient address ?
Old email server u...@abc.company.com
new email server u...@xyz.company.com
Where should i change in transport_maps, virtual_aliasing?
Can u show me the example to change ?
On Mon, Dec 22, 2008 at 02:53:37PM -0500, Munroe Sollog wrote:
> While that gets me what I am looking for, it is avoiding the
> functionality that is documented, regarding subdomain matching. When I
> fire up a new server on that domain all I want to do is point all mail
> to be
While that gets me what I am looking for, it is avoiding the
functionality that is documented, regarding subdomain matching. When I
fire up a new server on that domain all I want to do is point all mail
to be forwarded to krypton. I have something like nullmailer or ssmtp
installed on the
Munroe Sollog:
> I will try to be as verbose as possible. I have been working with a
> few people in IRC and can't seem to get the functionality wanted. I
> have half a dozen servers, all with hostnames on a fake domain. I
> want mail bound for r...@hostname to be forwarded to a central
> locati
On Mon, Dec 22, 2008 at 02:03:44PM -0500, Munroe Sollog wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I will try to be as verbose as possible. I have been working with a
> few people in IRC and can't seem to get the functionality wanted. I
> have half a dozen servers, all with ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I will try to be as verbose as possible. I have been working with a
few people in IRC and can't seem to get the functionality wanted. I
have half a dozen servers, all with hostnames on a fake domain. I
want mail bound for r...@hostname to be forward
Mark A. Olbert a écrit :
> Log info:
>
> Dec 8 07:03:23 wiggle_butt postfix/pickup[13057]: 132802741F3: uid=0
> from=
> Dec 8 07:03:23 wiggle_butt postfix/cleanup[13064]: 132802741F3:
> message-id=<[EMAIL PROTECTED]>
> Dec 8 07:03:23 wiggle_butt postfix/qmgr[13058]: 132802741F3: from=<[EMAIL
to see life as it is and
not as it should be."
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dario "subbia"
Cavallaro
Sent: Monday, December 08, 2008 7:24 AM
To: mouss
Cc: postfix-users@postfix.org
Subject: Re: Info on Filtering Mail based
mouss ha scritto:
can you show the contents of transport_maps?
And the content of alias map? As far as I can remember I had a similar
error and IU had made two mistakes:
1) listed in transport the domain and the destination;
2) no alias set in aliases;
And last but not least, there was no o
ma.comlocal:
localhostlocal:
# put in to support mailman
list.arcabama.commailman:
- Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mouss
Sent: Sunday, December 07, 2008 11:30 PM
To: postfix-users@postfix.org
Subject: Re: Info
Mark A. Olbert a écrit :
> Sorry about the line endings. Let me try again:
>
> Error message:
>
> [EMAIL PROTECTED]:/etc/postfix# mailq
> -Queue ID- --Size-- Arrival Time -Sender/Recipient---
> 140DC2741FE 459 Sun Dec 7 17:57:07 [EMAIL PROTECTED]
> (host 127.0.0.1[127.0.0.1] sa
ddest of all - -to see life as it is and
not as it should be."
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark A. Olbert
Sent: Sunday, December 07, 2008 4:35 PM
To: postfix-users@postfix.org
Subject: RE: Info on Filtering Mail based on subdo
s and
not as it should be."
-Original Message-
From: mouss [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 07, 2008 4:56 PM
To: Mark A. Olbert
Cc: postfix-users@postfix.org
Subject: Re: Info on Filtering Mail based on subdomain
Mark A. Olbert a écrit :
> That almost makes sens
Mark A. Olbert a écrit :
> That almost makes sense, even in my ignorant state. Please bear with me.
>
> I'm pretty sure I've overridden local because I use maia mailguard, which
> re-injects email into the mail processing queue after running it through
> amavisd/spamassassin. Here are the additi
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mouss
Sent: Sunday, December 07, 2008 4:12 PM
To: postfix-users@postfix.org
Subject: Re: Info on Filtering Mail based on subdomain
Mark A. Olbert a écrit :
> I recently installed Exchange as my mail server, with postfix on a linux box
> servi
reviously, when mail delivery took place on my linux box with postfix
> it "just worked".
>
> I think what I need to do is set postfix to distinguish between mail sent to
> my domain (e.g., [EMAIL PROTECTED]) and mail sent to a subdomain used only
> for mailman lists (
x box with postfix
it "just worked".
I think what I need to do is set postfix to distinguish between mail sent to my
domain (e.g., [EMAIL PROTECTED]) and mail sent to a subdomain used only for
mailman lists (e.g., [EMAIL PROTECTED]), and use a different final delivery
mechanism for each
93 matches
Mail list logo
