Re: constant relay access denied on VPS

On Thu, 14 Jul 2011 00:42:09 +, aly.khi...@gmail.com wrote: Sent from my BlackBerry device on the Rogers Wireless Network remove mynetworks line in main.cf, only add it if its not ok by default postconf -n and post logs on pastebin if it still not working

Re: constant relay access denied on VPS

Thank you for your help. There is just too much wrong with this installation. I've decided that I will just nuke the whole installation and start over. Thanks for everyone's help along the way. On Wed, Jul 13, 2011 at 10:03 PM, Victor Duchovni < victor.ducho...@morganstanley.com> wrote: > On W

Re: constant relay access denied on VPS

Am 14.07.2011 04:12, schrieb jeffrey starin: > The mystery deepens. > > When I run postmap -s virtual > > I do don't see dukey but do see users I never created. > > So, how does one recreate the necessary tables? that is, make new hash maps. since you are using some plesk system i would re

Re: constant relay access denied on VPS

The mystery deepens. When I run postmap -s virtual I do don't see dukey but do see users I never created. So, how does one recreate the necessary tables? that is, make new hash maps. Thanks you. On Wed, Jul 13, 2011 at 10:03 PM, Victor Duchovni < victor.ducho...@morganstanley.com> wrote: > O

Re: constant relay access denied on VPS

On Wed, Jul 13, 2011 at 10:01:56PM -0400, jeffrey starin wrote: > Considering that tables are hashed in postfix, it would be helpful if there > was a utility or a method to un-hash the tables and actually see what's in > there. > > Is there a method to un-hash postfix tables and see what is insid

Re: constant relay access denied on VPS

Considering that tables are hashed in postfix, it would be helpful if there was a utility or a method to un-hash the tables and actually see what's in there. Is there a method to un-hash postfix tables and see what is inside them? Thanks. On Wed, Jul 13, 2011 at 9:58 PM, Reindl Harald wrote: >

Re: constant relay access denied on VPS

Am 14.07.2011 03:49, schrieb jeffrey starin: > dukey exists and I can login to domain1.com as dukey and check emails using > horde this means NOT that it exists for postfix because POP3/IMAP/Webmail (Receive) has nothing to do with postfix > I can send email FROM dukey to email addresses in ot

Re: constant relay access denied on VPS

dukey exists and I can login to domain1.com as dukey and check emails using horde. I can send email FROM dukey to email addresses in other domains, and they are received, but as stated in my first email, no one can respond to those emails because they are receiving the following error message back

Re: constant relay access denied on VPS

On 7/13/2011 7:37 PM, jeffrey starin wrote: > I have a VPS with several virtual domains, > first-one.domain1.com > second-one.domain2.com and > third-one.domain3.com Please send in plain text next time so

Re: constant relay access denied on VPS

Jeffrey, Does the user "dukey" actually exist in your recipient table? As you are using a VPS with plesk it looks like the mailboxes are probably made from the control panel in plesk virtual_mailbox_maps = hash:/var/spool/postfix/plesk/vmailbox Check in your control panel. btw this means now

Re: constant relay access denied on VPS

Well that helped, sort of... I added domain1.com to the mydestinations in main.cf and now I'm getting a different error message: User unknown in local recipient table (state 14). At least it's a different error message than before which was relay-access denied. Should I regenerate the recipient t

Re: constant relay access denied on VPS

This might seem obvious, but do you have your actual domain in mydestination in your main.cf file? AK Sent from my BlackBerry device on the Rogers Wireless Network

Re: constant relay access denied on VPS

Sent from my BlackBerry device on the Rogers Wireless Network