_blacklist_action (default: ignore)"
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ip]
> Is this setup possible with postfix?
I really do not know. I suppose that what you *need* to do can be
done, but since I (and Stan and probably most of the list) don't
understand the high-level goal, I can't help much except to point out
a few obvious problems, as I just did.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
gure your sieve to deliver that header accordingly.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
E.html
http://www.postfix.org/postconf.5.html#smtpd_data_restrictions
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
are using. But that's
wrong, you should do one of the two above.
> (postconf -n output found at http://www.ziskind.us/postconf.out)
You should post that inline. In any case, none of your three NS hosts
are answering queries.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
e is nothing in the [E]SMTP protocol by which a client can
tell a server why it will be unable to deliver that message.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
or Dovecot SASL.
> For more help please follow the Postfix Debug instructions.
http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
(or, as it says, wiki1 for Dovecot 1.x)
http://www.postfix.org/SASL_README.html#server_dovecot
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Saturday 22 October 2011 18:56:18 Jack Fredrikson wrote:
> From: /dev/rob0
> > http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
> > (or, as it says, wiki1 for Dovecot 1.x)
> > http://www.postfix.org/SASL_README.html#server_dovecot
>
> Do I really want to create
;
> Now here you can help me directly. Yes, of course it's supposed to
> be valid. Where should I list the domain? Where should I list the
> user? TIA,
Again: http://www.postfix.org/ADDRESS_CLASS_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
mains but
> reject mails from any other domain.
>
> I'm using postfix 2.7.1 on RedHat 5.7
>
>
> Any ideas?
http://www.postfix.org/RESTRICTION_CLASS_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
x27;re
using helo_access as a whitelist. This is covered in the
SMTPD_ACCESS_README, "dangerous use of smtpd_recipient_restrictions"
section.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ny suggestion are highly
> appreciated. Thanks!
The ESP suggestion was very good. "Doing it right" in the email world
is very difficult. If money is at stake, spend a little of it. It may
end up saving you far more than you spend!
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
l spam is sent using forged sender addresses. If you can find a
better way to manage your whitelist, do. Or better yet, reduce the
need for whitelisting by using only safe restrictions.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ions. Are there newer/better
> RBLs I should be using?
Quality of DNSBL is more important than quality. I have posted my
postscreen rules which are doing a very good job. I'd recommend that
you look that up and consider upgrading if you are pre-2.8.
Also, the Barracuda BRBL is a very nice service, almost on par with
Zen in terms of effectiveness, and has seemed very safe here.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
user-query ::
query = SELECT username FROM mailbox WHERE username='%s'
AND active = '0'
result_format = 'reject %s Mailbox disabled'
Look up the appropriate SMTP code in RFC 5321, and DSN in RFC 3463 if
desired. I think it would be '550 5.2.1
verride, Postfix will use what's in DNS.
As an alternative, you could use split DNS ("view" in BIND terms) for
the backup MX host.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
worry
> guess it wants to send some bounce etc
On the contrary, this is almost always a sign of trouble. Why was a
bounce sent?
Common causes: backscatter, spammer exploit, open relay ...
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
.0/0 REJECT Please use the MX host
Being a bit slow on the draw this morning I see that Charles has
suggested fundamentally the same thing, just done differently.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
gnored
> once the config is fully read.
Furthermore, there are no postconf(5) settings that include the
string, "smptd". Even if formatted correctly, we do count off for
spelling errors!
> I highly suggest running 'postconf -n' and reviewing the results.
And see that the misspelled parameters are not listed.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
lly, you will not be
bitten by mistakes of this nature. There is exactly one person to
accept the "blame" here, if you want to talk about blame. But this
list is not the place for that.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ropriately.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Of course nowadays most of those are failing against
postscreen, so the HELO rejections are rare for me now.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
s discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
nknown[193.83.162.5]: 450 4.7.1 Client host rejected: cannot
> find your reverse hostname, [193.83.162.5]
postconf.5.html#unknown_client_reject_code
postconf.5.html#reject_unknown_client_hostname
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
rely there are
generic sqlite frontends which might meet your needs. I'm just typing
SQL commands in sqlite3(1) in a shell.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Please stop top-posting. Thank you.
On Wednesday 16 November 2011 08:43:49 Amira Othman wrote:
> How can I separate logs of the instances to be different files?
You asked this last week, on Thursday. Brian and I answered you.
--
Offlist mail to this address is discarded unless
&q
), one for each line in body_checks(5).
If you really think this is worth pursuing, you should consider either
content filtering (inefficient, not safe) or a different MTA.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tion stage unto
itself.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
disk to solve?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
rules. And getting all angry about what rules they choose is nothing
short of STUPID, as is the defensive reaction over being criticized
for the choices you have made.
Take it off list.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
> unknown_local_recipient_reject_code = 550
And here we see that my dissertation on transport_maps above was not
relevant, because you have not set that. A typo in main.cf, or did you
just assume that /etc/postfix/transport had a special meaning? With no
transport_maps set, your aforementioned hash is ignored, and relayhost
is used. postconf.5.html#transport_maps
> > http://www.postfix.org/DEBUG_README.html#mail
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
clients resend, or
> have I lost mail here and the sender notified?
>
> Nov 20 00:02:55 mail02 postfix/postscreen[20334]: NOQUEUE: reject:
> RCPT from [93.74.115.187]:64752: 450 4.3.2 Service currently
> unavailable; from=,
> to=, proto=SMTP,
> helo=
This is normal and expected. Reread POSTSCREEN_README.html#after_220
namely, the "Important note" and following text.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ertificate verification. But you can learn
about it here if you are interested:
http://www.postfix.org/TLS_README.html#server_vrfy_client
http://www.postfix.org/postconf.5.html#smtpd_tls_CAfile
http://www.postfix.org/postconf.5.html#smtpd_tls_CApath
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
IFICATION_README.html#recipient
http://www.postfix.org/postconf.5.html#reject_unverified_recipient
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
pd_hard_error_limit=1000
> -o smtpd_client_connection_count_limit=0
> -o smtpd_client_connection_rate_limit=0
> -o
> receive_override_options=no_header_body_checks,no_unknown_recipien
> t_checks,no_milters -o local_header_rewrite_clients=
> smtp inet n - n - 1 postscreen
> smtpd pass - - n - - smtpd
> -o receive_override_options=no_address_mappings
> dnsblog unix - - n - 0 dnsblog
> tlsproxy unix - - n - 0 tlsproxy
>
> -- end of postfinger output --
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ject_unauth_destination
[ ... ]
check_recipient_access hash:/etc/postfix/dspam_check_aliases
check_sender_access hash:/etc/postfix/dspam_check_aliases
dspam_check_aliases ::
s...@example.comREJECT
nots...@example.com REJECT
Simpler, and this could be integrated with a general-purpose address
lookup, if desired.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
space.
> Is it intended to type a "tick" and repeat the character ? If not ,
> what is wrong?
If viewed in a pager like less(1), you will see bold text.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
hing that a remote SMTP server tells your smtp(8) client is
logged with the rejection. That text is under the control of all the
remote sites to which you connect. It is not and cannot be
standardized.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
y pertinent but I am running
>
> 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC
> 2011
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> amd64
>
> and Postfix 2.8.7
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
bulk mail sending is a big
chore. Consider that ESPs actually earn their money. Sometimes doing
things in-house is more expensive than outsourcing.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ven: fix the application.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tly used the same four example addresses. So we
could only assume the problem only involved those addresses.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Exactly the point the other Steve was making.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Monday 05 December 2011 06:11:27 Ignacio wrote:
> On Sun, Dec 4, 2011 at 9:15 PM, /dev/rob0 wrote:
> > Your OP sounded as if the headers needed to change for some
> > reason. Since we now know that envelope senders and recipients
> > are what matters, it&
; Hildebrandt's excellent book but I'm still at a loss.
>
> Any suggestions or advice would be appreciated.
Rethink the structure. Simplify. Choose one or the other MTA; make it
do everything you need.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
Nonsense. Recognition of new domains need not be instant. Email is
itself not instant messaging. Domain owners should expect reasonable
delays in changes of domain hosting, and are responsible to plan
accordingly. Your expectations are absurd.
A simple workaround, as I am sure has been suggested on this list
numerous times, is to run a query from a cron job to populate and
postmap the domain lists.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
remains that SSL has been deprecated by
TLS. STARTTLS is the new standard.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
ml#danger
> The reason I'm asking is I added a set of lines for RBL reverse DNS
> and they don't seem to be having any effect.
The "real" question lacks adequate information to answer. See:
http://www.postfix.org/DEBUG_README.html#mail
--
Offlist mail to this addres
newer (and recommended)
Zen list.
> permit
The answer to your original question is that permit_auth_destination
prevents any other restrictions from being used.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
connect to for SMTP. Usually 25.
Much of the world thinks this is so. They are wrong. We are not. You
should keep submission separate from mail exchange, and port 587 is
the standard means for doing so.
BTW I think Noel had the ultimate answer to this thread: just stick
with your smtps on 465 unt
TTLS problem.
Reindl Harald asked about this last night, 01:16 UTC. What a wild
goose/squirrel chase this was!
(I'm sure there is a Boris Badenov / Natasha joke in there somewhere:
"Ees kaput for goose and squirrel!")
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
n the loopback
interface, chances are high that said attacker will also have any
encryption keys that might be used.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
in this thread which
suggests that you should be, see:
http://www.postfix.org/ADDRESS_CLASS_README.html#relay_domain_class
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
t; virtual alias maps hash file.
This is good advice, essentially the same message as from the
aforementioned DATABASE_README.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
gsumm.pl; perhaps if Jim is
still reading the list he can comment?
It would be worthwhile to add these to sample submission and smtps
lines in the default master.cf. Wietse, have you considered that?
Thanks.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
e
whitelist is hard to maintain properly, worse than a large blacklist.
So, you might need to step back and reevaluate your restrictions.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tream from your MX mailstream.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
On Thursday 15 December 2011 08:24:51 Gábor Lénárt wrote:
> On Thu, Dec 15, 2011 at 08:19:18AM -0600, /dev/rob0 wrote:
> > On Thursday 15 December 2011 07:53:35 Tomas Macek wrote:
> > > But we have clients, that send mails on both port 25 and
> > > 587. I really can
it off.
Barracuda "Deep header parsing" is a disaster. A large percentage of
legitimate mail from end users on dynamic IP addresses (most people
are in that group) will be blocked.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
id_maps = static:125
> # Additional for quota support
> virtual_create_maildirsize = yes
> virtual_mailbox_extended = yes
> virtual_mailbox_limit_maps =
> mysql:/usr/local/etc/postfix/mysql_virtual_mailbox_limit_maps.cf
> virtual_mailbox_limit_override = yes
> virtual_maildir_limit_message = Desculpe, tamanho da caixa postal
> excedido, tente mais tarde! Sorry, mailbox size exceeded, try
> later!
> virtual_overquota_bounce = yes
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
including other entries as needed, and 'postmap /path/to/noreply-
reject'.
Finally, main.cf:
smtpd_data_restrictions = [ ... ]
check_recipient_access hash:/path/to/noreply-reject
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
onf.5.html#authorized_submit_users
3. Alternatively, you could limit access to sendmail(1) using
filesystem permissions, but this might break in an upgrade.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
tion and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
"we" refers to my
long-time observation of this list, and I think it's a common
view. Similarly, I think Stan's use of "we" can be defended.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
reserved for such use.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
you decide to go for local(8) delivery, it is simple to set up:
http://www.postfix.org/BASIC_CONFIGURATION_README.html
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
gt; [1] Where "mumble" is one of _client_ or _recipient_ ; it doesn't
> make much sense to use _helo_, and using _sender_ will actually
> increase the chances that you're doing it wrong; the sequence of
> restrictions is VERY important.
snip
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
urse the amavisd-new list would be a better place to follow
up.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g.
My bet is on this file; you have done something in "sender_checks"
that you should not have done.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
g/DEBUG_README.html#mail
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
se may be) see
in their MUA.
> >full logs of sample problem transaction, as well as output of
> >postconf -n.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
e inet:127.0.0.1:12525
>
> /etc/postfix/whitelist
> example.com permit_auth_destination
> u...@example2.com permit_auth_destination
>
> After creating or modifying /etc/postfix/whitelist do
>
> $ postmap whitelist
>
> See: man 5 access
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
worth your time;
my guess is that it would not be.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Tuesday 03 January 2012 11:28:09 Charles Marcus wrote:
> On 2012-01-03 12:09 PM, /dev/rob0 wrote:
> > Info/advice: with postscreen(8), sane HELO restrictions, and good
> > DNSBLs, clamav is not going to get much use.
>
> Clamav, with the sane-security sigs, most certain
-- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
nd consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ame up with: are you using a DNS forwarder which is
probably blocked by Spamhaus? Try testing, from the Postfix host:
$ dig 2.0.0.127.zen.spamhaus.org. any
This should return their test records. Compare with NXDOMAIN here:
$ dig 2.0.0.127.zen.spamhaus.org. any @8.8.4.4
> >> First, please supply 'postconf -n' output, as you were directed
> >> in the list welcome message. This allows us to see how you are
> >> currently configured so we can recommend changes that work with
> >> your particular setup, and help you fix anything that's not
> >> currently correct.
> >>
> >> Also, post the output of following command:
> >>
> >> $ postconf |grep 'mail_version ='
(Stan, UUOG, that can be simply "postconf mail_version" :) )
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
htly less pain.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
pecial syslog_* settings in your postconf, therefore it
seems likely that the problem was introduced by a change in your
syslogd or its configuration.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
is desirable or important. It is generally far
harder to manually speak SMTP to a server than it is to configure a
mail client. I use Kmail or mutt(1), myself.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
hat they are forced to authenticate properly?
That is a policy decision for you to make.
> Whats weird is that the problem gets fixed by simply restarting
> the services.
Try it without restarting Postfix next time, just your saslauthd and
anything it needs for data (e.g., mysqld, postmaster, whatever.) You
do not have a Postfix issue.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ything it needs for data (e.g., mysqld,
> postmaster, whatever.) You do not have a Postfix issue.
Forgot to mention Courier authdaemond, mentioned in the OP.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
of luck on this one.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
ld prefer to avoid
> that if possible.
>
> Another unrelated question, I looked at the mailing list archives
> and 2011 seems to be missing.
> http://archives.neohapsis.com/archives/postfix/
Must not have been a memorable year. ;)
--
http://rob0.nodns4.us/ -- system administration and cons
"IF /^To:/" to anchor to the beginning of the
line.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
few spams & 419s from hotmail or gmail, but the
direct-to-MX botnets are not getting through very often.
> (like it should be) and a filtering during dovecot should mean
> that whitelisted servers still get their email filtered.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Sun, Jan 15, 2012 at 07:49:49PM -0600, Al Zick wrote:
> On Jan 13, 2012, at 5:52 PM, /dev/rob0 wrote:
> >On Friday 13 January 2012 16:57:21 Al Zick wrote:
> >>On Jan 12, 2012, at 3:57 AM, Egoitz Aurrekoetxea Aurre wrote:
> >>>Apart from this if you u
15.
It hasn't changed much; I promoted BRBL to 3 points and SEM to 2. It
would not hurt to add a few less-trusted 1-point lists. My threshold
value is 3.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
uot;dono...@example.us" and also for
"dono...@example.net".
http://www.postfix.org/BASIC_CONFIGURATION_README.html
If you need namespace separation, consider the virtual alias example:
http://www.postfix.org/VIRTUAL_README.html#virtual_alias
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
might
choose.
The task of translation into LDAP is left to you.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
(Web address is blacked out, today only, 2012-01-18)
pient validation and is
> >strongly discouraged.
>
> Postfixadmin supports domain aliasing without losing recipient
> validation (although I don't use it myself)...
Seems like a SQL trigger on insert could easily create both entries
when one is entered.
--
http://rob0.nodns
0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
(Web address is blacked out, today only, 2012-01-18)
Top-posting fixed, please do not top-post your replies on this list.
Thanks.
On Thu, Jan 19, 2012 at 08:16:22AM +0100, Hervé Hénoch wrote:
> Le 18/01/2012 19:30, /dev/rob0 a écrit :
> >On Wed, Jan 18, 2012 at 10:59:46AM +0100, Hervé Hénoch wrote:
> >>In main.cf :
> >>
where there are two authentication failures
> within the same second, or where for some other reason things
> don't match up perfectly.
That can be a problem even with all the logs in one file.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
tem administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
s done. I'm working on that as we speak.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Thu, Jan 19, 2012 at 05:24:31PM -0500, Wietse Venema wrote:
> /dev/rob0:
> > If you want to see smtpd_restriction_classes gone crazy, refer
> > to my "howto" link from the site below. The particular page &
> > sections you would want is 02-postfix-sqlite
401 - 500 of 1152 matches
Mail list logo
