RE: About SMTP Auth with Mysql

Thanks for answer I will check mysql proxy -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Patrick Ben Koetter Sent: Wednesday, November 25, 2009 11:06 PM To: postfix-users@postfix.org Subject: Re: About SMTP Auth with Mysql

Re: Postfix/Cyrus Forwarding Question

I belive the best way to way to to this is to use sieve k - "Dennis Putnam" wrote: > I'm not sure if this is the right forum for this question but I don't > know where else to start. > > I am running Postfix/Cyrus on the same server that contains user home > directories. The forwarding m

Re: About SMTP Auth with Mysql

Vahriç, * Vahriç Muhtaryan : > You can find out related out below. thanks for the debug output. Your config looks okay. Your problem is - as I understand it - you want Cyrus SASL to do something it can't do: 1. If you list more than one host with $sql_hostnames then those hosts will be querie

Re: Multiple Mail domains for reverse ptr records? I'm confused

ML a écrit : Hi Wietse, I have some confusion about multiple reverse PTR records per IP. You need only one. The name (from the address->name) lookup must resolve to the address. I am still confused. Like my example below, what happens if I want to setup a single mail server that hosts m

Re: Postfix/Cyrus Forwarding Question

Victor Duchovni: > On Wed, Nov 25, 2009 at 12:41:37PM -0500, Dennis Putnam wrote: > > > If I understand this correctly, I can set the forward_path to a directory > > No, not a directory a file, and not "a" file, but a set of files, one > for each user. For example I remember from historic times

Re: Postfix/Cyrus Forwarding Question

On Wed, Nov 25, 2009 at 12:41:37PM -0500, Dennis Putnam wrote: > If I understand this correctly, I can set the forward_path to a directory No, not a directory a file, and not "a" file, but a set of files, one for each user. > The hierarchy of that directory is not clear The construction of the

Re: Postfix/Cyrus Forwarding Question

Hi Viktor, My bad, I was referring to this line in the documentation when I used $name: $user The recipient's username. In any case I think the light is starting to glow, albeit dimly. The examples in the documentation are not very helpful. Is there someplace I can look for better ones?

Re: Postfix/Cyrus Forwarding Question

On Wed, Nov 25, 2009 at 11:56:41AM -0500, Dennis Putnam wrote: > Thanks, that clears up a few things. It appears that this applies to > individual users via the $name parameter. There is no "$name" parameter. That is a generic place-holder for any of the parameters above it, to explain that you c

Re: Postfix/Cyrus Forwarding Question

Hi Viktor, Thanks, that clears up a few things. It appears that this applies to individual users via the $name parameter. It is not clear how to handle many users (surely I can't list everyone) which may be on different servers. Is there a wild card format and/or a default? Can the path be set

Re: Postfix/Cyrus Forwarding Question

Hi Wietse, Thanks for the reply. I'm not sure I completely understand. Is the forward_path a directory on the mail server or a path to the remote users' home? Is that a per user or system setting (e.g. users' home directories may be on different servers)? I'm guessing that the forward_path is

RE: About SMTP Auth with Mysql

Hello, You can find out related out below. Regards Vahric [r...@postfix-auth1 ~]# ./saslfinger-1.0.3/saslfinger -s saslfinger - postfix Cyrus sasl configuration Wed Nov 25 18:47:20 EET 2009 version: 1.0.2 mode: server-side SMTP AUTH -- basics -- Postfix: 2.5.9 System: CentOS release 5.4 (Final

Re: Postfix/Cyrus Forwarding Question

On Wed, Nov 25, 2009 at 11:27:18AM -0500, Dennis Putnam wrote: > I am running Postfix/Cyrus I assume you mean Cyrus IMAP... > on the same server that contains user home directories. With the local(8) transport delegating delivery via mailbox_transport. > The forwarding mechanism (.forward) is,

Re: Postfix/Cyrus Forwarding Question

Dennis Putnam wrote: I'm not sure if this is the right forum for this question but I don't know where else to start. I am running Postfix/Cyrus on the same server that contains user home directories. The forwarding mechanism (.forward) is, of course, working and I understand it. What I don't

Re: Postfix/Cyrus Forwarding Question

Dennis Putnam: > I'm not sure if this is the right forum for this question but I don't know > where else to start. > > I am running Postfix/Cyrus on the same server that contains user > home directories. The forwarding mechanism (.forward) is, of > course, working and I understand it. What I don'

Postfix/Cyrus Forwarding Question

I'm not sure if this is the right forum for this question but I don't know where else to start. I am running Postfix/Cyrus on the same server that contains user home directories. The forwarding mechanism (.forward) is, of course, working and I understand it. What I don't understand is how this

Re: Design: sender-dependent default_transport

Rainer Frey (Inxmail GmbH): > Hi Wietse, > > thanks for addressing this issue, a scaling solution for this problem will be > really appreciated. > > We are an E-Mail Marketing provider and offer a hosted solution for a broad > customer base for which we want to be able separate the reputation (

Re: Postfix DKIM

On Tuesday 24 November 2009 20:38:51 Michael Saldivar wrote: > On Wed, Sep 9, 2009 at 8:08 PM, KLaM Postmaster wrote: > > I found the easiest way by far, was to use the DKIM feature of > > amavisd-new > > simple to setup and work like a ch

Re: Don't filter the users\

Mikael Bak schrieb: > Submission on port 587 implies STARTTLS (I think). Well, only if you configure it that way. (OK, it *really* makes sense to encrypt transfer, if you do authentication...) But: jan...@kohni ~ $ telnet smtp.web.de 587 Trying 217.72.192.157... Connected to smtp.web.de. Escape

Re: Rate limiting with anvil

On Wed, Nov 25, 2009 at 01:20:45PM +0100, Daniel Ryslink wrote: > anvil_rate_time_unit = 300 > mynetworks = $config_directory/our_network_blocks What is in this file? > smtpd_client_connection_rate_limit = 30 > smtpd_client_message_rate_limit = 100 > smtpd_client_recipient_rate_limit = 60 These

Re: Don't filter the users\

Stan Hoeppner wrote: > Why bother? This is an ISP scenario, correct? The 587 command set is > standard SMTP right? Just iptables (verb) TCP 25 to TCP 587 for any IP > ranges within the ISP's MUA customer range. This is assuming said > customers already have to submit auth over TCP 25 to relay m

Re: Rate limiting with anvil

By default, Postfix will exclude clients in mynetworks from smtpd_client_mumble_limits. You may want to specify a separate list for mynetworks (relay control) and for anvil (rate control). http://www.postfix.org/postconf.5.html#smtpd_client_event_limit_exceptions (with Postfix 2.1, this was calle

Re: valid checkers for POSTFIX/DKIM/DOMAINKEYS

On 11/25/09, fake...@fakessh.eu wrote: > Le mercredi 25 novembre 2009 03:55, Israel Garcia a écrit : >> Hi >> >> I'm really sorry if it's OT but I'm having problems verifying my setup >> of postfix/dkim/domainkeys. I've found some dkim/domainkeys online >> checkers, one told me dkim/domainkeys val

Re: Rate limiting with anvil

Thank you for answering, here is the requested information: According to the instructions in the mailing list welcome message, send postconf -n output instead of cut-and-paste. alias_database = hash:/etc/mail/aliases alias_maps = hash:/etc/mail/aliases allow_min_user = yes allow_percent_hack

Re: valid checkers for POSTFIX/DKIM/DOMAINKEYS

On Tue, 2009-11-24 at 21:55 -0500, Israel Garcia wrote: > Hi > > I'm really sorry if it's OT but I'm having problems verifying my setup > of postfix/dkim/domainkeys. I've found some dkim/domainkeys online > checkers, one told me dkim/domainkeys valid others checkers not. When > sending the same

Re: valid checkers for POSTFIX/DKIM/DOMAINKEYS

Le mercredi 25 novembre 2009 03:55, Israel Garcia a écrit : > Hi > > I'm really sorry if it's OT but I'm having problems verifying my setup > of postfix/dkim/domainkeys. I've found some dkim/domainkeys online > checkers, one told me dkim/domainkeys valid others checkers not. When > sending the sam

Re: Rate limiting with anvil

Daniel Ryslink: > Hello, > > I am trying to set rate limits on our smtp relays to prevent abusive > (compromised) user hosts from flooding the service with fast, intensive mail > floods. > > I have used the following directives (I can post whole main.cf, but I don't > think it's necessary): >

Re: Design: sender-dependent default_transport

Hi Wietse, thanks for addressing this issue, a scaling solution for this problem will be really appreciated. We are an E-Mail Marketing provider and offer a hosted solution for a broad customer base for which we want to be able separate the reputation (so individual customers can take part in

Re: Don't filter the users

You can tell the users that the "submission" port gets a better level of service than port 25, because they share that port with spammers. As you pointed out in your original email, they would be subject to less filtering, and therefore there would be less delay, less false positives, and so on.

Rate limiting with anvil

Hello, I am trying to set rate limits on our smtp relays to prevent abusive (compromised) user hosts from flooding the service with fast, intensive mail floods. I have used the following directives (I can post whole main.cf, but I don't think it's necessary): smtpd_recipient_limit =