Re: forwarding mail to another MX on same domain

I just realized that this would not resolve the issue because the remote MX would just redeliver it to the local server which is the final destination of the domain. I'm probably better off with a simple alias domain forward. So while it's not worth considering how to tweak my specific configurati

Re: Limiting header_checks by domain or interface

Ville Walveranta a écrit : > Is it possible to limit header_checks either by recipient domain or by > listening interface? I'd like to remove certain headers, but only from > specific domains. > You can set a cleanup for each smtpd. something like this: 192.0.2.3:25 smtpd

Re: forwarding mail to another MX on same domain

Ville Walveranta a écrit : > I just realized that this would not resolve the issue because the > remote MX would just redeliver it to the local server which is the > final destination of the domain. I'm probably better off with a simple > alias domain forward. > > So while it's not worth consideri

Re: forwarding mail to another MX on same domain

Ville Walveranta: > I'll continue here since Krosrow's issue has been resolved (so I'm not > really hijacking the thread). > > I now have the following defined in mailbox_transport_maps: > > [EMAIL PROTECTED]smtp:mx.myexternaldomain.com > > Yet when I attempt to send mail to the loca

Re: Postfix and quota clarification

Hi! On Sat, Nov 22, 2008 at 9:53 PM, Wietse Venema <[EMAIL PROTECTED]> wrote: > mouss: >> Rocco Scappatura a ?crit : >> > Hello, >> > >> > I have a post-office platform based on >> > Postfix-2.5.2+Courier-IMAP-4.0.1-Courier-authlib-0.53+MySQL-5.0.33. >> > >> > Can someone give some hint on how ena

Re: Address Verification Header

Jason Wohlford wrote: On Nov 21, 2008, at 4:37 PM, Noel Jones wrote: Jason Wohlford wrote: On Nov 15, 2008, at 1:36 PM, Noel Jones wrote: Jason Wohlford wrote: Is there any way to perform an address verification on a message and then add a header to the message? I'd like to let postfix do

Re: Access Restriction Not Working

Carlos Williams wrote: > Inbound = blocked > Outbound = still works > > Why? Keeping in mind the suggestions to update your syntax, it sounds like you want smtpd_recipient_restrictions with a check_recipient_access map. Seeing as you want to block both to/from a given domain, you can use the same

Re: Address Verification Header

On Nov 22, 2008, at 11:41 AM, Noel Jones wrote: Jason Wohlford wrote: On Nov 21, 2008, at 4:37 PM, Noel Jones wrote: Jason Wohlford wrote: On Nov 15, 2008, at 1:36 PM, Noel Jones wrote: Jason Wohlford wrote: Is there any way to perform an address verification on a message and then add a h

Re: Address Verification Header

Jason Wohlford wrote: On Nov 22, 2008, at 11:41 AM, Noel Jones wrote: But regardless, if you want to evaluate the results of the verification outside of postfix, you really need to do the verification probes outside of postfix. Yes, but I trust postfix. I have some hope of hacking a perl scr

Use of permit_inet_interfaces?

I now have smtpd_client_restrictions = permit_mynetworks permit_inet_interfaces check_client_access hash:$config_directory/tables/smtpd_client_access reject smtpd_client_restrictions_katharion = permit_mynetworks permit_sasl_authenticated ch

Re: forwarding mail to another MX on same domain

Couple of messages earlier in this thread I posted the following pcre smtpd_recipient_access table: # reject domains that are served by Katharion # on the generic smtpd interface /(@virtualdomain1\.com| @virtualdomain2\.com| @virtualdomain3\.com| @virtualdomain4\.com| @virtualdomain5\.com)$/

Re: Use of permit_inet_interfaces?

Ville Walveranta wrote: > I was under the impression that `permit_inet_interfaces' in > smtpd_client_restrictions would've allowed requests coming *through* > the inet_interfaces (currently defined as 127.0.0.1, 192.168.1.99 – > still in the testing environment) but not from the additional > interf